Blog Category: Product Development

Your unwillingness to walk away from a losing project degrades your overall ability to win.

510-Exit

Consider two new-product success modes. In Success Mode A you launch a well-protected, premium-priced product. In Success Mode B, you thoroughly search the market segment, but find no unmet needs you can address. So you walk. May not sound heroic, but it’s the only way to ensure enough resources for more Success Mode A. Market Satisfaction Gaps let you distinguish Mode A from Mode B.

More in white paper, Market Satisfaction Gaps

Unlike other areas of business, surprises are welcome when you’re developing new products.

506-Welcome-Surprise

Surprises in quality or cost control are unpleasant. But innovation relies on surprises. Without “non-obviousness,” an invention cannot even be patented. When a previously hidden customer outcome becomes known, the discovering supplier has the luxury of seeking solutions in a competition-free environment.

More in 2-minute growth video #25, Let your customers surprise you

There are many ways to improve product development that are popular… and proven to fail.

thinking and results feedback loop

One is throwing more money at R&D in a Soviet-style arms race. Another is exhorting the troops to do better. An all-time favorite is asking tough project-review questions… but not training teams in the skills needed to find the answers. What if all your teams had the highest possible skills in understanding customer needs? Might this work better?

More in e-book, Reinventing VOC for B2B

Validating hypotheses with customers distorts your entire new product development process.

499-Distorted-Viewpoint

Confirmation bias is the “tendency for people to favor information that confirms their preconceptions or hypotheses, regardless of whether the information is true.” It’s what happens when you take your lovely new-product hypotheses to customers. This systematically distorts data on customer needs… and that can’t be good for innovation, right?

More in 2-minute video at 35. Insist on data-driven innovation

What if your customer’s stakeholders don’t agree with each other?

497-Key Account Blueprinting

According to the authors of The Challenger Customer, “The limiting factor is rarely the salesperson’s inability to get an individual stakeholder to agree to a solution. More often it’s that the stakeholders inside the company can’t even agree with one another about what the problem is.” To overcome this, try Key Account Blueprinting… New Product Blueprinting applied to one large account at a time. This forces stakeholder agreement.

More in white paper, Key Account Blueprinting

The greatest danger in customer interviews is hearing what you want to hear.

492-Selective-Hearing

Your new product development should start where it ends: with the customer. When you take your “pride and joy” hypothesis to customers and ask their opinion, two bad things can happen: 1) They tell you what they think you want to hear. 2) You hear what you want to hear. Start by uncovering their needs, not testing your pre-conceived notions. And be sure to use quantitative interviews to eliminate confirmation bias.

More in 2-minute video at 35. Insist on data-driven innovation

Why take a “leap of faith” when you could take a leap of confidence—more quickly and cheaply?

487-Leap-of-Faith

Lean Startup methodology refers to “Leap of Faith Assumptions,” and recommends testing assumptions with customers at the first opportunity. For B2B, this “first opportunity” to learn comes before a prototype is created… through VOC interviews to mine the foresight of knowledgeable customers. Don’t miss this B2B adjustment to Lean Startup.

More in white paper, Lean Startup for B2B (page 6)

Got cool technology? Great. Just test it silently with customers.

486

Avoid “technology push.” But should you just leave your technology quivering on the lab bench? Hardly. Conduct customer interviews without mentioning your technology. If customer outcomes match your technology… wonderful! Otherwise, look for different technology (for this market), or look for another market (for this technology).

More in 2-minute video at 21. Give your hypotheses the silent treatment

Validating hypotheses with customers may have been OK once. When fedoras were worn.

482-Fedora

In many areas of life, there’s the “old way” and the “new way.” Does your company still develop “hypotheses” internally, and then meet with customers to validate them? This can lead to confirmation bias for you and stifled yawns for your customers. In the “new way,” you start by uncovering customer needs, not by internally “ideating” your solutions.

More in e-book, Reinventing VOC for B2B

Great product development is always preceded by great market segmentation.

476

Three conditions must be met: 1) A market segment (cluster of customers with similar needs) is clearly defined. 2) The segment is worth winning in terms of size, growth, profit potential, etc. 3) The segment is winnable, i.e., it’s not defended by a well-entrenched competitor. Overlook these conditions and you’ll waste resources. Great market segmentation is key to successful innovation.

More in 2-minute video at 16. Segment by markets for innovation

Lean Startup is fine for B2B… but don’t skip this extra “Learn” step.

470-Learning-before-Hypothesizing

The “Build-Measure-Learn” cycle in Lean Startup begins with a hypothesis, and is great for B2C. End-consumers can seldom tell you what will amuse them or increase their sense of self-worth. But knowledgeable B2B customer can predict their desired outcomes. So start with a “Learn” pre-step. Customers will tell you all you need if you know how to ask.

More in white paper, Lean Startup for B2B (page 3)