I believe it should be this: Leave your business stronger than you found it. It doesn’t matter how good those soon-forgotten quarterly financial results were. If the leader weakened the business by degrading its ability to grow—through either neglect or raiding capabilities for short term gain—that leader failed. I’m puzzled that boards of directors and executive teams allow business leaders to perform well in the short term while damaging the long-term health of their business. Very odd.
More in article, B2B Organic Growth: Moving to earned growth
Do your new product development teams deal only with facts? Or are “factoids” interspersed, cleverly hiding among the facts? The Oxford English Dictionary defines a factoid as “an item of unreliable information that is repeated so often that it becomes accepted as fact.” Better to clearly identify and separate your assumptions from facts at the onset of your project… and rigorously investigate the assumptions until your project is based on facts alone.
More in video De-risking Transformational Projects
We see three areas where leaders can have a greater negative impact on innovation than positive: 1) organizational friction (travel bans, spending freezes, hiring delays, excessive re-orgs, etc.) that slow innovation to a crawl, 2) spreading too few resources over too many projects so that nothing moves briskly, and 3) short-changing the front-end of innovation, so that a clear picture of customer needs is lacking. Companies pay a heavy price for keeping such leaders in place.
More in article, Accelerate New Product Innovation
Research shows that it’s often “game over” for your product if a competitor’s product has a better Google search ranking. The key is good search engine optimization (SEO), and the key to that is predicting which keywords your prospects will search for. Here’s a tip: In your front-end voice-of-customer interviews, capture customers’ comments verbatim. Then use their language—which is unlikely to change—in your SEO strategy.
More in article, B2B Product Launch: How to get it right
Many refer to the new-market, new-technology quadrant of the Ansoff matrix as the “suicide quadrant,” given its high-failure rate. This need not be the case. With good planning, you can spot potential “landmines” much earlier, and take steps to either kill your project quickly, redirect it, or accelerate success. Do this by rating risk factors for impact and certainty… and then communicate your progress through Certainty Matrices.
More in article, How to Thrive in the “Suicide Quadrant”
“Proven right” breeds confirmation bias; “be right” inspires a search for truth. In new product development, “proven right” seeks to validate the supplier’s ideas; “be right” explores customers’ worlds seeking what others have missed. “Proven right” results in squandered R&D spending and missed opportunities; “be right” in delighted customers, premium pricing, and pleasant financial review meetings.
More in e-book, Leader’s Guide to B2B Organic Growth
If you want profitable, sustainable B2B growth, you must develop "growth muscles." You wouldn’t try to climb El Capitan without climbing skills. Yet many business leaders proclaim double-digit growth plans year after year, but do nothing to build the capabilities needed to succeed. ... Read More
Can you eliminate most commercial risk when developing B2B new products? Yes… by building a Certainty Time Machine. Once you start the development stage, you should primarily be dealing with technical risk, not commercial risk. ... Read More
Imagine you just launched your new product and the market responded with… one big collective yawn. Was it a poorly orchestrated launch? Perhaps, but it’s more likely your launch was doomed a couple of years earlier by poor front-end work. Our research shows five of six B2B product development teams lack a clear understanding of market needs before conducting B2B-optimized VOC. Without this insight, your launch might be putting lipstick on a pig.
More in article, B2B Product Launch: How to get it right
What’s the net present value of accelerating the launch of a $5 million revenue-per-year product by one month? About $80,000… or $4000 per business day. Yet we often hinder teams’ progress with organizational friction: travel bans, spending freezes, hiring delays, new assignments, re-organizations, new initiatives, frequent changes in strategy. Consider these actions carefully lest you turn exciting innovation into a mind-numbing slog.
More in article, Accelerate New Product Innovation
During the Vietnam war, the US was still using its cold war approach of “problem as given”… applying prescribed responses for a long list of scenarios. This was a disaster in the face of evolving threats. Now their protocol is “problem as understood”… developing solutions only after the problem is well defined. Is your company using “cold-war innovation,” or does it place a high priority on learning what customers truly want before developing products for them?
More in e-book, Leader’s Guide to B2B Organic Growth
In new product development, keep your mind open to all customer needs before converging on your solutions. Your brain works better this way. It’s why we don’t “judge” ideas during brainstorming. It’s why you like digital photography better than film: You take as many shots as you like (diverge) and later pick the best (converge). When it comes to customer needs, take lots of shots so you can focus on the best later.
More in e-book, Reinventing VOC for B2B
The difference between speed and velocity is that only velocity has a direction associated with it. Many in business are focused on going as fast as they can… in any direction. Avoiding solid front-end-of-innovation work because you want to develop your new product faster is a prime example. Sure, you launched your product quickly… but no one bought it, because you failed to first understand customers’ needs.
More in e-book, Reinventing VOC for B2B
A project landmine is something that blows up budgets, schedule and reputations. No one steps on one they can see. So why don’t we look for them harder and earlier in a project life? Because we’ve been conditioned to think that killing our project equates to failure. Instead, we should identify areas of uncertainty as early as possible. Celebrate when you kill your own project swiftly… and celebrate when you try hard and are unable to kill it.
View video, De-risking Transformational Projects
