Two organizations run innovation assessments in the same month. Both get scores back. Both leadership teams look at the results, nod, and start planning capability investments. Six months later, neither organization has improved its innovation output.
The problem, in both cases, was not the score. It was the question. One organization used a maturity model when it needed a readiness assessment. The other ran a readiness assessment but treated it like a maturity benchmark. The data was accurate. The interpretation produced no useful action.
Innovation maturity and innovation readiness are related concepts that answer different questions. Using the right one, in the right order, is what determines whether an assessment leads to change.
Know where you stand before you invest in innovation capability
I run a structured readiness assessment with leadership teams — identifying the binding constraints before you decide how to build capability. 25+ years of pattern recognition across 50+ companies.
What innovation readiness measures
Innovation readiness answers a binary question: are the prerequisite conditions for innovation in place?
The Innovation Readiness Assessment I use evaluates nine dimensions across three levers — leadership support, organizational design, and innovation practice. A low score on any of the critical dimensions is not just a gap to improve. It is a blocker that prevents other dimensions from working.
Consider a company that has excellent innovation tools and a well-trained team. If their innovation budget gets reallocated every time quarterly numbers disappoint, the tools and skills produce nothing. The readiness condition (protected resources) is missing. That missing condition blocks the value from everything else.
Readiness has a binary quality in this sense: if a critical dimension is absent, it does not matter how strong other dimensions are. The weakest link determines what is possible. This is different from maturity, where every dimension improves continuously and there is no single condition that blocks everything else.
Readiness is also a prerequisite, not a destination. You do not become “ready” and then stop. Organizational conditions shift. Leadership changes. Budgets get restructured. A company that scored a 4 on resource protection last year may score a 2 this year after a CFO change. Readiness requires regular reassessment because the conditions it measures are not stable.
Who should use a readiness assessment:
- Leadership teams before investing in a major innovation program
- Organizations where innovation programs keep failing despite genuine effort
- Companies evaluating whether to hire an innovation leader or bring in external expertise
- Any organization that wants to identify the binding constraint before investing in capability
What innovation maturity measures
Innovation maturity answers a different question: how advanced and sophisticated is your innovation practice?
Maturity models assess how systematically an organization manages innovation. They typically cover: how structured the innovation strategy is, how consistently the ideation process works, how well innovation projects are governed, how effectively the organization captures learning, and how reliably it scales successful innovations.
Maturity is a continuous scale. There is no point at which you stop improving — higher maturity means more systematic, more efficient, and more consistently productive innovation practice. A Level 2 organization has defined some processes. A Level 4 organization has integrated, measured, and continuously improves those processes.
Maturity assessment tells you how good you are at a thing, not whether the conditions exist for that thing to work. A manufacturing company might score Level 3 on innovation process maturity — meaning it has documented processes, tracks progress, and reviews results. But if the incentive system still punishes experimentation, Level 3 process maturity will not produce better innovation outcomes. The process is there. The culture blocks it.
Who should use a maturity assessment:
- Organizations where readiness foundations are in place and leadership wants to track capability development
- Companies that have addressed their critical readiness blockers and want a benchmark for improvement
- Leadership teams that want to compare their innovation capability against external benchmarks
- Organizations with multiple business units that want to understand where capability is stronger and where it is weaker
Side-by-side comparison
| Innovation readiness | Innovation maturity | |
|---|---|---|
| Core question | Can we start? Are the conditions in place? | How advanced are we? How good is our practice? |
| Logic | Binary: missing critical conditions block everything | Continuous: every dimension can always improve |
| What it finds | Specific blockers that prevent innovation from working | The sophistication level of existing innovation practice |
| Best used when | Before investing in capability; when programs keep failing | When foundations are in place; to track improvement over time |
| Output | Binding constraints to address in priority order | Maturity level by dimension; benchmark vs. best practice |
| Time horizon | Now: what is blocking us today | Over time: how are we developing our capability |
| Primary audience | Leadership team (they own the conditions) | Innovation leaders and program managers |
The diagnostic sequence: readiness first, maturity second
The right sequence is not a matter of preference. It follows from what each assessment produces.
A readiness assessment tells you whether the organizational conditions allow innovation to produce results. If critical conditions are missing, this is where to start — because no amount of capability improvement will matter until the conditions are right.
A maturity assessment tells you how to develop capability once the conditions are in place. Using a maturity model before fixing readiness blockers is like training a sales team when there is no product to sell. The training might be excellent. The conditions do not allow it to produce results.
I have worked with organizations that ran a maturity assessment, scored themselves at Level 2, and invested six months in bringing their process maturity to Level 3. At the end of those six months, their innovation output had not improved. Not because the process improvement was wrong, but because the incentive system still made volunteering for innovation projects a career risk. The maturity improvement had no effect because the readiness blocker was still in place.
The diagnostic sequence:
Step 1: Run a readiness assessment. Identify the binding constraints. Are they in leadership support, organizational design, or innovation practice?
Step 2: Address the binding constraints. The order matters. Leadership support first, organizational design second, innovation practice third. This sequence is not arbitrary — higher-order conditions enable lower-order changes.
Step 3: Run a maturity assessment. Now that the conditions are in place, measure how sophisticated your innovation practice is and where to invest in capability development.
Step 4: Track maturity improvement over time. Use the maturity assessment annually to measure progress and identify the next capability frontier.
A practical example
An industrial equipment manufacturer assessed their innovation maturity and scored Level 2 across the board. The assessment recommended investments in: ideation process improvement, innovation portfolio management tooling, and innovation skills training.
Before making those investments, I ran a readiness assessment with the leadership team. What it found: the innovation budget had been reallocated twice in the past three quarters. The innovation team had no formal access to customer relationships controlled by the sales organization. The incentive system evaluated everyone on quarterly operational metrics with no innovation-specific criteria.
The maturity recommendation was technically correct. The organization’s innovation processes were unsophisticated. But investing in process maturity when the budget was unstable, customer access was blocked, and nobody was evaluated on innovation outcomes would have produced a more sophisticated process for producing no results.
We addressed the readiness blockers first: committed the budget at board level, created a formal protocol for innovation team customer access, and designed separate evaluation criteria for the six people working full-time on innovation. Then we invested in process maturity. Twelve months later, both the readiness score and the maturity score had improved — and so had the number of experiments reaching customer validation.
