You have mapped capabilities and overlaid cost and differentiation. What decision does that enable?
Show the full answer Hide the answer
What is being tested
Whether you know that a capability map's value is entirely in the overlays and the decision they support.
The decision: where to invest and what to buy
Cross differentiation with health, 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 |
The bottom-left cell is where organisations most often discover they are spending scarce engineering time building a commodity capability badly — an authentication system, a billing engine, a ticketing tool. Cost overlaid on top usually confirms it: the largest spend is frequently on the least differentiating capabilities.
Why a capability map beats a systems diagram for this conversation
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.
Three systems calculating tax is obvious on one and invisible on the other.
The other overlays worth having
- Systems, revealing duplication and gaps.
- Change frequency, identifying which capabilities need the best architecture and the most autonomy.
- Health, assessed from evidence — incident count, change lead time, patch currency — rather than self-assessed, because self-assessed health is always amber.
The failure to avoid
The map as the deliverable. A beautiful hierarchy with no overlay and no decision attached is a consulting artefact. It will be produced once, admired, and never updated.
The corrective discipline: produce the map only when there is a decision waiting for it, and put the overlay that informs that decision on it.
What a strong answer adds
Naming the second-order use: team alignment. Capability boundaries are the most durable basis for team boundaries, and aligning teams to capabilities makes Conway's Law work for you rather than against you — the architecture and the organisation reinforce each other in the right direction.