Why Killing ideas Fosters More Innovation
Why Killing ideas Fosters More Innovation
Bluenove's Martin Duval is not only a successful entrepreneur and an open-minded innovator. He is also a controversial business writer with French flair who can deliver straight to the point conclusions. Whereas most would-be innovators will lay a stress on the production of new ideas - the ideation process - Duval knows, like most hardened innovators, that the truth lays not in that process but in the more delicate art of rejection and ... killing innovations. Here are his thoughts on the subject, for the benefit of our readers:
Lately, I had a chance to describe the challenges faced by French start-ups with regard to the financing of the early innovation phase and the managing of partnerships with major corporations, and that piece was published by the French High Tech weekly 01 Informatique. In that article, entitled all players in the innovation chain should play their role!, I was stating that start-ups should only focus and partner with those corporations, which have implemented a structured and proactive business incubation and partnership programme such as NOVA External Venturing, part of the manufacturing industry behemoth Saint-Gobain, or the 'Veolia Innovation Accelerator'. Amongst the new 'Open Innovation' processes which have been designed and implemented by those major corporations, I did point out the ability and the value of killing innovation and potential partnerships. I know that this may sound strange coming from a proponent of innovation but I insist, one has to learn how to say NO if one wants to get to YES.What I mean by that is that start-ups by nature have limited resources and time to work their way through the complexity of a large organisations and handle their long-winded decision-making cycles. Therefore, when a large organisation is able to implement a process to efficiently filter out potential partners within a reasonable period of time, it is in fact sending out a positive rather than negative message. I would advise a 1 month or a 6 weeks-delay at the most as a fair period for a large organisation to get back to a candidate partner with a positive or negative answer. Delaying the response for any length of time and keeping start-up owners on tenterhooks is simply not on in my eyes.The start-up in question can then decide to keep trying to partner through another part of the organisation at its own risk, or to change what needs to be changed within its project structure or even look for another partner. Ideally, the more a negative feedback is explained and detailed, the higher the value that is delivered: such explanations can help highlight the weaknesses within the original project, so as to better identify the target market position for the new solution. As a consequence, it is an easy way for corporations to deliver value and improve their reputation within their innovation ecosystem. It is certain though that rejecting an application actually requires a lot of preparation as well as some process and resources in order to produce the analysis and manage the follow-up the within 1 month to 1 ½ month. As a matter of fact, rejection can take place at each gate within the open innovation stage-gate process with a higher probably and more preparation needed early in the process than ever after: from screening before initial contact, right after the initial contact and/or meeting, after the feasibility study, during the partnership negotiation and after the test.To a certain extent, I even believe that a good quality rejection process delivers more attraction and better corporate image than piecemeal success stories. Besides, that kind of process applies not only to start-ups but also to universities, government-owned or private R&D labs, suppliers and customers involved in crowd-sourcing initiatives etc. At the end of the day, large organisations can derive a real high-end competitive edge from the management of rejections regarding innovation proposals from start-ups and other innovators. The tougher the process is, the more desirable those selective large organisations therefore become in the eyes of smaller players.taginlineimportSimilarly, when it comes to managing internal innovation processes, too little attention and effort is devoted to killing projects in my eyes. Oftentimes, a standard innovation pipeline is contrived - as part of an innovation process - with a wide ideation spout on the left side and a narrow tube on the right, from which successful projects emerge. Once again, there is so much value in killing projects efficiently at each stage-gate of the innovation process and here are a few examples of the expected benefits:
- re-allocating resources to other, more promising projects,
- learning from trial and errors and capitalising on best practices across projects,
- developing a culture of innovation - learning from errors, aiming at success - in order to foster motivation and encourage new daring ideas,
- simplifying project portfolio management,
- reducing overlap if not competition between projects.
Innovation processes are becoming more and more collaborative with the help of enterprise 2.0 platforms supporting ideas and project management. Thus it ensues that sharing thoughts about innovations that should not be accepted and projects that should be stopped is an absolute must-have. Once again, let us emphasise the fact that the proper number of resources should be allocated to the screening of projects and that pruning weak ideas should be an area of focus. Both the rejection and even the killing of bad ideas/innovations can actually deliver benefits from a competitive edge viewpoint. Are you - and your company - ready to reap those benefits and image improvement from saying NO and for killing more innovations?
Bluenove is a consulting firm specialized in Open & Collaborative Innovation http://www.bluenove.com
June 28, 2010Thanks Michael for your comment, very kind. All the credit goes to our good friend and partner - and former co-worker - Martin Duval from Bluenove. My only merit was to edit the English translation of the text. Glad you liked it and let me know if you'd like to contribute on a similar topic. my Twitter handle is @ygourven or @orangebusiness.
June 21, 2010This is well written, Yann. I've found that big companies typically won't share much in the way of feedback on reasons for discarding the submission. They fear that doing so will backfire on them (and there may be something to that notion). Some companies with which I have good relationships do provide decent feedback in rejecting submissions, and I agree it enhances my perception of them.
April 1, 2010Thanks for your kind comment Roland. I like your idea about letting people work on the project and then revisiting the project based on people's enthusiasm. Very refreshing!
March 31, 2010Totally agree that killing ideas is crucial but I'm reminded of a talk given by Henry Chesbrough where he talked about type 1 and type 2 errors. To cut a long story short he talked about revisiting projects you've killed 3 months later, if the people are still working on them then it might be worth revisiting the decision. But yes as P&G say fail fast and cheap, not slow and expensive.
October 19, 2016
October 6, 2016
September 27, 2016