Capability Mapping
Laying out capabilities hierarchically and overlaying information — systems, cost, health, differentiation — to make investment decisions visible.
Definition
A capability map arranges capabilities in a hierarchy, typically two or three levels. Its value comes almost entirely from what you overlay on it; the map alone is a taxonomy.
The overlays that make it useful
- Systems. Which applications implement each capability. Immediately reveals duplication — three systems calculating tax — and gaps.
- Health. How well is each capability supported? Colour-coded from an honest assessment, not a self-assessment by the owning team.
- Differentiation. Is this capability a competitive differentiator, a necessary hygiene function, or a commodity? This is the single most decision-relevant overlay.
- Cost. What is spent maintaining each. Frequently reveals that the largest spend is on non-differentiating capabilities.
- Change frequency. Which capabilities change most, which should therefore have the best architecture and the most autonomy.
The decision the overlays produce
Cross differentiation with health and cost, and the investment logic falls out:
| Differentiating | Health | Action |
|---|---|---|
| High | Poor | Invest heavily. This is where architecture effort belongs |
| High | Good | Protect and evolve |
| Low | Poor | Buy or outsource. Do not build |
| Low | Good | Leave alone; resist the urge to modernise it |
The bottom-left cell is where most organisations discover they are spending engineering time building a commodity capability badly.
Why this beats a systems diagram for these conversations
A systems diagram is organised by how, so it cannot answer "should we be doing this at all". A capability map is organised by what, which is the frame a business audience already thinks in — and which makes duplication and misallocation visible without technical vocabulary.
Failure scenarios
- The map is the deliverable. A beautiful map with no overlay and no decision attached is a consulting artefact.
- Self-assessed health, so everything is amber and nothing is red.
- Too many levels, so it becomes unreadable and unmaintainable.
- Never updated, so it describes the organisation two years ago.
- Used to justify a reorganisation rather than to inform investment, which discredits it permanently.
Interview question
"You have mapped capabilities and overlaid cost and differentiation. What decision does that enable?"