Capability Mapping & Governance
Knowing what the organization can do, independent of the specific system currently doing it.
9.5.1Definition
A capability map is a structured, hierarchical inventory of what a business can do — "process payments," "manage customer relationships," "fulfill orders" — described independent of any specific implementing system or team. Governance is the set of ownership and decision rights attached to each capability, clarifying who is accountable for it.
9.5.2Why It Exists
Organizations frequently know which systems they operate but struggle to answer a subtly different, more strategic question: what can the business actually do, and where is each capability currently implemented. Capability mapping exists to answer that question directly, giving leadership a system-independent view for investment and consolidation decisions, distinct from the application inventory (9.2) that tracks implementation.
9.5.3Capability Map vs. Application Inventory
| Capability map | Application inventory (9.2) | |
|---|---|---|
| Describes | What the business can do | What systems exist |
| Stability | Relatively stable over time | Changes as systems are built, retired, replaced |
| Use | Strategic investment decisions | Operational system management |
9.5.4Common Mistakes
- Confusing a capability map with an org chart or system inventory, describing structure or implementation instead of what the business actually does.
- No clear governance owner per capability, leaving investment and improvement decisions with no accountable decision-maker.
- A capability map built once and never used in actual prioritization or investment conversations.
9.5.5Best Practices
- Keep capability descriptions implementation-independent — describe the "what," not the current "how."
- Assign a clear, accountable governance owner to each major capability.
- Use the capability map actively in investment and consolidation decisions, not as a static reference document.