Maturity Model Guidance¶
Framework — instantiates Phase-Specific Intervention
Implements the archetype by tying recommended practices to capability maturity stages rather than recommending the same practice to every organization.
Maturity Model Guidance ties recommended practices to an organization's capability maturity level — and its defining idea is that the levels form a normative, aspirational ladder the organization is trying to climb: advancing is the goal, and the framework prescribes the practices that fit the current rung while forbidding the ones that are premature. The same advanced practice that pays off at a high level is wasted or harmful at a low one, because the prerequisites for it don't yet exist. Where a best-practices checklist urges every organization to adopt the same practices, this framework first rates where the organization actually is, recommends the practices appropriate to that level, marks the higher-level practices as contraindicated until their foundations are in place, and defines the criteria that count as reaching the next level. Its center of gravity is the climbable capability ladder with per-level practice sets and advancement gates — a stage you rise through by earning it, not a state that happens to you.
Example¶
A software organization assesses itself against a capability maturity framework in the tradition of the CMM.[n1] The assessment rates it at an early level: work gets done, but through heroics — no consistent process, results depend on who is on the team. The framework's guidance for this level is pointed: the appropriate practices are the basics — version control, a defined build, requirements and estimates written down, a repeatable project routine. Just as important is the contraindication: the framework explicitly warns against adopting the glamorous high-maturity practices — statistical process control, quantitative optimization of the development pipeline — because an organization that can't yet run a repeatable process has no stable data to optimize, so those practices would be theater. Advancement is gated: to move up a level, the organization must demonstrate defined criteria (its core processes are documented and actually followed across projects), not merely declare the intent. Once it clears those gates, the recommended practice set changes to the next rung's, and the practices that were contraindicated before become the appropriate next investment. The framework thus hands a different organization a different next step, keyed to the rung it is standing on.
How it works¶
- Rate the rung. An assessment places the organization at a maturity level from evidence of how it actually works, not how it aspires to work — the level, not a universal ideal, indexes the guidance.
- Practices for this level. Each level carries the practices that fit it: the foundations that a low-maturity organization must install before anything advanced can stick.
- Contraindicate the premature. Higher-level practices are explicitly marked as not-yet-appropriate, so the organization doesn't burn effort on optimization it can't support — the framework's guard against cargo-cult adoption.
- Gate the climb. Advancement runs on defined, demonstrable criteria for reaching the next level, so a rung is earned by evidence rather than claimed.
Tuning parameters¶
- Number of levels — few broad tiers or many fine ones. More levels give finer next-step guidance but risk turning the ladder into a bureaucratic scoring exercise.
- Assessment rigor — self-rating versus formal appraisal. Rigor makes the level trustworthy but is costly and can incentivize gaming the appraisal.
- Advancement-gate strictness — how much evidence to certify a level. Strict gates keep levels meaningful but slow the climb; lenient ones let organizations claim maturity they haven't built.
- Contraindication firmness — hard "do not adopt yet" versus soft advice. Firm contraindications prevent premature practices but can block a genuinely ready outlier; soft ones invite level-skipping.
When it helps, and when it misleads¶
Its strength is that it stops the two symmetric errors of one-size advice: pushing advanced practices onto an organization that can't support them, and leaving a capable organization coasting on beginner practices. By handing each organization the next step rather than the ideal end state, it makes improvement a walkable path.
Its central failure mode is level as trophy — the maturity rating becomes a badge chased for procurement or prestige, so the organization games the appraisal to "reach Level N" while the underlying practices remain hollow. The classic misuse is treating the ladder as a status ranking or a stick, punishing low-maturity units rather than guiding them, which corrupts the assessment into defensiveness. The guarding discipline is to keep the level a diagnostic that selects the next practice, tie certification to demonstrated behavior rather than paperwork, and hold an informal reality-check that the practices are lived, not merely documented.
How it implements the components¶
phase_classifier— the assessment that rates the organization's current maturity level from evidence of practice.action_by_phase— the per-level set of recommended practices appropriate to that rung.phase_contraindication_map— the higher-level practices marked premature until their prerequisites exist.phase_exit_criteria— the demonstrable criteria that certify reaching the next level.
It does not implement the phase_condition_model that explains an involuntary clinical stage's biology — that's Disease-Stage Treatment Protocol, where advancing to a higher stage is bad news rather than the goal; nor the exception_review_path and phase_transition_memory that manage a product's market decline and carry patterns across generations — that's Product Lifecycle Strategy. Its levels are an aspirational ladder the organization climbs, not an involuntary stage it suffers or a market curve it rides.
Related¶
- Instantiates: Phase-Specific Intervention — supplies the capability-level-matched-practice core for improvement frameworks.
- Sibling mechanisms: Disease-Stage Treatment Protocol · Product Lifecycle Strategy · Lifecycle-Stage Policy · Market Regime Strategy · Incident Phase Playbook · Stage-Specific Communication Plan · Ecological Phase Management · Education Scaffolding by Stage · Escalation/De-escalation Matrix
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The mechanism rates observed organizational capability against maturity evidence and uses that finding to determine appropriate and contraindicated practices.
Nearest alternative: Representation, Specification & Plan — The staged guidance is represented in a framework, but its defining use begins with an evidence-based maturity disposition that indexes the recommendation.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Capability-maturity guidance belongs to organizational process-improvement and management practice.
Related originating lineages:
- Computer Science & Software Engineering — The Capability Maturity Model in software engineering was a canonical formalization.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
[n1] The Capability Maturity Model — originated by Watts Humphrey and the Software Engineering Institute — which rates an organization's software process on staged levels (initial, managed, defined, quantitatively managed, optimizing) and prescribes different practices at each. It is the canonical example of guidance tied to a capability rung rather than issued uniformly. ↩