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

Best Practice: Include Industry-Specific, Core Business, and IT Capabilities

Description

A comprehensive Enterprise Capability Model (ECM) should include 1) industry-specific capabilities, 2) core business capabilities, and 3) Information Technology capabilities. Industry-specific capabilities describe the abilities that make the enterprise recognizable as a particular type of organization. Core business capabilities describe common enterprise functions such as Finance, Human Capital Management, Legal, Procurement, Risk, Compliance, Sales, Marketing, and Customer Management. IT capabilities describe the abilities required to acquire, build, integrate, operate, secure, support, and govern technology.

Figure: A comprehensive Enterprise Capability Model is commonly organized into three major branches: Industry-Specific Capabilities, Core Business Capabilities, and Information Technology Capabilities. These branches help ensure that the model covers what makes the enterprise unique, what most enterprises must perform, and what technology capabilities are required to enable, govern, operate, and improve the enterprise.

This three-branch structure should be treated as a practical starting scope. It helps modelers avoid building a narrow capability map that only describes a business domain, only describes administrative support functions, or only describes technology management activities. The enterprise can then decompose each branch into lower-level capabilities that reflect the organization, industry, and intended analytical use cases.

Benefit(s)

Including industry-specific, core business, and IT capabilities produces a more complete and balanced model. It allows leaders and architects to analyze the enterprise as a whole rather than as isolated functional fragments.

This structure also supports more reliable cross-domain analysis. Application portfolios, technology portfolios, operating models, value chains, risks, regulatory obligations, data assets, initiatives, and investments can be mapped against an ECM that reflects the full enterprise rather than only one management viewpoint.

Best Practice: Adapt the Top-Level Structure to the Enterprise

Description

The recommended top-level structure is a strong default, not a rigid mandate. Enterprises should adapt the structure when the nature of the organization requires it. For example, a public-sector organization may need branches that reflect public-service missions, regulatory authorities, or citizen-service domains. A diversified holding company may need industry-specific capability branches for multiple business lines. A technology company may need to expose more product, platform, engineering, and operations capabilities at higher levels.

Adaptation should be deliberate and governed. The goal is not to mirror the current organization chart or political ownership structure. The goal is to produce a stable, understandable ECM that supports analysis, planning, governance, knowledge management, and communication.

Benefit(s)

Adapting the structure allows the model to fit the enterprise without losing discipline. It gives stakeholders a model that feels relevant while preserving a consistent capability-modeling logic.

This also improves adoption. People are more likely to use a model when its top-level structure reflects how the enterprise creates value, delivers services, manages shared functions, and operates technology.

Best Practice: Provide Examples Across Capability Categories

Description

Capability models become easier to understand when readers can see practical examples across the three major capability categories. Industry-specific examples show capabilities that make an enterprise recognizable as a particular type of organization. Core business examples show shared capabilities that appear in most enterprises. IT examples show that technology management capabilities are first-class enterprise capabilities, not merely supporting activities.

The following table provides representative examples. The names are illustrative starting points that should be adapted to the enterprise, its industry, its vocabulary, and its governance needs.

Benefit(s)

Providing examples helps readers understand how the ECM can cover industry-specific, cross-enterprise business, and IT capability areas using a common modeling pattern. It also helps modelers test whether the taxonomy is too narrow, too generic, too IT-centric, or too disconnected from the enterprise’s operating reality.