George Hadjiyiannis

George Hadjiyiannis

Software Executive, Entrepreneur, Software Architect

The role of execution in innovation

Why innovation in most companies seems to falter.

George Hadjiyiannis

8 minutes read

Innovation

We are by now used to the idea of a light bulb being the universal icon for innovation. This is, of course, a tribute to Thomas Edison's most well-known invention, but not by any means the only one. Edison was one of the most prolific inventors in history, with a list of over 1000 patents bearing his name. The light bulb icon is still used to represent the act of generating ideas, and by extension the act of innovation.

However, Edison famously also said:

“Genius is one percent inspiration, and ninety nine percent perspiration. As a result, a genius is often a talented person who has simply done all of his homework.”

Unfortunately we often conveniently forget about this part of the light bulb story. Innovation in many companies today is simply a focus on generating ideas (ideation). The actual perspiration part, execution, gets relegated to a side task. When companies invest in innovation (and such investment is by no means to be taken for granted), they generally do explicit investments in ideation, but with little thought for the execution that inevitably needs to follow. They spend significant amounts of money and effort on market research, they fly employees to remote sites for hackathons, they organize Design Thinking workshops, and they pay for software to manage the ideas coming from both employees and customers. Everyone gets excited about the possibilities and starts talking about new markets and new products, but, more often than not, the eventual outcome has a different story to tell. When all is said and done, there is usually little to show for it at the end.

At the entrance of the world-renowned INSEAD Business School in France, stands a quote by Georges Frédéric Doriot (considered the father of Venture Capital):

“Without action, the world would still be an idea.”

(many thanks to Prof. Theodoros Evgeniou for letting me know of this quote; it is in many ways the final idea that led me to this post). Ideas are indeed all for nothing unless they are brought to fruition by the appropriate execution. When companies (at least the ones who invest anything in innovation) fail to produce great and innovative products, it is almost never because of the lack of ideas. It is almost always the result of a failure in execution.

There is a few different modes of failure that I have encountered previously. The first evolves more or less along the lines of the following scenario: A certain team undertakes one of these ideation exercises (usually some form of workshop), and comes up with an idea that they get really excited about. At the end of the workshop everyone is excited, and fully intends to follow through on this idea, because it is believed to be so valuable. Up until this point, however, there has been no thought of what it will cost. The idea looks simple so it is assumed it will not cost a lot (I plan to write a later post as to why this phenomenon always seems to happen in software products). Often, there is the implicit assumption that it can be implemented “on the side” of the normal business with zero additional investment. Then all the team members go back to said normal business, where generally there is little spare capacity (if, indeed, the organization is not already underwater, as these workshops tend to take place as a reaction to the company finding itself outpaced by their competition in the first place). The strain of the daily business often takes priority over executing on the idea, which is seen as optional. The team starts off with little effort applied, and slowly peters out as the realization settles in that they cannot execute this as a side project. In one of the companies I worked for, we had a classic example of this scenario. A team of design and UX experts went off to an off-site Design Thinking workshop. They spend four days on ideation, coming up with an idea for a mobile app. During the fifth day, the finalized various things and put together a “prototype”. They were particularly proud of the fact that it only took them four hours to create their prototype. Notice, however, the complete lack of software engineers (and by extension, the lack of knowledge of the cost of creating the app). The prototype turned out to be no more than a click-dummy with a few screens of what essentially looked like a messenger app, for an app that was meant to be powered by AI. In the end, the entire project remained nothing more than a click-dummy.

The second mode usually impacts the teams that are knowledgeable enough to have allocated real resources for the execution, albeit not enough. Typically the idea that initiates the whole process will be of a scope that is not significantly less than the very product that led to the company's creation, yet the budget and resources allocated will be substantially smaller. Once again, the idea is assumed to be simple, and as a result expected to be cheap. The company engages in the execution, only to find out that, in practice, the product will cost a lot more than expected. At this point there are two options left: the company can abandon the project completely, or it can take shortcuts and cut scope, often sacrificing the end-value of the product in the process. It is worth noting that most of the time this latter option also leads to an abandoned product, once the customers find out that the value is not there because of underinvestment. Unfortunately, Edison was not exaggerating for dramatic effect when he said that 99 percent is the hard work. See, he is also famous for another quote:

“I have not failed. I just found 10,000 ways that won't work”.

The light bulb, iconic as it may be now, was an innovation no different than any other. The idea of resistively heating a filament with an electric current until it glows, inspired as it may have been, was probably the simple part. The hard part was finding a combination of materials, packaging, and manufacturing techniques that resulted in a lamp that was affordable, yet did not burn out in a few hours. Edison went through a very large number of tries before he had something that would work in practice.

So, what should a company do if they want to be successful in innovating? First of all, stop investing in the one percent, and start investing in the whole thing. Accept the fact that you will never succeed in innovating with execution being a side-project to your daily operations. Create and allocate budget that is meant to cover execution, including product creation, as well as Go-to-Market, and the the first year of operations once you are there. Resist the temptation to circumvent this realization by assuming that you will just “reuse” the resources you use in the daily business (“Oh, we'll just use the servers we have for the current product - there's still plenty of capacity left”). It does not matter whether these resources are your front-end engineers, or your data-center servers. The fact of the matter is that when forced to make a decision between the daily business and the innovation whenever any such conflict occurs, realistically you will choose to go with the daily business, and the innovation project will stall. In effect, when you have to risk the stability of the current servers in order to install a new middle-ware for the innovation project, the installation will stall for a long time.

Also, make sure that the majority of the budget is allocated to the execution. Simply reduce your ideation ambitions until the scope is such that you can do it justice during execution. If your budget for ideation and requirements discovery is three months, and your budget for execution is four, you will simply end up with a great idea and an insignificant portion of the product. In the same company from the scenario above, I experienced a project that worked with the customer for 7 months on discovery, and left themselves 3 months to build it (spoiler alert: it did not end well).

Finally make sure you build a dedicated team with the right mix of people. Ideation is mainly associated with creative people, and visionaries. Execution is manly associated with engineers and operations people. It is unlikely you can staff a team where every person is good at both ideation and execution so don't try. Instead, get both skill sets through the mix. Ideally you should have the complete team from the beginning. And yes, that means more engineers than creatives; this should not be a problem unless you have people making decisions for the skill-set they do not have. The creatives should drive ideation, and the engineers should drive implementation approach and cost estimates. Both groups can contribute to both activities, but each activity should be driven by those with the core competence in that activity. Finally, iterate on scope until you get something of value that can be implemented in the budget you have allocated.

Most companies fail because they simply focus on ideation and assume the execution. Unfortunately, ideation is essentially the theory of the product; execution is the practice. And as the quote goes:

“In theory, there is no difference between theory and practice. But in practice, there is.”

(atrributed to Jan L. A. van de Snepscheut).

Recent posts

See more

Categories

About

A brief bio