Business Capability Model

A business capability model defines what an organization is able to do, in a consistent structure that people across the business can use. Each capability, such as managing customer accounts, forecasting demand or onboarding suppliers, is named, described and placed in a hierarchy. The model often records relationships between capabilities and other elements, such as the value streams that use them, the organization units that perform them and the applications that support them.

The capability model is the foundation for much of business architecture. It provides the definitions behind a capability map and a common reference for linking strategy, projects, applications and costs. Because capabilities change far less often than processes or organization charts, analysis built on the model stays meaningful over time. For IT strategy and finance, a well-defined model makes it possible to describe technology spending in business terms and compare it across divisions and years.

Definition of Business Capability Model

A business capability model is a formal description of an organization's capabilities, organized in levels, with a definition for each capability and, often, attributes such as owner, strategic importance and maturity.

The terms model and map are often used interchangeably. Where a distinction is made, the model is the full set of definitions and relationships, while the business capability map is the visual, usually single-page view drawn from it. Both are central to business architecture.

Elements of a Capability Model

Each capability has a name, usually a noun phrase, and a short definition stating what it achieves. Good definitions describe outcomes rather than activities or systems.

Capabilities are arranged in levels. Level one covers broad areas, such as customer management or finance, while levels two and three break these into more specific capabilities.

Attributes may include an owner, strategic importance, current maturity, target maturity and risk. These attributes support heat maps and investment analysis.

Relationships link capabilities to value streams, organization units, information, applications and initiatives.

Principles of Good Capability Modeling

Capabilities should be stable. A capability describes what the organization does, which changes slowly, rather than how it does it, which changes often. A bank has needed to manage loans for centuries, even though the way it does so has changed many times.

Capabilities should be unique and non-overlapping, so that each application, cost or project maps clearly to one place.

Capabilities should be independent of the organization chart. If two departments perform the same capability, it appears once in the model. Naming capabilities after departments or systems is a common mistake that makes the model fragile.

Importance of Business Capability Models in Enterprise Architecture

The capability model gives business and technology a shared vocabulary. When everyone uses the same definitions, discussions about priorities and investments become more precise.

It provides a stable structure for analysis. Applications, costs, projects and risks can be linked to capabilities, producing views that remain valid through reorganizations and system changes. Trends can be tracked over several years because the underlying structure stays the same.

It also supports comparison. Organizations with several divisions or recent acquisitions can use one model to compare how each performs and supports the same capabilities.

Linking Capabilities to Spending

Mapping applications and their costs to capabilities shows how much the organization spends to support each one. This view is often more meaningful to business leaders than spending by department or technology type.

Comparing spending with strategic importance highlights mismatches, such as heavy spending on a low-priority capability or underinvestment in a critical one.

Cost frameworks such as the TBM taxonomy organize the technology side of spending, while the capability model provides the business view, and many organizations link the two.

This connection is the basis for capability-based planning, where investment decisions are framed in terms of the capabilities they improve.

Common Pitfalls

Models that mix capabilities, processes and departments become confusing and hard to maintain.

Models that go too deep, with hundreds of level four capabilities, are rarely kept current and overwhelm their audience.

Models built without business involvement may be technically sound but fail to win the support needed for decisions. Validation with business leaders is essential. Business leaders are also best placed to judge strategic importance, which is one of the model's most used attributes.