Archive for the ‘Innovation Examples’ Category

Reducing Cycle Time in the Early Phases of the New Product Development Process

Wednesday, June 27th, 2012

Cycle time reduction is usually reserved for the engineering/manufacturing phases of the new product development process. This is not surprising since it’s fairly easy to measure the time to make an engineering change or create a CAD drawing. But how do you reduce cycle time within the more subjective activities of the early phases of new product development a.k.a. Fuzzy Front End (FFE)?

Three Critical Considerations: Unfortunately, there is no single easy solution to reducing the cycle time of the FFE. Three of the most critical challenges typically encountered in reducing FEE cycle times include:

1. Lack of strategic focus

2. Absence of a sustainable new product development front-end process

3. A lack of capabilities and infrastructure to support a front-end process

Strategic Focus

If you don’t have a strategic focus, get one. You need to understand where you’re going to compete, who you’re going to serve and what technology is going to get you there. If you do have a strategic focus, communicate it. Start communicating your strategic focus to the members of your team. If your strategic focus is not evident to your team, you’re just going to be spinning your wheels with a lot of off-strategy ideas. Off-strategy ideas equate to wasted time.

The Importance of a Front End Process

We have witnessed many companies rushing their products to market without investing time to understand either the market or the customer. Perhaps the sales person makes a few customer calls, but that’s about all. Sure enough, that cuts down on the cycle time in the FFE, but equally surely, it spells disaster. Remember Robert Cooper’s research, where poorly-defined early-phased FFE activities equated to a 26% success rate, whereas sharp and early definition produced a success rate of 85%. So we certainly do not recommend skipping these important FFE activities for the sake of reducing your cycle time.

Infrastructure Is Essential

Essential FFE capabilities include a marketing research team that performs on-going research to gain an understanding of unmet customer needs, attitudes, perceptions, market size, trends etc. The team is responsible for constantly feeding a pipeline of opportunities, so that marketing research efforts are independent of any single project. This offers considerable advantages over the alternative approach, which involves setting up ad hoc research capabilities and additional time-consuming data collection for each new product that is released to market.

Perhaps you already have a marketing research team, but everything still seems to move at snail’s pace. This is a familiar problem. It usually lies with too many off-strategy ideas, and either a lack of strategic focus, or a failure to communicate the strategic focus to the marketing research team.

If you’re genuinely serious about releasing successful new products and reducing cycle time in the FFE, do your due diligence, and ensure that you have an excellent understanding of your customers and market. Assess whether your organization has a sustainable new product development process—one with the right market research capabilities. Last but not least, ensure that you have a strategic focus, thereby reducing all those off-strategy ideas.

The secret is that by ensuring a more robust and focused up-front product development process you will achieve the desirable side-effects of reduced cycle times and successful new products.

Share

If You Build It, Will They Will Come?

Wednesday, June 13th, 2012

So often, when developing new products, new product developers get caught up in the beauty of the solution. We believe the product is perfect and people will clamor to buy it. Like Ray Kinsella in Field of Dreams we believe “If you build it, they will come.”

But, so often dreams are dashed and the product never catches on. We blame marketing and sales, we blame the customer who didn’t see the value of the product, and we are dumbfounded that even though we designed the best solution to a problem, no one wanted it.

Maybe we need to think about the theories of diffusion and adoption. There are things we can do, as product developers, to improve the chance that our new product will catch on and be a success. Everett M. Rogers, author of “Diffusion of Innovations” and grandfather of diffusion theory offers many insights into how innovations are adopted and how characteristics of innovations can help or hinder adoption.

Diffusion

Diffusion is defined by Everett Rogers as the process by which an innovation is communicated through certain channels over time among the members of a social system. Some people take longer than others to try out and adopt a new innovation. The first ones to adopt an innovation are called Innovators. They tend to be avid consumers of mass media, from which they learn about new innovations they are eager to try out. They also tend to be big networkers, sharing information about innovations across far-flung social networks. Since innovators tend to be a little “out there” they don’t function as opinion leaders, but their value is in getting the word out to different far-flung social networks. They make up about 2.5% of the population.

The opinion leaders are in the next group called Early Adopters. They take a little longer to try out and adopt new innovations. They read mass media, but they also network with innovators and learn about new innovations. They are different from innovators in that they are looked up to by their social group as a source of advice on new innovations. Once they adopt an innovation, they use their personal influence with their social network to encourage adoption. Early adopters make up about 13.5% of the population.

The next group to adopt is called the Early Majority, and they make up 34% of the population. To a great extent they rely on the opinions and experiences of the early adopters in learning about and deciding whether to adopt new innovations. Later adopter groups also rely on their social network for finding out about new innovations, but they take even longer to decide try and adopt.

Implications for New Product Development

Based on diffusion theory, Rogers notes several characteristics of innovations that encourage diffusion and affect the rate of adoption. This is excellent advice for new product developers. To encourage diffusion and adoption, create a product with:

• Relative advantage over other products – innovators and early adopters look for a better value proposition

• Compatibility with existing values, beliefs, past history and needs of potential adopters – the less a potential adopter has to adjust their behavior the greater the chance of adoption

• Minimal complexity of understanding and use – the more confident a person is that they can master and use the innovation, the more likely they are to adopt it

• Trialability – free trials and demos let a person try the product with no risk

• Observabililty – very often people need reassurance that they are making the right decision by adopting an innovation. If they can see many people have already adopted an innovation, they will feel more comfortable adopting it

As an example, Rogers presents the case of cellular phones. In 10 years time, starting in 1983, 13 million phones were sold in the U.S. During that time performance improved and prices came down, which encouraged adoption, but the design of the product has all of the above attributes, which encouraged very rapid adoption:

