Red Zen Marketing

It's one of the most common mistakes I've seen new product development teams make, time and again.

Regardless of the firm's industry or category, or whether it's a physical product or software, all too often the team in charge of a bringing a new product to market lose their way--they lose touch with the customer.

Development teams encounter a single problem or focus on a single dimension of the product and begin to get wrapped around the axle on that area. Slowly the initial impetus behind development of the product or service recedes into the background; the customer need/opportunity--the Voice of the Customer--becomes obscured by the deliberations and problem-solving that begin to consume the development team. As this occurs, the concentration of attention moves inward. Focus becomes parochial, with thinking centered around what is best for the firm or on the barriers to making changes. New constraints become givens for the project, even if the project started as an innovation-focused project to reinvent the firm and bring grand new opportunities to bear. I call it the molasses effect.

Examples of subtle obstructionist mindset shifts that occur:
"We want it to look entirely different but It has be made on our existing line."
"This is the best market opportunity but we have to address it without undermining our current channel."
"We know it needs to have those features, but we have to get to market by X so those will have to wait."
"There might be better technologies to do X/Y, but we don't have people who understand those, and besides, we know how to do Z."

Now, I know what some of you are thinking. Yes, I can also think of examples where the raising of those exact objections was warranted, and there is a long story behind each one. Granted, But for each of those exceptions, there are many, many more times that these phrases were overheard in cases where they were nothing but excuses for sticking to the status quo. And, often the reason is fear.

So. How is this best avoided?

1. Use a cross-functional team. Don't allow the development process to proceed to far being run by any one group--whether engineering, R&D, software development, marketing, manufacturing, etc. As appropriate, gather a group from the relevant areas of the firm to participate on the team, led by a strong project manager who does not dictate product outcomes, but guides the project progress and accountability, and let ideas flow against the project timeline.
   
2. Ensure that the product development team--those in the trenches on the team, actively involved in weekly meetings--are closely involved in understanding end customer requirements, desires, frustrations, & needs. I happen to be biased toward use of the Voice of the Customer methods that have proven their efficacy over and over again, but successful products come out of other customer intimacy/research methods as well. 
3. Use Personas in the development process, to keep the target segment customer clearly in the mind of the development team. Personalizing the customer in this way is incredibly powerful, whether the product is a window, an electric fan, a pizza buffet, an online banking service, or an iPhone software app. 
4. Open your mind to partnerships. The best solution may involve working with other firms. Novel solutions to difficult problems in todays connected, global marketplace need not be all resolved "in house". Think "who has the pieces to complete this puzzle?" and take the step of approaching and asking for ideas or assistance. Think win/win. Having a smaller piece of a huge pie is usually a good thing. There's a reason most consumer electronics firms (think Apple, Motorola, Hewlett Packard, etc.) don't actually assemble most of their products themselves, but rely on partners like Flextronics and HTC to do this for them. When siding maker NuCedar ran into a difficulty with paint retention, they went directly to Sherwin Williams for help, and found a willing partner who helped them enter the market with a jaw-dropping 1400-color pallet, dwarfing vinyl siding choices and offering a UV reflective finish to reduce summer heat absorption.
   
   
   
   
   
5. Look to other industries for solutions. Often, others have solved the problem you are up against in a slightly parallel industry for a different reason. It may take some research (luckily there's lots of great tools for that these days!) but it will be out there, perhaps written about in a different industry's trade journal. Try to define the problem on a different level when you search.
   
6. Perhaps it should have been listed first, but this final recommendation comes straight from the second of Stephen Covey's Seven Habits: Start with the End in Mind. In this case, as you move forward in development, the team should always be doing their best to be visualizing the characteristics of the ideal product/solution. These are now 'how' aspects (not features), but are the benefit aspects of the product or service. "It will let me unlock my car while laying in bed on a cold morning" is a visualization of the ideal product outcome. As product development proceeds, this skeletal vision should become fleshed out with more benefits and aspects surrounding the core benefit to the customer, meeting the primary need. Keeping this in mind focuses development in a powerful way, and is similar in many ways to the AGILE method of software development in which the most important/necessary/core aspects of the software are developed first, quickly, in order to create constantly working code. Then, additional features are added to this core, always being sure to test the operating prototype against customers' needs to validate its alignment. By extension, this idea of frequent prototyping also helps to keep things on track, and is a corollary to this same idea, as it is the embodiment of keeping the 'end in mind'.
   

If you have more suggestions for keeping barriers to innovation from getting in the way and stifling true development progress, leave your ideas in the comments here. I love to hear your experiences as well!

And, yes, if you're firm is struggling in this area now, I can help with that.