Assessment

Innovation Readiness Assessment

Eight questions on whether your innovation effort is structured to produce commercial outcomes: problem selection, portfolio focus, validation, funding gates, experiments, leadership tolerance, scaling and learning.

Innovation activity is easy to generate and easy to admire: labs, sprints, showcases. This assessment ignores the activity and scores the system: how problems are chosen, how bets are funded and killed, and whether anything learned survives.

Last reviewed 3 July 2026 · Free and ungated

Bring independent operator perspectives into this decision

A complimentary first report puts your innovation portfolio in front of operators who have built, scaled and shut comparable ones. The challenge comes back as a confidential report from the Global Board.

Bring independent operator perspectives into this decision

How a client brief works · What you receive

Fixed questions · no AI · nothing stored

Run the scorecard

Answer for how initiatives were actually selected, funded and stopped in the last year, not for the innovation strategy document.

0–39 Low maturity 40–59 Developing maturity 60–79 Moderate maturity 80–100 Stronger maturity How our tools are scored
  1. Problem selection Does innovation start from problems worth solving or from ideas seeking problems?
    • Initiatives start from technologies or executive enthusiasms
    • Problems are named, but chosen for visibility rather than value
    • Effort concentrates on customer or cost problems with sized value at stake
  2. Portfolio focus Is the portfolio a set of deliberate bets or an accumulation?
    • Nobody could list the live initiatives, let alone defend the mix
    • A portfolio view exists, but nothing is ever removed from it
    • Bets are balanced across horizons and pruned on a regular rhythm
  3. Customer validation Is desirability tested with real customers before serious money?
    • Concepts are validated internally, by people paid to like them
    • Customer input arrives after the build, framed as feedback
    • Real customers test willingness to pay or switch before scale-up funding
  4. Funding gates Does money arrive in tranches tied to evidence?
    • Initiatives are funded annually and defended annually, evidence optional
    • Stage gates exist on paper but almost nothing dies at one
    • Funding releases against evidence thresholds, and gates genuinely kill projects
  5. Experiment design Are experiments built to disprove, or to demonstrate?
    • Pilots are designed to succeed and always do
    • Hypotheses are stated, but success criteria flex after the fact
    • Experiments predefine the kill signal and the pass mark before they run
  6. Leadership tolerance What actually happens to teams whose honest experiments fail?
    • Failure is punished quietly, so nothing is ever reported as failed
    • Failure is tolerated officially, but careers say otherwise
    • Well-run experiments that disprove the idea are treated as good work, visibly
  7. Scaling path Is there a route from validated pilot into the core business?
    • Pilots succeed and then orbit indefinitely; the core will not take them
    • Handover happens, but the receiving unit had no stake and starves it
    • The receiving business co-owns pilots early, with budget for the scale-up
  8. Learning discipline Does anything learned outlive the initiative that learned it?
    • Each initiative rediscovers what the last one already paid to learn
    • Post-mortems happen for big failures; insights live in slide graveyards
    • Findings are captured, reused and visibly steer later bets
Reading the score

What the result bands mean

0–39: Low maturity

This is innovation as performance: initiatives chosen for optics, pilots engineered to succeed, and nothing ever killed. The budget is buying morale and announcements, which have value. But the organisation should not expect new revenue from a system with no mechanism for producing it.

40–59: Developing maturity

The vocabulary and structures are in place (portfolios, gates, hypotheses) but the incentives underneath still point the old way: gates that never fire, failure that is officially fine and practically fatal. The system produces motion and consumes credibility, which is a wasting asset.

60–79: Moderate maturity

The system genuinely works: problems are chosen deliberately, evidence gates funding, and honest failure is survivable. The characteristic remaining fault is the last mile: validated concepts queuing at the border of the core business, which has quarterly targets and no reason to adopt someone else's risk.

80–100: Stronger maturity

These answers describe a rare thing: an innovation system with working feedback loops from problem to scale. The exposure at this level is the system's own success criteria: a disciplined machine optimises towards what its gates can measure, and the threats that end companies rarely arrive in measurable increments.

Activity is not the measure

An innovation function can run continuously (sprints scheduled, demos delivered, walls covered in canvases) while producing no commercial outcome whatsoever, because none of that activity requires an idea to ever face a customer, a gate or a P&L. The eight questions here score the parts that create consequence, which are the parts that organisations most often skip.

Scoring and bands

Three answers per question at 0, 5 and 10 points, totalled and normalised to 100 across four bands. The arithmetic is fixed and runs locally; nothing you answer is stored. Score the last twelve months of actual behaviour, and resist the pull of the strategy document.

The kill rate is the tell

If a single number predicts innovation health, it is how many initiatives were stopped by evidence in the past year. A portfolio where nothing dies is not a portfolio; it is a queue of commitments accumulating sunk cost and political protection. Healthy systems kill early, cheaply and without career damage, which is why the funding-gate and leadership-tolerance questions carry the story.

Who this is for

  • Executives deciding whether the innovation function has earned its next budget.
  • Innovation and strategy leads who suspect the machinery is performing rather than producing, and want a structured way to say so.
  • Boards asking why validated pilots never seem to reach the revenue line.

Frequently asked questions

Does a strong score mean we will out-innovate competitors?

It means your system converts effort into evidence and evidence into decisions efficiently. What it cannot guarantee is that you are pointing that system at the right problems. That is a strategy question, and worth independent challenge on its own.

We are a small company without formal gates. Is this relevant?

The disciplines matter more at small scale, not less, because each bet is a larger share of everything. A founder asking "what evidence would make us stop?" before spending is the same question as a gate. The formality is optional; the question is not.

How do we score leadership tolerance honestly?

Ignore the stated policy and trace the people: find the last two teams whose experiments returned a clear negative result, and look at what happened to them next. If nobody can recall a clearly reported negative result, score the question 0. That silence is the answer.

The system can be disciplined and still aimed at the wrong bets.

Bring independent operator perspectives into this decision