How it worksSupportPricingFAQ
Resources
BlogBest Practices
About
Talk to usLogin
← Back to the blog

Why innovation programs in large DACH corporations fail: five patterns

August 20, 2026 · 6 min read

Before an innovation program officially fails, it has usually failed twice already: once before the approval, when nobody clarified who the customer is and what they are willing to pay, and once after it, when nobody was looking anymore. This has little to do with the usual explanations (no culture of learning from failure, rigid structures), which admittedly aren't wrong, but are so vague that you can't derive anything from them. And a lot fails: in a survey by the Institute for Applied Innovation Research at Ruhr University Bochum among innovation experts from 1,200 manufacturing companies, only about one in sixteen officially pursued product ideas became a commercial success (the survey is from 2007, though nobody claims the rate would be friendlier today). If you look more closely at the programs that failed, five patterns repeat, and they do so in this order.

The length of a discussion and the degree of clarity it produces are not in any linear relationship.

Pattern 1: False clarity

A project gets discussed for months, and because everyone has discussed it for so long, in the end everyone believes everything has been clarified. But the length of a discussion and the degree of clarity it produces are not in any linear relationship: at some point people get tired, the item gets closed and everyone goes their own way, and a few weeks later it turns out you only scratched the surface and the important questions were left unanswered. This happens especially when there is little data on the table and strong personalities sitting around it, because then factual questions turn into endless opinion battles. Who the customer is, how you reach them, what they are willing to pay, who is responsible for what: in a large corporation, in my experience, none of this sorts itself out. The only thing that really helps is to systematically record what has actually been clarified and validated and what has merely been talked about for a long time.

Pattern 2: Risk quietly becomes a point estimate

In exactly these discussions it is especially hard here to name risks openly, because the answer is then always "validate further", until every risk seems to have disappeared. You always keep some residual risk, though, even after the most drawn-out validation. Upper management often doesn't want to accept that, so uncertain numbers are quietly turned into point estimates. And if you show confidence intervals anyway, you come across as unsure, while the colleague with the one clean number is seen as confident and well informed. Yet their project is probably just as uncertain, the risk just isn't spoken out loud.

Pattern 3: The outcome gets judged, not the decision

There is a reason risk gets polished away: failure is judged much more harshly here than elsewhere, and it is judged by the result, even though you should really judge a project by the information that was available at the time of the decision. In hindsight you always know better. This way of judging works its way back into planning, because if you know you will be measured on the outcome, you have little reason to write uncertainty honestly into the case. It has to be normal that a program manager can't predict the effect of their initiatives exactly, and that management accepts a defined risk when the numbers are calculated with confidence intervals. And a project that clearly isn't working has to be stoppable without anyone losing face.

Pattern 4: The business case ends up in a drawer

In the way many companies actually operate, the business case has served its purpose once it is approved, it got the sign-off, and it is never opened again. People assume the expected benefit will show up on its own and don't look closely. From the point of view of the individual owner this even seems rational: if you look closely, you can only lose, since the project might not perform as planned, so better not draw attention to it. Yet the real work of the business case only starts after the approval, as the baseline you steer execution against. Without that comparison nobody notices whether the assumptions from back then still hold, and course corrections don't happen, simply because nothing signals that a correction is needed. Most programs, after all, only fail in execution, which is exactly the phase in which nobody is looking anymore.

Pattern 5: Vanity metrics instead of leading indicators

And where there is reporting, it is often the wrong things that get reported. Small problems are hushed up. The metrics that look good get reported, while the real drivers get dropped because they are red. That way exactly the people who would have the power to turn a project around lose sight of it, and in the end it fails suddenly and loudly, when it is too late to change anything.

Tracking that works means identifying the leading indicators, the metrics that are visible early and move the end result the most (when in doubt, always top of funnel too), and using these leading indicators in the forecast to predict the end result. That makes their relevance visible to everyone. And you should know that people game KPIs. The choice of KPIs and how they are calculated should therefore belong to the person with the biggest interest in a correct end result. If the salesperson picks their own metrics, they pick the ones they can push up most easily, regardless of whether that helps the company. That sounds harsh, but it is everyday life in companies and basically human nature.

Does that mean being less thorough?

No. But fast and careless are not the same thing. Even if you like validating, you have a limited validation budget, and you can validate twice as long and still have validated the wrong things. Then you weren't thorough, just slower. The real skill is judging what is worth validating and discussing in the first place. Bayescase, innovation management software, answers exactly that through sensitivity analysis: which assumption moves the result and which doesn't.

And if you don't want to wait for culture change from the top, you can start today by calculating and showing confidence intervals. Most people understand them fairly quickly, as long as you can explain where the uncertainty comes from. The harder part is the comparison with the project next door that shows up with a single number: the skill is to show that it is just as uncertain, probably even more so, and is only keeping quiet about its risk.

Frequently asked questions

Why do innovation programs fail in large companies?
Rarely because of a lack of innovation culture. Five patterns repeat: important details stay unclear despite long discussions, risks are quietly polished away into point estimates, the outcome gets judged instead of the quality of the decision, the business case disappears into a drawer after approval, and vanity metrics get reported instead of the real drivers. Only about one in sixteen officially pursued product ideas becomes a commercial success.
How can I tell early that an innovation project is going off track?
From leading indicators, the metrics that are visible early and move the end result the most, when in doubt top of funnel. If you use these leading indicators in the forecast to predict the end result, you can see long before the first revenue whether a project is on track. The choice of KPIs should belong to the person with the biggest interest in a correct end result, because people game metrics they get to choose themselves.
How do I deal with uncertainty in a business case?
With ranges instead of point estimates: calculate and show confidence intervals, and be able to explain where the uncertainty comes from. A sensitivity analysis shows which assumptions actually move the result and should therefore be validated, and which discussions you can skip.
How do I find out which patterns show up in our own program?
The easiest way is to go through the phases one by one: how ideas come in, how they are evaluated and decided on, what goals a project gets at approval and whether anyone actually tracks the actuals afterwards. The innovation process check asks about exactly these five phases and takes about three minutes.

Sources

scinexx / Ruhr-Universität Bochum: Survey by the Institute for Applied Innovation Research among innovation experts from 1,200 manufacturing companies. Only about one in sixteen officially pursued product ideas became a commercial success (survey from 2007).

Alex Gutzler

Written by

Alex Gutzler

Founder & CEO, Bayescase

What will your strategy deliver?

In a short conversation we take one of your initiatives and show how an idea becomes a business case with targets and tracking.

Talk to usarrow_forward