Capability Map

The value of a capability map comes from being stable. Processes change, organisational structures change every reorganisation, and systems are replaced — but a bank still needs to originate loans, assess credit risk, service accounts and handle collections. Anchoring analysis to capabilities gives a frame that survives, which is what makes multi-year comparison possible at all.

The properties that distinguish a useful map from a diagram of the org chart with different labels: capabilities are expressed as what the business does rather than how or who does it, they are mutually exclusive so that a given ability appears once, and they decompose to two or three levels — beyond which the exercise becomes process modelling and stalls.

The uses that justify building one. Heat-mapping — overlaying maturity, cost, risk or strategic importance to show where investment should go and, more usefully, where it is currently going and should not be. Duplication analysis — showing that six systems implement the same capability across three business units. Investment alignment — connecting a portfolio of projects to the capabilities they improve, which frequently reveals that the strategic priority has no funded work against it.

The failure to avoid is the map as an end in itself. Enterprise architecture teams can spend a year producing a beautiful model that nobody uses, and the discipline that prevents it is to build the map only to the depth a specific decision requires.