Designing, Building, and Maintaining Comprehensive and Usable Enterprise Capability Models

A capability is not realized by a name in a hierarchy. It is realized through a combination of people, roles, processes, applications, data, technologies, vendors, policies, controls, metrics, funding, and operating practices. The Enterprise Capability Model (ECM) should help stakeholders understand these realization dimensions.

Best Practice: Represent How Capabilities Are Realized

Description

Each significant capability should be explainable in terms of how it is realized. The model should identify or link to the people and roles involved, the processes that perform the work, the applications and technologies that enable the work, the data and information needed, the vendors or suppliers that support delivery, and the governance mechanisms that guide or constrain the capability.

Realization modeling should be fit for purpose. Some capabilities require only lightweight realization detail. Others, especially strategic, regulated, risky, or transformation-critical capabilities, may require deeper realization views.

Benefit(s)

Representing realization dimensions helps stakeholders understand what it takes to perform, sustain, improve, automate, outsource, insource, modernize, or retire a capability. It also provides the context needed for meaningful maturity and health assessments.

Implementation Guidance

Use a consistent realization model so that teams examine each capability through comparable dimensions. The following dimensions are a practical starting point.

Best Practice: Use Realization Relationships for Analysis

Description

Realization relationships should be used to analyze capability support, maturity, health, risk, cost, investment, and improvement needs. A weak capability may not be weak because the capability is poorly defined. It may be weak because it lacks the right applications, has outdated processes, depends on fragile data, lacks clear ownership, carries high regulatory exposure, or is constrained by obsolete technology.

The model should therefore help users distinguish between capability weakness and realization weakness. This distinction is important because the right remediation depends on what part of the realization stack is failing or underdeveloped.

Benefit(s)

Using realization relationships for analysis makes capability improvement more actionable. Instead of saying that a capability is immature or unhealthy, the enterprise can identify whether the problem is organizational, procedural, application-related, data-related, technology-related, vendor-related, control-related, funding-related, or measurement-related.

This practice also supports more precise investment planning. Different realization gaps require different work: process redesign, application modernization, data remediation, role clarification, vendor change, control strengthening, automation, or organizational redesign.