Often, at conferences or during client engagements, we get asked what the single most important KPI in Innovation Accounting. Usually, the question behind the question is this:
“What is the one metric a CFO will actually care about?” Or put differently:
“What KPI ensures the innovation department is not seen as a Mickey Mouse function or just another cost center?”
Our answer is always the same: there is no single KPI that can measure innovation on its own. Companies need a proper Innovation Accounting dashboard made up of several indicators—or at the very least a minimum viable Innovation Accounting system—if they are serious about making innovation a repeatable and scalable capability.
That said, one of our favorite KPIs is “Cost of Failure.”
It is one of the richest indicators in Innovation Accounting because of how many organizational truths it reveals. In our view, it is as fundamental as NPVI, innovation ROI, or any top-line growth metric.
Whenever they hear “Cost of Failure”, most people think it’s a pure financial metric. In reality, it goes way beyond that. So here’s what companies can learn by measuring and tracking “Cost of Failure” over time.
It shows whether your governance actually works
A high cost of failure usually means weak ideas are allowed to survive for too long.
In many companies, stage-gate processes are designed around templates, presentations, and stakeholder alignment rather than evidence of actual market need. Teams learn how to clear gates instead of learning how to validate assumptions.
But eventually products hit the market, and at that point teams can no longer sugarcoat reality. Customers either find the product useful or they don’t. No amount of internal storytelling changes that.
And the longer organizations spend convincing themselves that a weak idea still has potential, the more costs accumulate. Eventually those costs land on the CFO’s desk when she starts asking a very simple question:
“How much have we invested into innovation, and what has it returned in terms of growth?”
This is exactly where “Cost of Failure” becomes powerful. It reveals how long poor ideas are allowed to continue before evidence finally catches up with them.
Once clearer decision points tied to evidence are introduced, teams tend to act earlier and with more confidence. A reduction in “Cost of Failure” becomes a strong signal that governance is finally supporting learning and evidence over opinions and gut feel. So if you want to improve your governance track “Cost of Failure” over time and benchmark.
A few years ago, we worked with a large media company that wanted to improve how new new digital products were governed. Like many organizations trying to improve growth, the first KPI we looked at was “Time to Market.”
And it helped—but only partially.
“Time to Market” told us how quickly ideas moved into development. It did not tell us whether the organization was making better decisions once uncertainty started showing up. That’s why we introduced “Cost of Failure.”
After redesigning the governance framework, introducing metered funding, and creating clearer validation checkpoints, the company reduced its “Cost of Failure” by around 40 percent.
It shows whether you have a real metered funding model
The metric also exposes how money is being allocated. Many companies fully fund ideas from day one based on little more than a polished pitch deck filled with assumptions. Once that happens, teams naturally consume the full budget allocated to them. And when the initiative eventually gets stopped—as most innovation initiatives do (75%)—the upfront investment heavily inflates the “Cost of Failure.”
By introducing true metered funding tied to evidence and validation, organizations reduce unnecessary exposure and improve capital efficiency.
“Cost of Failure” becomes a practical way to see whether the company is truly funding experiments—or simply financing large projects upfront and hoping for the best.
It helps set realistic goals for innovation investment and innovation ROI
Without understanding “Cost of Failure,” companies struggle to have realistic conversations about innovation investment.
Whether you are discussing expected innovation ROI with the CFO starting from budget she already committed or trying to define how much investment is required to achieve a certain level of growth, “Cost of Failure” becomes a critical metric for innovation goals setting and budget planning.
This is why “Cost of Failure” sits at the center of Innovation Accounting. It directly influences how companies think about portfolio size, investment levels, and expected returns from innovation activities.
It shows whether your culture can handle bad news
High “Cost of Failure” often reflects a deeper cultural problem. Teams hesitate to act on negative evidence because shutting projects down can feel politically risky or personally damaging. Sometimes people continue investing simply because they fear what failure might mean for their careers.
Making “Cost of Failure” visible changes those conversations.
Teams become more comfortable surfacing weak signals earlier and acting on them faster. In that sense, the metric becomes a practical indicator of psychological safety—not in theory, but in day-to-day decision making.
From a leadership perspective, it reveals whether the organization has created an environment where stopping ideas is seen as responsible behavior rather than personal failure.
It reveals gaps in (experimentation) skills
Sometimes projects continue not because governance is weak or because culture discourages stopping, but because teams simply lack the skills required to run effective experiments.
If teams do not know how to test assumptions properly, they generate weak evidence. And if decision-makers (Venture Board) lack the skills to interpret that evidence correctly, poor ideas continue moving forward.
A consistently high “Cost of Failure” can therefore be a useful signal that the organization needs stronger experimentation, discovery, and evidence-based decision-making capabilities.
It shows whether teams are actually following the process
Most companies have some form of innovation process documented somewhere. The harder question is whether teams actually follow it.
“Cost of Failure” makes that visible.
When the number remains high, it often means teams are skipping validation steps, committing too early, or progressing ideas before answering the questions most relevant to that stage of maturity. When the metric starts dropping, it is usually a sign that experimentation loops, evidence gathering, and governance processes are finally working as intended.
It helps leaders shift from picking winners to funding experiments
One of the most interesting side effects of tracking “Cost of Failure” is the shift it creates in leadership mindset. Initially, most leadership conversations focus on trying to identify winning ideas early.
But once leaders understand the economics behind “Cost of Failure,” the conversation changes. The focus shifts away from prediction and toward designing portfolios of smart experiments.
The metric makes uncertainty financially visible. And once leaders see how expensive it is to be wrong too late, they become much more interested in learning earlier.
It makes the cost of learning visible
Of course, not every failure is truly a failure. Many initiatives generate customer insights, technical capabilities, or market understanding that improve future products and future decisions.
But from a CFO’s perspective, if an initiative does not generate measurable ROI, it will still be categorized as a financial failure. That tension is important to acknowledge.
This is exactly why “Cost of Failure” matters so much in Innovation Accounting. It creates a bridge between the language of experimentation and the language of finance. It allows organizations to discuss learning in economic terms rather than treating innovation as something impossible to measure.
Because in the end, the real question is not how often companies fail. It is how much it costs them to learn—and how effectively they turn that learning into future growth.
This article was originally posted on the OUTCOME Blog
