Enterprise Capability Map

Definition

An enterprise capability map is the most comprehensive form of business capability model, covering the full scope of an organization's capabilities across all business domains. It is typically organized into three levels: Level 1 (L1) capability domains, which represent the major areas of organizational activity; Level 2 (L2) capabilities, which represent the specific abilities within each domain; and Level 3 (L3) sub-capabilities, which represent the detailed activities within each capability. The enterprise capability map provides a stable, strategy-neutral view of the organization's capabilities that can be used as a common reference point for strategic planning, investment prioritization, organizational design, and technology portfolio management.

Origin & Context

Enterprise capability maps emerged as a business architecture artifact in the early 2000s, as organizations began to recognize the limitations of process-centric and technology-centric views of the enterprise. The BIZBOK Guide formalized the enterprise capability map as a core business architecture artifact, and major consulting firms developed industry-specific reference capability models for sectors such as banking, insurance, healthcare, and manufacturing.

Why It Matters

The enterprise capability map provides a stable, business-focused reference architecture that transcends organizational silos, technology platforms, and process variations. It enables organizations to have strategic conversations about what they need to be able to do, independent of the political and technical constraints that often distort investment decisions. Business architects use it to identify capability gaps, prioritize investments, rationalize technology portfolios, and design organizational structures.

Common Misconceptions

Myth: An enterprise capability map is the same as an organizational chart.

Reality: An organizational chart describes the reporting structure; an enterprise capability map describes the organizational abilities required to execute the strategy. Multiple organizational units may contribute to a single capability.

Myth: Building an enterprise capability map requires a multi-year effort.

Reality: A first-version enterprise capability map can typically be developed in four to eight weeks using industry reference models, stakeholder workshops, and document analysis.

Practical Example

A global manufacturing company develops an enterprise capability map covering 8 L1 domains, 45 L2 capabilities, and 180 L3 sub-capabilities. The map is used for: (1) a capability assessment identifying 12 critical capabilities; (2) a technology portfolio rationalization mapping 340 applications to the capability map; and (3) an organizational design review identifying fragmented capabilities that should be consolidated.

Industry Applications

Financial Services

Banks develop enterprise capability maps covering Customer Management, Product Management, Risk Management, and Operations domains.

Healthcare

Health systems develop enterprise capability maps covering clinical, administrative, and support domains.

Manufacturing

Manufacturers develop enterprise capability maps covering design, production, supply chain, and commercial domains.

Technology

Technology companies develop enterprise capability maps covering product development, platform engineering, customer success, and go-to-market domains.

Related Terms

• Business Capability Model: An enterprise capability map is the most comprehensive form of business capability model, covering the full scope of the enterprise.
• Capability Assessment: A capability assessment evaluates the maturity of the capabilities in the enterprise capability map.
• Capability Roadmap: A capability roadmap sequences the development of the capabilities identified in the enterprise capability map.