What Does It Mean for an Innovation to Fail?

Failure is not “we didn’t file a patent” or “the demo didn’t wow the room.” An innovation attempt has failed when the people it was meant to serve do not adopt it, do not value it above what they already use (including doing nothing), or do not stick with it once the project team leaves.

That standard explains a lot of confusion. A clever prototype can be a successful invention and a failed innovation at the same time. A launch can look successful on day one and still fail if behavior snaps back to the old path. For how invention, innovation, and lasting impact differ, see 7 Differences Between Invention, Innovation, and Impact.

Why Do Innovation Failure-Rate Statistics Mislead?

You will see confident percentages — often very high — attached to “most innovations fail” or “most new products fail.” Treat them carefully. Studies define failure differently: missed revenue targets, discontinued SKUs, pilots that never scale, or startups that shut down. Those are not the same event, and they are not always comparable.

The useful claim does not need a magic number. Most innovation attempts do not become widely adopted solutions. The reasons are repeating and observable. Fix those, and you will outperform a team that only argues about the statistic.

What Are the Main Reasons Innovations Fail?

1. They Solve the Wrong Problem

A sponsor’s favorite idea gets built before anyone has named the job a real person is trying to do. The result can be novel and still unwanted. Tell: nobody can say, in one sentence, whose life gets better and how you would know.

2. They Skip Evidence

Teams build the full thing to “see if it works,” instead of running a test that could falsify the bet while it is still cheap. Applause in a demo is not evidence of adoption. Tell: the first time customers meet the idea, the budget is already spent.

3. They Never Leave the Pilot

The pilot renews. The deck stays green. Nobody makes a kill-or-scale decision. That is activity, not innovation. I describe the surrounding costumes in 7 Types of Innovation Theater, and the stall after a promising pilot in 9 Reasons Digital Transformations Stall After the Pilot. Tell: “we’re still learning” after the learning questions have already been answered.

4. The Change Isn’t Worth It

Adoption fails when the new way costs the user more effort, status, risk, or time than the old way — and nobody redesigned that tradeoff. People are not resistant by nature. They are often rational. Tell: training is funded and the job design is not.

5. The Old Path Still Wins

Incentives, metrics, habits, and the legacy process keep rewarding the behavior you said you were replacing. A sleek new tool loses to the spreadsheet that still determines the bonus. Tell: “we launched” while the old scorecard is unchanged.

6. Nobody Owns It After Launch

The project team celebrates and leaves. There is no owner in the business for adoption, exceptions, and the slow work of making the new way stick. For the stages organizations skip between insight and scale, see 6 Stages Most Organizations Skip Between Insight and Scale. For how a real process carries a bet past launch, see What Is the Innovation Process — and What Are Its Stages? Tell: success is reported on go-live day.

How Can You Tell an Innovation Is Heading for Failure?

• The problem statement is the solution in disguise.
• There is no kill criterion written down.
• The only evidence is internal enthusiasm.
• Customers must do unpaid homework the team never tried themselves.
• The old process, metric, or vendor is still the easy path.
• No named person owns adoption after the project ends.
• Leaders ask for more ideas instead of fewer, better bets.

Good ideas die this way too — not only bad ones. For the patterns that kill work before it ever ships, see 8 Ways to Kill a Good Idea Before It Ships.

What Should You Do Instead?

1. Frame the problem before you fund the build. Name the person, the job, and the evidence.
2. Test cheaply, and be willing to stop. Evidence before affection.
3. Make the new way easier than the old way for the person who has to change — not only for the company.
4. Change the metric or incentive that still pays people to stay on the old path.
5. Name an adoption owner before development spend gets large, and keep them after launch.
6. Match the type of bet to your capacity. Most failures are not “we weren’t disruptive enough.” They are “we asked the organization to absorb a change it was not designed to finish.” See What Are the Different Types of Innovation? and How Do You Build a Culture of Innovation?

Stop collecting ideas. Start removing the reasons a good one cannot be adopted.

FAQ: Why Innovations Fail