Thursday, November 09, 2006

An innovation process and software framework

In a recent press release, Archstone consulting reports on its findings in a recent survey on innovation. According to their survey, over 70% of the firms they talked to were planning to increase investment in innovation, yet over 50% were dissatisfied with the results of their innovation initiatives to date. Only 5% claimed to have "a highly effective innovation process".
Clearly there's a significant disconnect between these figures, and we believe one of the important reasons is that innovation is still so poorly defined from a process and systems perspective.

As many of you know, we at OVO have been working to define an "end to end" process that supports innovation, and to define the tools and software necessary to support that process. Much like a purchasing process has defined phases or steps, and enabling software, or as a sales team has defined phases or steps and underlying CRM software, we believe innovation needs to be defined from a process point of view to be repeatable, and will need integrated software applications as the number of people and number of ideas increase.

To that end, we've put together the following diagram to start a discussion about innovation processes and tools.


At the top, in green, are activities in the innovation process, starting with identifying trends and customer requirements. In the arrow are the steps we advocate for an innovation process: generate ideas, capture ideas, evaluate ideas, develop as products or services and launch the new products or service.

In blue are the data and system requirements to support each phase of the innovation. These are divided into two sections: software or data that support a specific step in the process (eg brainstorming software supporting the "Generate" step) and software or data that supports the entire process, which is represented at the bottom of the graphic. These applications or data requirements span the length of the process and include requirements like capturing metrics across the process and reporting across the process.

By creating this framework, we are trying to forecast what we think will happen to innovation, and use analogies from the ERP world and CRM world. Increasingly, firms value consistent, collaborative information that enables a business process. This means that the existing software applications that support "innovation" will have to consolidate and support the entire process in one component framework or integrated solution, just like the way ERP consolidated from financial software, purchasing software and inventory software. Innovation is an important and necessary business process, and probably the least well supported from the standpoint of process and software today.

This framework is one we've put forward as a representation of the processes and tools necessary for repeatable, successful innovation. If you care to, please comment or provide your feedback. I think if we practitioners, consultants and interested bystanders can create a consistent vision for the future of innovation and the tools and processes necessary for success, we can help our clients and business partners become more successful.

Let me know your thoughts and what you would change in the framework.
AddThis Social Bookmark Button
posted by Jeffrey Phillips at 4:50 AM

8 Comments:

Anonymous Paul Gladen said...

Hi Jeffrey

Thanks for sharing your framework - it looks robust to me - and stimulated a couple of thoughts.

One aspect that might be worth exploring is how this interacts and integrates with existing processes, data and systems. For example how does it link to competitive intelligence capabilities, the CRM environment, knowledge management systems or reporting/performance measurement systems.

Often the opportunities for innovation are under our nose we're just not tuned to spot them - but if we can integrate innovation tools into the business as usual environment we may succeed in making innovation a business as usual activity rather than an afterthought.

6:30 AM  
Anonymous Anonymous said...

Hi Jeffrey,
There is a need really building to build a more structured innovation preocess to help the company and the individual. Today we don't have any integrated application but there are emerging a number of techniques, software and tools that might be able to be combined into a ERP for innovation.
You add to that emerging process. I take dispute with some of your sequence. I strongly believe Roadmapping must go at the front end, not at launching- although this depends on your definition if end-to-end.
I'd say that a map that I relate too was recently produced by Pretium that places platform technology and Business options as the first activity, followed by Roadmapping to exploit this along with Idea Management, then the Stage Gate process and having a systematic value system in place to get to commercialisation. Within your suggested map you introduce the aspects before Ideas of spotting, trend capture, VOC. I feel your Develop is more Commercialise and we need to asdd in other tools, evaluations like a clear Go-to-market process, the Diffusion of Innovation and their options, Web-based technology.
My biggest question over your process lies in Launch- Product visioning and as I have previpously said Roadmapping come much earlier in the process
My contributions to what we are all striving to get our heads around
Regards

6:35 PM  
Blogger Dorai said...

Thanks for describing this framework. I can see how it can implemented using some open source portal frameworks and portlets (like Plone, Liferay) or commercial products. If you have pointers on how tools can be used for trend spotting, I would appreciate hearing about it.

Right now, we use our product InfoMinder to track certain web pages. But this is a low level tracking of information. Spotting trends may require a higher level Tech Mining or Text Mining.

3:57 PM  
Blogger brimyn said...

I like your concept of Gernate, Capture, Evaluate, Develop, and Launch. I also know that in many industries there is a serious problem of developing prototypes way to late in the process. I would rather see some fast-cheap prototypes available BEFORE the evaluation.

If you put a step called "Concept" in between Caputre and Evaluate you might have a better framework to do the evaluation. The prototypes and concepts in that new step should also have a smell test applied by real customers ... not just the internal experts who may be out of touch.

8:20 AM  
Anonymous Anonymous said...

Hi Jeffrey,
FYI - your cool diagram does not show up in Mozilla Firefox 2.0. Just thought you might like to know (so non-Internet Explorer users can benefit, too).

10:49 AM  
Anonymous Scott Arthur Edwards said...

Hi my friends! I'm writing to you because I just came across a business that I think has great potential. It lets you save money on almost everything. Make money from almost everything, Including home loans- plus... help lower your taxes--best of all--it requires absolutely no investment. I thought you might be interested and like to check it out...

Here I have a net opportunities site/blog. It successfully covers net opportunities related stuff and almost everything else!

Come and check it out if you get time, Scott.

9:22 PM  
Anonymous Anonymous said...

Here it is... FREE advertising, FREE download. No cost to you! Get your FREE download NOW! Make money and get FREE advertising! This is a great program for you to take advantage of... Check this out now for FREE!

To find out more visit: home business site. It successfully exposes FREE information covering traffic and home business related stuff. Don't forget, FREE, FREE, FREE!!!

10:53 PM  
Blogger Scott A. Edwards said...

Dear friends, Now you can help yourself take advantage of the huge surpluses of FREE advertising in your spare time, in the comfort of your own home. Hook up NOW with this exiting program. Click here: FREE INFORMATION

11:20 PM  

Post a Comment

<< Home