In the phrase ‘ideas mean nothing and it’s all about execution’, I think by ‘ideas’ people normally mean (good, novel) ideas for a product/service.
But indeed they also mean visualizing their product/service succeeding (without thinking about all the implementational details, especially ways it can go wrong).
For a startup to succeed, you need a good product/service idea AND good execution. (As a good product poorly executed will probably fail, as will a bad idea well executed.) So neither is optional.
But by saying ‘ideas mean nothing and it’s all about execution’ people often imply that (good) product/service ideas are relatively easy, and execution is the hard bit. However the fact that only 5% of patents get commercialized, and only 10% of startups succeed, suggests that good ideas & good execution are both scarce.
So maybe ‘ideas mean nothing and it’s all about execution’ is simply a counter to inventors who assume that execution is easy and ideas are the hard bit. As they often do, e.g. individuals who file patents and assume incorrectly that they’re very brilliant/valuable and lots of companies will want to licence or steal their idea.
Or it may be that those who are good at execution can recognise good product/service ideas (fairly well), even if they can’t come up with them themselves. Whereas those who can come up with good ideas usually can’t do good execution. So good executors are more valuable for a startup.
Yeah, I think we agree that it depends on where you draw the line between “idea” and “execution”. It just seems odd to me to draw the line in the place that most people draw it, and which you refer to in your reply, as the idea only being about the product. If you think about an idea as a simulation, it’d be silly to only simulate the product part and to not simulate anything about customer acquisition.
Yes I see what you mean re drawing the line in different places. Similarly an idea for a product can be distinguished from the execution, i.e. creation, of the product.
A few times I’ve been approached by people who claim to have ‘invented’ some software, perhaps with a patent for it, but on closer question they’ve merely had an idea for some software and want someone else to write it. (Again assuming that the idea is the hard part.)
This illustrates that a patent is a simulation (or indeed a plan) of a product. If it were to be created, it would do XYZ. (US patents are meant to include sufficient detail to enable people with relevant skills to implement it—i.e. a complete plan—though European patents needn’t.)
My inconclusive thoughts around this:
In the phrase ‘ideas mean nothing and it’s all about execution’, I think by ‘ideas’ people normally mean (good, novel) ideas for a product/service.
But indeed they also mean visualizing their product/service succeeding (without thinking about all the implementational details, especially ways it can go wrong).
For a startup to succeed, you need a good product/service idea AND good execution. (As a good product poorly executed will probably fail, as will a bad idea well executed.) So neither is optional.
But by saying ‘ideas mean nothing and it’s all about execution’ people often imply that (good) product/service ideas are relatively easy, and execution is the hard bit. However the fact that only 5% of patents get commercialized, and only 10% of startups succeed, suggests that good ideas & good execution are both scarce.
So maybe ‘ideas mean nothing and it’s all about execution’ is simply a counter to inventors who assume that execution is easy and ideas are the hard bit. As they often do, e.g. individuals who file patents and assume incorrectly that they’re very brilliant/valuable and lots of companies will want to licence or steal their idea.
Or it may be that those who are good at execution can recognise good product/service ideas (fairly well), even if they can’t come up with them themselves. Whereas those who can come up with good ideas usually can’t do good execution. So good executors are more valuable for a startup.
Yeah, I think we agree that it depends on where you draw the line between “idea” and “execution”. It just seems odd to me to draw the line in the place that most people draw it, and which you refer to in your reply, as the idea only being about the product. If you think about an idea as a simulation, it’d be silly to only simulate the product part and to not simulate anything about customer acquisition.
Yes I see what you mean re drawing the line in different places. Similarly an idea for a product can be distinguished from the execution, i.e. creation, of the product.
A few times I’ve been approached by people who claim to have ‘invented’ some software, perhaps with a patent for it, but on closer question they’ve merely had an idea for some software and want someone else to write it. (Again assuming that the idea is the hard part.)
This illustrates that a patent is a simulation (or indeed a plan) of a product. If it were to be created, it would do XYZ. (US patents are meant to include sufficient detail to enable people with relevant skills to implement it—i.e. a complete plan—though European patents needn’t.)