Maturity InsightsThree scores, two gaps
Glass Ceiling Index = Capacity minus Ceiling. Conversion Gap = Ceiling minus Conversion. Chips show Low, Moderate or High; numeric indices come once enough diagnostics exist to benchmark against.
The Healthy Executor
Capability, leadership and execution all working
Rare. Your constraint is ambition, not capability.
Everything is functioning. Most organizations that score here have either done deliberate work to get there or haven't answered honestly. Assuming it's real, the question is no longer whether you can, but what for. The failure mode from here is complacency, and it is invisible from the inside.
Who they are
- Capability leadership reports at or one step below the executive table
- Enterprise data has named owners, not committees
- Multi-year funding, not an annual project scramble
What they do
- Reassess maturity on a cycle, not when something breaks
- Retire capability that no longer earns its place
- Publish decisions, not just dashboards
Three questions for your next leadership meeting
- What are we capable of that we haven't yet decided to attempt?
- Is this true across the enterprise, or only in the part we can see?
- What would a second, less optimistic respondent have scored?
The Exhausted Transformer
Everything works except the people carrying it
You are changing faster than your organization can absorb.
Capability is strong, leadership is engaged, execution functions, and every new initiative lands on people still absorbing the last three. Change fatigue doesn't show in capability scores. It shows later, in adoption, attrition and the goodwill the next change needs. A short diagnostic can't detect it; recognizing yourself here is the better signal.
Who they are
- Three or more enterprise initiatives running at once
- Strong delivery function, weak or absent change function
- Adoption measured at launch, rarely at 12 months
What they do
- Stack initiatives rather than sequence them
- Celebrate go-live and move on
- Lean on the same few change-capable people every time
Three questions for your next leadership meeting
- How many enterprise changes has an average employee absorbed in the past 18 months?
- For our last three initiatives, what is adoption today, not at launch?
- Who is carrying change load that no one has resourced or acknowledged?
The Capped Enterprise
More capability than the leadership layer can absorb
You have built more capability than your leadership layer can use.
Your technical people are good and your data is better than most, and none of it reaches the room where enterprise decisions get made. This isn't a capability problem; it's an interface problem. Organizations here often spend years buying more capability to fix a problem more capability can't fix.
Who they are
- Capability sits two or more layers below the executive table, often inside IT
- Technical bench stronger than the sector norm
- Requests arrive as deliverables, not outcomes
What they do
- Produce sophisticated analysis that circulates sideways and stops
- Attend meetings to report, not to decide
- Lose good staff to organizations that will use them
Three questions for your next leadership meeting
- When did an executive decision last change because of something our data told us?
- Who at the leadership table could explain what our capability is for, without a slide?
- What are we buying next, and what says that's the real constraint?
The PowerPoint Enterprise
Sound decisions the organization cannot convert
Your executives make sound decisions. Your organization can't convert them.
The strategy is coherent and the leadership interface works. Somewhere between the decision and the workplan it dissolves, usually at a department boundary, usually because no one owns what the decision depends on. It looks like success right up until the annual review. You don't need a better strategy; you need a mechanism that survives the budget cycle.
Who they are
- Well-articulated strategy, often externally produced
- Ownership assigned to committees, not named people
- Department budgets set apart from enterprise priorities
What they do
- Agree in the room and lose it on the way out
- Track initiatives by status colour, not outcome
- Re-plan rather than diagnose why the last plan stalled
Three questions for your next leadership meeting
- Name the last cross-departmental decision that stuck. What made it stick?
- For our three most important data assets, who is the accountable person, not the committee?
- Which of last year's priorities are actually funded in this year's workplan?
The Technology Optimist
Belief running ahead of foundation
Leadership believes more than the foundation can support.
The executive layer is engaged, and the capability underneath is thinner than the conversation suggests. This pattern usually comes before a visible failure, because expectations are already public. It is recoverable now; it stops being recoverable after the first missed commitment.
Who they are
- Recent executive enthusiasm, often triggered by AI or a peer's announcement
- Data quality untested, or known to be poor and unspoken
- Pilots multiply; few reach production
What they do
- Announce before proving
- Fund tools ahead of governance and stewardship
- Treat a pilot's success as proof of enterprise readiness
Three questions for your next leadership meeting
- What have we committed to publicly that our data couldn't withstand scrutiny on?
- If someone audited our foundational data tomorrow, what wouldn't we want them to open?
- What's the smallest thing we could prove before we announce the next big thing?
The Hero Organization
Performance with a phone number
Everything that works, works because of specific people. That isn't a system.
Individuals are holding this together, and they're probably good at it, which is what hides the problem. Nothing is repeatable, transferable or resilient to a resignation. The risk isn't performance; it's that your performance has a phone number.
Who they are
- Small capability team, often one or two long-tenured people
- Processes carried in people's heads
- Standards applied by habit, not governance
What they do
- Deliver reliably until someone leaves
- Rebuild the same thing because nothing was captured
- Resist process because past process came without purpose
Three questions for your next leadership meeting
- If our two most capable people left this quarter, what stops?
- What do we do that is documented well enough for someone else to do it?
- Where are we mistaking individual effort for organizational capability?
There is a pattern this diagnostic can't see
Change capacity, whether your people can absorb another initiative, doesn't appear in any score above. It shows up eighteen months later, in adoption numbers nobody wants to present. Measuring it takes a dedicated instrument and more than one respondent.
How this works
Assigned by pattern. A cascade of gap conditions between the three scores decides the archetype; the relationship between them matters more than the absolute values.
A hypothesis, not a score. The Litmus is a ten-question indicator, not an assessment. Single-respondent self-report is the weakest evidence in any maturity practice, so treat the result as a pattern worth investigating. A facilitated assessment with an affiliate turns it into evidence.
The Maturity Method™ · Mass Maturity Inc. · © 2026 · Maturity Insights