Capability Maturity Model
A capability maturity model is a framework for assessing the current level of development of a specific capability and defining the path to higher levels of performance — typically using a 1–5 scale from ad hoc to optimized.
Definition
A capability maturity model (CMM) is a structured framework for evaluating the current state of a capability and defining the stages of improvement toward a target state. Most maturity models use a five-level scale: Level 1 (Initial/Ad Hoc) — the capability exists but is performed inconsistently and relies on individual heroics; Level 2 (Managed) — the capability is performed consistently within individual projects or teams; Level 3 (Defined) — the capability is standardized across the organization with documented processes and training; Level 4 (Quantitatively Managed) — the capability is measured and controlled using quantitative metrics; Level 5 (Optimizing) — the capability is continuously improved based on data and feedback. In business architecture, capability maturity models are used to assess the current state of each capability in the capability map, identify gaps relative to the target state required by the strategy, and prioritize investment decisions.
Origin & Context
The capability maturity model concept originated with the Capability Maturity Model for Software (CMM), developed by the Software Engineering Institute (SEI) at Carnegie Mellon University in the late 1980s. It was later expanded into the Capability Maturity Model Integration (CMMI). The concept has since been adapted for business architecture, where it is applied to assess the maturity of business capabilities rather than software development processes.
Why It Matters
Capability maturity models matter because they transform capability assessment from a subjective judgment into a structured, repeatable evaluation. Without a maturity model, it is difficult to compare capability performance across business units, track improvement over time, or make the case for capability investment. With a maturity model, organizations can objectively assess where each capability stands, define what 'good' looks like at each level, and create a prioritized roadmap for capability improvement.
Common Misconceptions
- Myth: Every capability should be at Level 5.
- Reality: The appropriate maturity level for a capability depends on its strategic importance. Differentiating capabilities (those that create competitive advantage) should be at Level 4 or 5. Commodity capabilities (those that are necessary but not differentiating) may only need to be at Level 3. Investing in Level 5 maturity for a commodity capability is wasteful.
- Myth: Maturity assessment is a one-time exercise.
- Reality: Capability maturity should be assessed regularly — at least annually — to track improvement, identify regression, and update the investment roadmap. Many organizations build maturity assessment into their annual planning cycle.
- Myth: Maturity assessment is purely objective.
- Reality: Maturity assessment involves significant judgment, particularly at the boundary between levels. The most reliable assessments combine quantitative metrics (where available) with structured interviews and facilitated workshops involving both business and IT stakeholders.
Practical Example
A retail bank assesses the maturity of its 'Customer Analytics' capability as part of a digital transformation initiative. The assessment reveals that the capability is at Level 2 (Managed) — analytics are performed in individual business units using inconsistent tools and definitions, with no enterprise-wide data governance. The target state, required to support personalized digital banking, is Level 4 (Quantitatively Managed). The gap analysis identifies three key investments: a unified customer data platform, enterprise data governance, and an analytics center of excellence. These investments are prioritized in the transformation roadmap based on their impact on the capability maturity gap.
Industry Applications
- Financial Services
- Banks use capability maturity models to assess the readiness of their digital capabilities (mobile banking, open banking, AI-driven decisioning) and prioritize technology investments.
- Healthcare
- Healthcare systems use maturity models to assess clinical and administrative capabilities, identifying where standardization and automation can improve patient outcomes and operational efficiency.
- Manufacturing
- Manufacturers use maturity models to assess Industry 4.0 capabilities (predictive maintenance, digital twin, smart factory), creating a roadmap for operational technology investment.
- Government
- Government agencies use maturity models to assess digital service delivery capabilities, identifying gaps in citizen-facing and back-office capabilities that need investment.
Related Terms
- Business Capability: Capability maturity models are used to assess the performance of business capabilities
- Capability Heat Map: Capability heat maps visualize maturity assessment results across the full capability model
- Value Stream Mapping: Value stream mapping is used alongside maturity assessment to understand how capability gaps affect value delivery