TL;DR Calling innovation initiatives “bets” is useful only up to a point. It reminds leaders that outcomes are uncertain, but it can also imply that management’s main task is to choose the right ideas at the beginning and wait to see which ones win.
Innovation governance has a more important job. Every stage of investment should make the organization better able to decide what to do next. The relevant return before revenue is not another prototype, business case, or completed milestone. It is greater Decision Readiness: clearer assumptions, stronger evidence, credible rival explanations, and an explicit basis for scaling, pivoting, stopping, or deferring the next commitment.
The free section provides the complete diagnosis. The paid section turns it into a one-page Decision Readiness Gate, applies it to a funding decision, and establishes a repeated practice that improves judgment across the portfolio.
Innovation portfolios are often described as collections of bets.
The metaphor has value. It reminds executives that no amount of analysis can guarantee a successful outcome. Markets move, competitors respond, technologies change, and customers behave differently from what a business case predicted.
But the metaphor can also distort the work of innovation management.
A bet sounds like a decision made once. The organization chooses an opportunity, places capital behind it, and later discovers whether it won or lost. Governance then becomes a search for better bets: better ideas, better forecasts, better selection criteria, or leaders with better instincts.
Innovation does not unfold that way. An initiative is a sequence of decisions made as new information becomes available. The first commitment should create the conditions for a better second decision. The second should improve the third. Capital should increase only as the organization earns a stronger basis for committing it.
The central question is therefore not whether management picked a future winner at the beginning.
It is whether each investment made the next decision better than the previous one.
Outcomes are unreliable teachers
When an innovation succeeds, the original decision is usually remembered as insightful. When it fails, the decision is recast as misguided. Annie Duke calls this tendency to judge a decision by its outcome “resulting.” Outcomes reflect both decision quality and luck, so a good process can produce a bad result while a weak process occasionally succeeds.[1]
Formal decision analysis makes the same distinction. Decision quality depends on how well the problem was framed, which alternatives were considered, what information was available, how uncertainty was assessed, and whether the choice was consistent with the decision-maker’s objectives at the time.[2] None of this guarantees the desired result.
Innovation adds a deeper difficulty. Frank Knight distinguished measurable risk from uncertainty, where probabilities cannot be estimated reliably because the relevant knowledge does not yet exist.[3] Early innovation decisions often concern exactly these unknowns: whether the problem matters enough, whether behavior will change, who controls the purchase, whether the technology can perform in context, and whether the economics can work.
Detailed forecasts do not convert these uncertainties into facts. They often make untested assumptions look precise.
Once the outcome is known, hindsight makes the path appear more predictable than it was.[4] Outcome bias then leads people to evaluate otherwise identical decisions differently depending on whether they produced favorable or unfavorable results.[5] The successful initiative acquires an origin story of foresight. The unsuccessful one fills with warning signs that supposedly should have been obvious.
An organization that learns only from winners and losers therefore learns too late—and may learn the wrong lesson.
Project progress can hide decision stagnation
Because outcomes take sometime months or years to appear, organizations look for earlier signals of progress. They review whether the team completed interviews, produced a prototype, launched a pilot, met its milestones, or stayed within budget.
These are legitimate project-management questions. They are poor substitutes for innovation governance.
A prototype can be completed without testing the assumption most likely to destroy the opportunity. Fifty interviews can produce little more than favorable comments if the sample, questions, and interpretation protect the original idea. A pilot can demonstrate technical feasibility while revealing nothing about adoption, willingness to pay, or the operating model required to scale.
Activity has increased. The organization’s ability to decide may not have changed.
This confusion is reinforced by the different economics of exploration and exploitation. James March described exploitation as the refinement of what is already known and exploration as the search for new possibilities.[6] Established operations can be evaluated through delivery, efficiency, revenue, and variance from plan. Early innovation cannot, because the assumptions that would make those measures meaningful are still being investigated.
When both are governed through project progress, exploration begins to imitate execution. Teams produce plans and artifacts that make the initiative look increasingly real. Momentum grows faster than evidence, and stopping becomes harder precisely when the organization should still be preserving flexibility.
Stage gates should govern commitments, not presentations
Stage-Gate was not originally designed as a bureaucratic checklist. Cooper’s model divided new-product work into stages that generate information and gates that decide whether further resources should be committed.[7] Later versions emphasized adaptability, different pathways, spiral development, and “gates with teeth,” while warning against rigid and over-bureaucratic implementation.[8]
The problem is not necessarily Stage-Gate theory. It is what many gates reward in practice.
Teams arrive with polished slides, prototypes, roadmaps, financial projections, and evidence summaries. Gatekeepers assess whether required deliverables exist and whether the presentation supports continuation. The initiative receives another tranche because it appears to have progressed.
Yet the governance question is not whether the team has been busy or persuasive. It is whether the evidence generated since the previous gate justifies exposing more capital, credibility, and organizational energy.
Discovery-Driven Planning made assumptions explicit and treated plans as hypotheses rather than facts.[9] Real-options reasoning showed why small, staged commitments can preserve the right—but not the obligation—to invest more after uncertainty has been reduced.[10]
Both point toward the same principle:
Knowledge should increase before commitment increases.
That principle needs an operational condition at the gate. I call it Decision Readiness.
Decision Readiness is the degree to which decision-relevant uncertainties have been made explicit and investigated with signals sufficient to justify a specified next commitment.
It does not mean that uncertainty has disappeared. Nor does it promise a successful outcome. It asks whether the organization has reduced the avoidable ignorance relevant to the decision before it increases its exposure.
What Decision Readiness requires
An initiative is ready for its next decision when governance can see six things clearly:
The decision: What commitment is being requested now—not the eventual ambition, but the next release of money, people, access, or reputation.
The theory of value: Why this initiative is expected to create value, for whom, and through which change in behavior or economics.
The critical assumptions: What must be true for that theory and the next commitment to remain defensible.
The evidence change: What the organization knows now that it did not know at the previous gate, including contradictory observations.
The decision thresholds: Which findings support scaling, pivoting, stopping, or deferring.
The proportional commitment: Why the size and reversibility of the next tranche are appropriate to the evidence available.
If these conditions are absent, another deliverable will not repair the decision. The project may be ready for its next activity without being ready for its next investment.
This also changes how stopping should be interpreted. If a €40,000 discovery stage produces credible evidence that a planned €3 million program should not proceed, nothing has launched and no revenue has been created. Yet the stage may have generated substantial governance value by preventing a much larger, weakly supported commitment.
The return is not failure avoided with certainty; that claim would be impossible to prove. The return is a materially better capital decision made while the downside was still contained.
The question every gate should ask
The most revealing gate question is not:
Did the team deliver what it promised?
It is:
Knowing what we know today, would we make the same next commitment again?
If the answer is yes, governance should be able to show which evidence supports the commitment and why the next tranche is proportionate.
If the answer is no, the organization should not conceal that learning behind project momentum. It should pivot, stop, or redefine the commitment.
If the evidence is insufficient, it should defer the decision through a bounded investigation with a date, cost ceiling, and explicit learning objective—not extend the initiative by default.
Innovation governance cannot remove luck. It can reduce how much capital is exposed to assumptions that could have been investigated earlier.
That is why innovation management is not primarily about making better bets. It is about earning better decisions before each larger commitment is made.
If this diagnosis is useful, the paid section provides the application: a Decision Readiness Gate you can use on one live initiative within the next seven days.
If someone on your team decides which innovation initiatives earn more money, forward this to them and ask one question: what evidence should a project have to earn its next decision?
The Decision Readiness Gate
Use this gate before approving a new tranche for an initiative whose commercial outcome remains uncertain. It is not a project scorecard. Its purpose is to expose whether the proposed commitment is supported by decision-relevant evidence.
Start with one real decision. Do not apply it to the portfolio in general.
