Capability Map — IT definition

A business capability map is the hierarchical representation of the business capabilities of an organization, typically over 3 to 4 levels. It is the reference deliverable of modern enterprise architecture: a shared snapshot, across executive committee, CIO, business, and architects, of "what the organization is able to do".

Where an org chart represents the who, a process diagram the how, and an application map the with what, the capability map represents the what — a stable level of abstraction that anchors all the other views.

Standard map structure

A capability map is typically organized in three zones:

• •Strategic capabilities: steering, governance, innovation, transformation.
• •Core business capabilities: what creates value (sell, produce, deliver, serve).
• •Support capabilities: what enables operation (HR, finance, legal, IT, procurement).

Each zone drills down in levels:

• •Level 1: 8 to 15 macro capabilities.
• •Level 2: 40 to 100 sub-capabilities.
• •Level 3-4: precise operational capabilities (200 to 500).

Heat maps and enrichment

A capability map becomes steerable when cross-referenced with data:

• •Criticality heat map: strategic capabilities in red, commodity in green.
• •Maturity heat map: under-invested vs over-invested capabilities.
• •Debt heat map: capabilities supported by obsolete applications.
• •Cost heat map: where the IT money goes.
• •Adoption heat map: capabilities actually used vs theoretical.

These views are the flagship deliverables presented to executive committees and strategic IT steering committees.

Use: arbitration and prioritization

A capability map serves several strategic purposes:

• •[Application rationalization](/en/glossary/application-rationalization): detect capabilities supported by several redundant applications.
• •Investments: prioritize budgets on under-invested strategic capabilities.
• •Transformation: identify capabilities to modernize before a cloud, ERP, or data program.
• •M&A: isolate capabilities to integrate or divest.
• •Regulatory compliance: trace which capabilities are impacted by DORA, NIS2, AI Act.

Industry references

To avoid starting from scratch, several industry frameworks exist:

• •APQC Process Classification Framework (PCF): most-used generic and industry-specific reference worldwide.
• •BIAN: banking (Banking Industry Architecture Network).
• •eTOM: telecommunications (Business Process Framework).
• •ARTS: retail (Association for Retail Technology Standards).
• •HL7 / FHIR: healthcare.
• •BIZBOK: Business Architecture Body of Knowledge (generic).

Starting from one of these references saves 6 to 12 months on map construction.

Best practices

• •Start high, drill down progressively: the level-1 map is built in half a day with the executive committee. Aiming for level 4 from the start is the most common mistake.
• •Stabilize language: avoid verbs (which look like processes); prefer nouns ("Order Management" rather than "Manage Orders").
• •Don't confuse with the org chart: the map is not a breakdown of departments; two departments can contribute to the same capability.
• •Update annually: a map that doesn't move becomes a decorative poster.
• •Link to the IT estate: without a connection to the application portfolio, the map stays theoretical.

Capability map and application mapping

Kabeen automatically attaches IT estate applications to business capabilities (by tags, by usage, by owner). The capability map then becomes an actionable view, continuously updated, exploitable for rationalization and budget arbitration.