Capability Maturity Model vs. Capability Map: Assessment vs. Inventory
A capability map tells you what capabilities exist. A maturity model tells you how well they are performing. You need both — in the right sequence.
The Capability Maturity Model (CMM) and the Business Capability Map are two of the most important tools in business architecture — and they are frequently confused because they both use the word 'capability.' In practice, they serve fundamentally different purposes and must be used in a specific sequence to drive strategic value. A Business Capability Map is an inventory: a structured, hierarchical list of all the things an organization must be able to do to deliver its value proposition. It answers the question 'What capabilities do we have or need?' A Capability Maturity Model is an assessment framework: a structured way to evaluate how well each capability is currently performing, and what 'good' looks like at each level of maturity. It answers the question 'How well are we performing each capability?' The relationship between them is sequential and complementary. You need a capability map before you can apply a maturity model — you cannot assess the maturity of capabilities you haven't defined. But together, they create one of the most powerful strategic planning tools available: the ability to identify which capabilities are strategically critical but currently underperforming, and prioritize investment accordingly.
Capability Maturity Model
A framework for assessing and improving the performance level of specific business capabilities
Best for
- Prioritizing capability improvement investments based on current performance gaps
- Establishing baselines before transformation programs and measuring progress over time
- Communicating capability performance to executives in a structured, comparable format
Business Capability Map
A hierarchical inventory of all capabilities an organization needs to deliver its value proposition
Best for
- Building a stable foundation for enterprise architecture and technology decisions
- Aligning business strategy with operational capabilities during strategic planning
- Comparing capability portfolios during mergers or organizational restructuring
Capability Maturity Model vs. Business Capability Map: Side-by-Side
| Dimension | Capability Maturity Model | Business Capability Map | Insight |
|---|---|---|---|
| Primary Purpose | Assess how well a capability is currently performing against defined maturity levels. Provides a standardized way to measure capability performance and identify improvement opportunities. | Define what capabilities the organization has or needs to have. Creates a comprehensive inventory of all business capabilities organized in a logical hierarchy. | Complementary purposes — assessment vs. definition |
| Output Format | Maturity scores (typically Level 1-5) for each assessed capability, often with specific criteria defining each level and gap analysis identifying improvement priorities. | Hierarchical list of capabilities organized by domain and sub-domain, typically spanning 2-3 levels from high-level business domains down to specific capabilities. | Different output types designed for different uses |
| Typical Structure | Level 1: Initial/Ad hoc → Level 2: Managed → Level 3: Defined → Level 4: Quantitatively Managed → Level 5: Optimizing/Leading | Level 1: Business Domain → Level 2: Capability Group → Level 3: Individual Capability (with some models including Level 4: Sub-capabilities) | Maturity progression vs. taxonomic hierarchy |
| Primary Use Case | Investment prioritization — determining where to improve capability performance based on strategic importance vs. current maturity gaps. | Strategic alignment — mapping which capabilities support specific strategic objectives and ensuring complete coverage of business requirements. | Investment decisions vs. strategic planning |
| Implementation Sequence | Applied after the capability map is defined and capabilities are clearly understood. Cannot meaningfully assess capabilities that haven't been properly defined. | Defined first as the foundation for all other capability work. Must be stable before maturity assessment can begin. | Map must come first, then maturity assessment |
| Update Frequency | Updated annually or after major improvement programs to track progress and reassess priorities. Scores change as capabilities improve. | Highly stable — updated only when the business model changes significantly or new strategic capabilities are required. | Dynamic assessment vs. stable foundation |
| Stakeholder Focus | Executive sponsors, investment committees, transformation program leaders who need to make capability investment decisions. | Strategy teams, enterprise architects, business unit leaders who need to understand and organize business capabilities. | Investment stakeholders vs. architecture stakeholders |
| Common Frameworks | CMMI (Capability Maturity Model Integration), P3M3 (Portfolio, Programme and Project Management Maturity Model), ACMM (Architecture Capability Maturity Model). | BIZBOK capability taxonomy, industry reference models (like APQC Process Classification Framework), custom organizational capability maps. | Assessment frameworks vs. taxonomic frameworks |
| Measurement Focus | How well capabilities are performing against defined criteria including process maturity, automation level, and outcome effectiveness. | What capabilities exist or are needed, with focus on completeness and logical organization rather than performance levels. | Performance measurement vs. capability identification |
When to Use Each
- Starting a digital transformation program
- Begin with capability mapping to define what capabilities will be impacted, then apply maturity assessment to establish baseline performance levels. You need to know what you're transforming before you can assess how well it's currently working or set improvement targets
- Preparing annual capability investment planning
- Use capability map to ensure all strategic capabilities are covered, then apply maturity model to identify which capabilities need investment. Investment decisions should be based on strategic importance (from the map) combined with performance gaps (from maturity assessment)
- Benchmarking against industry peers
- Use industry-standard capability maturity models to enable meaningful comparison of capability performance levels. Maturity models provide standardized performance criteria that enable objective comparison across organizations
- Building enterprise architecture practice
- Start with capability mapping to create a stable foundation for all architecture decisions and technology investments. The capability map becomes the organizing framework for enterprise architecture and ensures technology investments align with business capabilities
- Evaluating merger or acquisition targets
- Compare capability maps first to understand capability portfolio overlap, then assess maturity levels to identify integration priorities. You need to understand what capabilities each organization has before you can meaningfully compare how well they perform them
- Designing new operating model
- Use capability mapping to define required capabilities for the target state, then design maturity targets for each capability. The operating model must define both what capabilities are needed and how well they need to perform
How They Work Together
The combination of a capability map with maturity assessment creates capability-based investment planning — one of the most rigorous approaches to strategic resource allocation. The capability map identifies which capabilities are strategically important; the maturity assessment identifies which capabilities are currently underperforming. The intersection of 'strategically important but currently immature' becomes your investment priority list. This is far more effective than traditional budget-based planning, which allocates resources based on departmental requests rather than strategic capability requirements.
The Common Mistake
The most common mistake is applying a maturity model before the capability map is defined — or worse, using a generic industry maturity model that doesn't match the organization's actual capability structure. This results in assessing the wrong capabilities, producing scores that don't connect to strategic priorities, and generating investment recommendations disconnected from the business model. Always define your capability map first, then design or adapt a maturity model that assesses the capabilities in your map.
Why Sequence Matters: Foundation Before Assessment
The relationship between capability maps and maturity models isn't just complementary — it's sequential. Getting the sequence wrong undermines both tools.
Many organizations rush to maturity assessment because it feels more actionable than mapping. After all, maturity models produce scores and gap analyses that seem immediately useful for investment decisions. But applying a maturity model before the capability map is defined creates several problems. First, you end up assessing capabilities that may not be relevant to your business model or strategic priorities. Second, you miss assessing capabilities that are critical to your success but aren't covered by the generic maturity model you're using. Third, the resulting scores don't map cleanly to your organizational structure or strategic objectives, making investment decisions difficult. The capability map provides the organizing framework that makes maturity assessment meaningful. It ensures you're assessing the right capabilities, at the right level of detail, organized in a way that connects to your strategic priorities and organizational structure. Once you have that foundation, maturity assessment becomes a powerful tool for identifying where to invest.
Making Maturity Models Work for Your Organization
Generic maturity models rarely fit perfectly with your capability map — and that's okay. The key is adapting them intelligently.
Industry-standard maturity models like CMMI provide excellent frameworks for assessment criteria and maturity level definitions. But they're designed for broad applicability, not for your specific capability map. The most effective approach is to use established maturity frameworks as templates, then adapt the assessment criteria to match your specific capabilities. For example, if your capability map includes 'Customer Onboarding' as a distinct capability, you need maturity criteria that specifically address onboarding processes, not generic 'Customer Management' criteria. This adaptation process requires understanding both your capability map structure and the underlying principles of maturity assessment. Each maturity level should represent a meaningful improvement in capability performance, with clear criteria for what 'good' looks like at each level. The criteria should be specific enough to enable consistent assessment but flexible enough to accommodate different ways of delivering the capability.
Adaptation Framework: Start with established maturity criteria (like CMMI levels), then customize the assessment questions to match your specific capabilities. Keep the 5-level structure but make the criteria capability-specific.
From Assessment to Action: Using Both Tools for Investment Planning
The real value of combining capability maps with maturity models emerges in investment planning — but only if you structure the analysis correctly.
Capability-based investment planning uses a simple but powerful framework: plot your capabilities on two dimensions — strategic importance (from your capability map and strategic priorities) and current maturity level (from your maturity assessment). Capabilities that are high importance but low maturity become your investment priorities. Capabilities that are high importance and high maturity become capabilities to maintain and protect. Capabilities that are low importance regardless of maturity become candidates for outsourcing or divestment. This analysis must be done at the right level of detail — typically at the individual capability level, not at the capability group or domain level. Investment decisions need to be specific enough to drive budget allocation and program design. The output should be a prioritized list of capability improvement initiatives, each with a clear business case based on strategic importance and current performance gaps. This approach ensures investment decisions are driven by strategic logic rather than departmental politics or budget history.
Investment Matrix: Plot capabilities on Strategic Importance (High/Low) vs Current Maturity (High/Low). Focus investment on High Importance + Low Maturity capabilities first.
Bottom Line
Build your capability map first to define what capabilities your organization has or needs. Then design a maturity model that assesses those specific capabilities against the performance levels required by your strategy. Use the combination to drive capability investment decisions — prioritize capabilities that are strategically critical but currently immature. This sequence ensures your maturity assessment is relevant and your investment decisions are strategic.