Business Capability Map

A business capability map describes what an organization does, rather than how it is organized or which systems it uses. Capabilities such as managing customer relationships, pricing products, recruiting staff or settling payments are listed and grouped into a hierarchy, usually on a single page at the top level. Because capabilities change far less often than organization charts, processes or technology, the map gives a stable reference point for planning and comparison.

Capability maps are one of the most widely used tools in enterprise architecture because they create a shared language between business and technology leaders. Applications, projects, costs and teams can all be linked to capabilities, revealing where the organization overinvests, underinvests or duplicates effort. For IT strategy and finance, a capability map turns long lists of systems and budgets into a picture of how spending supports the business.

Definition of Business Capability Map

A business capability map is a model of an organization's capabilities, arranged in a hierarchy from broad areas at level one to more specific capabilities at levels two and three. A capability is an ability the organization needs, such as forecasting demand, described in terms of what it achieves rather than how.

The map is a central part of business architecture and is closely related to the business capability model, which defines capabilities in more detail.

How Capability Maps Are Structured

Level one capabilities are typically grouped into strategic, core and supporting areas. Strategic capabilities include planning and governance, core capabilities deliver products and services to customers, and supporting capabilities include finance, HR and IT.

Each level one capability is broken down into level two and sometimes level three capabilities. Most organizations end up with between 50 and 200 capabilities in total.

Good maps avoid duplication, so each capability appears only once, and use nouns or noun phrases rather than process steps. A capability named "invoice management" is easier to reuse than one named "send invoices to customers".

Capability Heat Maps

A capability heat map colors each capability according to a chosen measure, such as strategic importance, performance, investment level or risk.

Heat maps make patterns obvious. For example, an important capability colored red for poor performance stands out as a priority for investment.

Several heat maps can be produced from the same capability map, each answering a different question. Comparing them, such as spending against strategic importance, often prompts the most useful conversations.

Importance of Business Capability Maps in Enterprise Architecture

Capability maps give business and technology leaders a common reference. Discussions about priorities and investment become clearer when both sides use the same list of capabilities.

They connect strategy to technology. By linking applications to capabilities, architects can show which systems support each part of the strategy and where gaps or overlaps exist. Projects can be linked in the same way, showing whether the investment portfolio is aimed at the capabilities leaders say matter most.

They also remain stable through reorganizations, so analysis built on them stays useful even when teams and reporting lines change. This stability makes capability maps especially useful during mergers, when two organizations need a neutral way to compare what each does.

Linking Capabilities to Applications and Costs

Mapping each application to the capabilities it supports reveals duplication, such as five applications serving one capability, and gaps where important capabilities rely on spreadsheets.

Adding cost data shows how much the organization spends to support each capability. Combined with application portfolio management, this helps architects target consolidation where savings are largest.

Finance teams can use the same structure to report technology spending in business terms. Approaches such as the TBM taxonomy provide standard categories for the cost side, while the capability map provides the business view.

Common Mistakes

Mapping processes or departments instead of capabilities produces a map that goes out of date with every reorganization. It also tends to mirror internal politics rather than the work the organization needs to do.

Going into too much detail too early creates hundreds of capabilities that are hard to maintain and hard for executives to read.

Building a map without a clear use leads to a document that is admired once and then ignored. Maps are most valuable when they answer specific questions about investment, risk or change.