P3 Minimum Viable Maturity
P3 Filter Guide: Minimum Viable Maturity
Purpose: This document is a pre-P3 filter for assessing organisational maturity and calibrating strategic ambition to current capability. Load this guide into your AI system alongside the companion Minimum Viable guides for Principles, Products, Strategy, Patterns, and Governance as part of a coherent P3 bootstrapping toolkit.
What is Maturity? (The Minimum Definition)
Maturity is not organisational age, team size, or a compliance score. It is the capability terrain — a multi-dimensional description of what the organisation can reliably sustain right now.
The word "reliably" is load-bearing. A team that successfully delivered a complex integration once, under heroic effort, driven by a few exceptional individuals, has not demonstrated maturity in that practice. They have demonstrated a single instance of exceptional performance. Maturity is what the organisation can do repeatedly, consistently, by multiple people, under ordinary conditions — including under the stress of competing priorities and personnel turnover.
Maturity is not a ladder. The traditional view of maturity — Level 1 through Level 5, climb one rung at a time — is a useful simplification that becomes dangerous when taken literally. An organisation does not sit at "Level 3." It has a surface of capability: high in some domains, low in others. A peak in deployment maturity does not compensate for a valley in architecture governance. When a strategic objective passes through a valley, the valley sets the ceiling — not the average capability, not the highest peak.
Maturity is the boundary of reliable execution. Inside the capability frontier, the organisation can make commitments and keep them. Outside it, performance depends on heroic effort — sustainable until the stress it cannot absorb arrives.
The P3 minimum definition of maturity at the practice level requires three conditions:
- Demonstrated repeatability — the practice has been executed successfully by more than one person, more than once, with comparable outcomes. Single-instance success is not maturity.
- Teachability — a new practitioner can reach competence in this practice within a reasonable timeframe using documented materials or structured mentoring. Knowledge that lives only in specific individuals is fragility, not capability.
- Degradation visibility — the organisation knows when this practice has deteriorated. There is a signal — a metric, a review cadence, a pattern of incidents — that surfaces a decline before it becomes a failure.
Declared vs. Demonstrated Maturity. The most dangerous maturity gap is the distance between what an organisation claims it can do and what it actually does under operational conditions, including stress. A documented testing strategy is not the same as a culture of test-driven development. An approved deployment checklist is not the same as a pipeline that structurally cannot bypass quality gates. When assessing maturity, look at demonstrated behaviour — what practitioners do, not what governance documents say they should do. The gap between declared and demonstrated maturity is the primary measure of capability fragility.
The Capability Terrain and the Frontier Tax
P3 maps maturity as a Production Possibility Frontier (PPF) — the boundary between what the organisation can currently achieve reliably and what requires capability it does not yet possess.
The terrain is multi-dimensional and jagged. An organisation may have high deployment maturity while having low architecture governance maturity. It may have rigorous security practices in one product area and ad-hoc practices in another. The strategic consequence is direct: the valley in the path of a strategic objective sets the ceiling for what that objective can reliably achieve. An organisation with sophisticated deployment pipelines but immature security practices is building an increasingly efficient mechanism for shipping insecure products. The topography does not average out.
The Frontier Tax. Operating at or near the capability frontier — where every resource is committed and every trade-off is live — is more expensive and more fragile than operating in the interior. Near-frontier organisations have no slack and no reserve capacity. A key departure, an unplanned compliance requirement, a sudden escalation: any of these can exceed the frontier's absorptive capacity and tip performance into failure. Resilient organisations operate near their frontier but not perpetually at it, preserving margin for unexpected demands.
Three laws govern the terrain:
- Capability cannot be declared. An executive memo does not create a capability. Capability must be built through investment, practice, and institutionalisation. Aspiration is not maturity; demonstrated performance is.
- Capability advances along gradients, not steps. There is no jump from Level 1 to Level 4. Advancement is continuous and multi-dimensional. Some domains advance faster than others; some temporarily regress while others grow.
- Expanding the frontier requires structural change. Efficiency improvements move the organisation toward its existing frontier. Expanding the frontier itself — reaching capabilities the organisation does not currently have — requires new patterns, new governance mechanisms, and new institutional arrangements that did not previously exist.
Minimum Viable Maturity Profile
At early maturity, the most valuable thing you can do is construct an honest, practice-level capability profile. Use four levels:
| Level | Name | What it means |
|---|---|---|
| L1 | Initial (Ad-hoc) | Practice happens inconsistently. Outcomes depend on specific individuals. No reliable documentation or repeatability. Cannot be taught from materials alone. |
| L2 | Managed (Repeatable) | Practice is documented and performed with reasonable consistency. Outcomes are broadly predictable. A new practitioner can be onboarded using existing materials. |
| L3 | Defined (Standardised) | Practice is embedded in tooling or infrastructure that enforces consistency. Compliance does not depend on individual discipline alone. The practice is consistent across teams. |
| L4 | Measured (Managed) | Practice is instrumented. Performance data is collected and reviewed. The organisation can detect degradation before it manifests as failure and adjust accordingly. |
Populate this template for your critical practice areas:
| Practice Area | Current Level | Evidence of current level | Gap to next level |
|---|---|---|---|
| e.g. Automated Testing | L2 | Test pyramid documented; ~60% coverage | Pipeline threshold gates not yet enforced |
| e.g. Deployment | L3 | CI/CD pipeline with automated quality gates | Metrics not tracked (lead time, failure rate) |
| e.g. Architecture Review | L1 | Ad-hoc; depends on specific senior practitioners | Documented review checklist and cadence needed |
Focus on your critical domains first. A complete capability survey is not the goal at pre-P3 maturity. Identify the four to six practice areas most directly relevant to your strategic direction and product commitments. Assess those honestly. The remainder can follow.
The Ratchet — converting capability gains into permanent features. Maturity gains are not self-sustaining. Without deliberate institutionalisation, capability erodes through personnel turnover, schedule pressure, and the gradual normalisation of shortcuts. The Ratchet describes the four-stage mechanism for converting a capability advance into a permanent organisational feature:
| Tooth | Mechanism | What it holds against |
|---|---|---|
| 1. Documentation | The practice is written down, including its rationale — not just its steps. Knowledge moves from specific heads to shared, structured form. | Ignorance and turnover |
| 2. Tooling | The practice is embedded in tooling or infrastructure that enforces it without depending on human memory or discipline. | Forgetfulness and drift |
| 3. Governance | A named owner has authority to detect violations and act on them. The practice is constitutionally protected, not merely recommended. | Pressure and exception-creep |
| 4. Culture | Practitioners defend the practice because they understand why it matters, not because they are required to. The practice is valued, not merely enforced. | Time and leadership change |
A capability advance that has reached Tooth 1 (documentation) is fragile. A capability that has reached Tooth 3 (governance) is resilient. A capability that has reached Tooth 4 (culture) is durable — it survives significant organisational change.
When assessing maturity, identify which Ratchet Tooth each practice has reached alongside the CMMI level. Two practices both assessed as L2 may have dramatically different durability depending on whether one is documented and the other is governed. The Tooth state is as important as the level.
A warning: False Ratchets are common. Tooling that practitioners routinely bypass with no consequence is not a Ratchet tooth — it is an inconvenience. Governance that never stops anything is not governance — it is theatre. When assessing whether a tooth is genuinely set, ask: "If a practitioner chose to ignore or bypass this mechanism, what would stop them?" If the answer is "nothing, but they're supposed to follow it," the tooth is not set.
The Capability Reality Test: The Strategy Sieve
The Strategy Sieve calibrates strategic ambition to the capability terrain. For each significant element of a proposed strategy, apply one of three verdicts:
Now. The organisation's current capability frontier encompasses this requirement. The relevant practice domains are at L3 or above, with governance in place and demonstrated performance under operational conditions. The organisation can make this commitment and keep it without additional capability investment.
Grow. The organisation's capability in this domain is currently below what the strategy requires, but the gap is bridgeable within the strategic timeframe through named, resourced investment. "Grow" is not a green light — it is a conditional approval. Proceed alongside a Ratchet schedule: a sequenced, resourced programme of specific capability advances in the domains that are below the required level, with milestones at each Tooth. Without the Ratchet schedule, "Grow" is aspiration with a deadline.
Recalibrate. The capability gap is too large to bridge within the strategically relevant timeframe. Recalibrate does not mean abandon — it means redirect toward a version of the objective the current frontier can reach, or extend the timeline to accommodate the structural change required to expand the frontier. A strategy composed entirely of Recalibrate findings is not a strategy; it is a capability development roadmap. Redesign the strategy accordingly.
There is no fourth option. Attempting to execute a strategy that requires capabilities the organisation does not have — and has no plan to build — does not produce ambitious outcomes. It produces systemic damage: burnout, technical debt, governance failures, and degradation of the capabilities the organisation did possess before the overreach began. The frontier does not negotiate.
Applying the Sieve to your capability profile:
- For each element of the strategic direction, identify which practice domains it depends on.
- Check the current level and Ratchet Tooth status of each domain.
- Apply Now / Grow / Recalibrate.
- For every "Grow" finding, attach a specific Ratchet schedule — named investments, sequenced Teeth, milestones.
- For every "Recalibrate" finding, revise the strategic element before proceeding.
The Veto of Physics. The Sieve's third verdict — Recalibrate — is the organisational equivalent of the Veto of Physics: the constitutional authority to say "this is aspiration, not strategy." The executive who demands Level 4 performance from a Level 1 organisation is not setting ambitious targets; they are building commitment on ground that does not exist. Honest assessment of the frontier is not pessimism. It is the precondition for plans that can actually be executed.
Connecting to the framework. Maturity calibrates Strategy (through the Strategy Sieve), conditions Governance (governance structures must match the maturity level that can sustain them — light governance on ad-hoc practices creates paralysis, heavy governance on critical ad-hoc practices still fails), and determines which Patterns the organisation can safely execute (an L1 practice domain cannot reliably run canonical patterns designed for L3 or above). The companion guides for Minimum Viable Strategy, Minimum Viable Governance, and Minimum Viable Patterns each assume a baseline maturity assessment as their starting point. This guide provides that baseline.