• Relative Advantage: Saves time in missed appointments and delayed schedules, can be used in an emergency, considered a status symbol

• Compatibility: For the user, the cellular phone operates just like a regular phone and it connects into the existing landline phone system

• Complexity: Because the cellular phone operates just like a regular phone, the user did not need to learn new skills

• Observability: The portable nature of the product and its use in public places helped emphasize the benefit of status to potential buyers

• Trialability: It is easy to borrow a friend’s phone and try it out. Also, many rental cars came with a cellular phone, providing an opportunity for trial

The next time you develop a new product, think about how you can incorporate these attributes into your product design. It will make a difference.

Share

Can you take small steps to innovation?

Wednesday, May 23rd, 2012

It takes a lot of effort to develop innovative ideas.  You practically have to transform your organization like A.G. Lafley did at P&G.  He successfully made this transition, but it took a lot of effort to do so.  The transformation included building a culture of innovation with strong senior management support, and the development and implementation of strategies, processes and infrastructure to support breakthrough ideas.   

Research states that the most profitable ideas are those that are breakthrough, but what if you’re not up to making a major transformation like P&G?  Can your organization take small steps to innovation?  I think so, small steps are very effective, especially when your organization is resistant to change.  One of the first steps in developing innovative products is to have an innovation strategy and strong leadership support; this in turn fosters a culture of innovation.   According to Booz Allen’s 2011 Innovation study, what drives innovation isn’t R&D spend, but rather strategic alignment and culture.

Your innovation strategy ultimately aligns with your business strategy, and it should indicate your strategic intent across your product strategies.  If you want to go beyond simple product revisions you need to indicate this within your innovation strategy.     ‘When’ is another important attribute that needs to be accounted for within your innovation strategy.  This is where you indicate the speed in which you implement changes to being more innovative, and it is totally appropriate to take small steps.   These steps can include:

1.  Development of a business and innovation strategy that is clearly communicated to the key players within your organization; including your new product development team members.  These strategies will enable your team to develop product strategies that align with your innovation strategy.  Alignment is KEY.

2.  Internal strategic initiatives sponsored by the CEO/President.   These initiatives can include an innovation day.  As the CEO/President, make sure that you’re present for opening and closing remarks, ideally participating during the entire session.  It is also important that it is not a one-off event, it is important to build a process for on-going idea submission and collaboration.

3.   Field studies that engage your staff in actively understanding unmet customer needs, this can be facilitated through a process called Design Thinking (see the link below for more information on the Design Thinker framework).

http://strategy2market.com/downloads/experiencepoint_s2m_productsheet.pdf

This is the time to get started on taking small steps toward more innovative products within your organization.

mdrotar@strategy2market.com    312.212.3144

Share

Mind Mapping for Generating New Product Requirements

Wednesday, May 23rd, 2012

According to Wikipedia, “Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid to studying and organizing information, solving problems, making decisions, and writing. …… Mind maps are, by definition, a graphical method of taking notes.” Mind Maps can be used to organize customer requirements during the conceptual stage of product development when the vision of the product is yet unclear. They help organize brainstorming sessions and document results in an easy to understand manner. Mind Maps usually start with a very simple idea or product description and branch out from there and are a visual representation of everything a product must do or that customers want it to do. They branch out and document a product development team’s trains of thought until the details emerge. (Fishbone diagrams are actually a form of mind map.)

Mind Mapping is not new. It’s been around for centuries. However, it’s been done manually with pen and paper. What is new is the software that allows users to create, modify and utilize mind maps quickly and efficiently. There are many software programs on the market today, both paid a freeware. Mind Maps can usually be exported into Excel and other programs for documentation and tracking.

I used mind mapping techniques to lead a customer team through the initial requirements gathering and development for a large scale factory automation project. There were technical and operations people on the team which lead to a multitude of business and technically related requirements. During the first day, the team generated over 130 separate requirements for the system. Some requirements were at a very high level and some were at the lowest levels of detail. Every suggestion was documented, no matter how trivial it might have seemed at the time. Over the next day and a half, Mind Mapping software was used to lead the team through a series of exercises to group the requirements into major headings and develop subgroups. All requirements were documented in a mind map within the appropriate group or sub-group. The resulting Map gave the team a “picture” of what the system would do.

After examining the map over the following days and weeks, the team added requirements that they hadn’t thought of during the initial sessions. Having the pictorial version of the requirements enabled people to easily “see” interactions between requirements that might not have been as evident with some other product requirements definition techniques. Mind Mapping allows one to draw relationships between requirements and describe out they’re related or perhaps in conflict. Conflicting requirements must be resolved. Identifying the conflict in the first place is a major part of the battle.

Performing Product Requirements Definition using mind mapping techniques in a setting like this achieves several key things:

1.  Generates a uniform picture or vision of what the product should be.

2.  Team building across functional areas

3.  Helps to develop and document a complete set of requirements and specifications for the development team to act upon.

4.  Enables the team to quickly identify holes or omissions in the requirements definition.

5.  Reduces the risk that a key requirement of the product will be left out. Said another way, it ensures that customers will be satisfied (or even elated!) with the product when it hits the market.

Mind mapping techniques and software can help New Product Development teams focus their efforts quickly and easily communicate the results of Product Requirements Definition efforts. It keeps everyone on the same page.

 

 

 

Share

New Business Plan for Flying via Private Jets

Thursday, May 10th, 2012

A private jet company is experimenting with a business plan analogous to Netflix. For a monthly rate, you could fly as many times as you want with your own private jet. Check out the article here:

http://travel.yahoo.com/ideas/new-airline-offers-all-you-can-fly-service.html;_ylt=Ala1eA.ELm6FTM1snrOvKyOhpYMA

Share