Most organizations don’t struggle because they lack smart people or modern tools. They struggle because they lack a shared understanding of what’s actually broken.
You’ve seen it:
- The dashboard says one thing, the team says another or simply ignore it.
- Projects “make progress” but don’t land.
- Meetings are sharp, follow-through is soft.
- A process “exists,” but everyone runs it differently.
- Someone says “we need tech to fix this”, but cant define what this is
The problem is we use one word—maturity—to describe two different things.
This model is needed because it separates them.
The Organizational Maturity Model: Capability + Process
1) Capability Maturity (skills-first)
How well a person or team turns information into judgment and action. This applies to individuals and organizations. Tech may support it, but it’s not “a tech ladder.”
2) Process Maturity
How clearly the work is defined, repeatable, measurable, and improvable.
The Organizational Maturity Grid: Diagnosing Your Next Growth Move
| Ladder 1: Capability Maturity C0 — Tribal memory Depends on what people remember. C1 — Capture Notes/emails/paper. Information exists but isn’t reusable. C2 — Organize Spreadsheets/docs/checklists. Structure appears. C3 — Standardize Shared definitions, consistent metrics, repeatable reporting. C4 — Explore People can ask “why?” and investigate without rebuilding everything. This typically includes tools like Interactive views, drilldowns, slicing by context. C5 — Execute Decisions translate into owners, next steps, routing, follow-ups. Insights turn into action: alerts, routing, checklists, workflows, ownership. This typically includes shared plans and task lists. C6 — Learning Loop System Improves Itself. Outcomes feed back to refine standards, playbooks, and tooling (AI?). The goal is faster, higher-quality decisions with less cognitive load. | Ladder 2: Process Maturity P0 — Ad hoc High variation. Lots of “it depends.” P1 — Repeatable There’s a usual way, but it’s not explicit. P2 — Defined Clear stages, handoffs, owners, and “done.” P3 — Measured Cycle time, aging, rework, defects, SLAs. P4 — Improved Experimentation and continuous improvement are normal. |
Putting this together you get the Organizational Maturity Grid.
This grid gives you a targeted prescription:
- Hero-Driven / High-Variance– Stabilize the process: define stages, ownership, and handoffs (raise P).
- Bureaucratic Efficient– Invest in capability: definitions, analysis skills, and exploration habits (raise C).
- Immature / Fragile– Start with minimum viable clarity + basic capture/organization.
- High-Performing / Compounding– Strengthen the learning loop: measure outcomes, review exceptions, and improve continuously.
How this helps (practically)
1) It prevents the wrong fix
Teams often solve the wrong problem:
- They add process when the issue is capability (they create bureaucracy).
- They add tools/AI when the issue is process (they automate confusion).
The dual model points to the right lever.
2) It explains uneven maturity without drama
Organizations aren’t one maturity level. They’re a patchwork by workflow.
This model lets you say, calmly:
- “Admissions is strong capability, weak process.”
- “Billing is defined and measured, but needs stronger exploration skills.”
That’s a useful conversation, not a judgment.
3) It turns maturity into a roadmap you can execute
For any workflow (or any person), you can choose one next move:
- raise Capability (C)
- or raise Process (P)
That turns “we need to improve” into “here’s what we’re doing next.”
4) It also applies to individuals
This isn’t only an org model.
- A high performer might be high capability / low process personally: brilliant work, inconsistent follow-through, hard to delegate.
- Another might be high process / low capability: extremely reliable, but not yet strong at root-cause diagnosis or judgment calls.
This gives managers a respectful development language:
- “Let’s strengthen your decision-to-execution muscle (C5).”
- “Let’s define your handoffs and definitions (P2).”
- “Let’s build your learning loop (C7) using outcomes and retros.”
The takeaway
Maturity isn’t one ladder. It’s two.
- Capability is how well you think and decide.
- Process is how well work runs and improves.
Real maturity is when those ladders climb together.