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

Best Practice: Connect Strategy to Capabilities

Description

Strategic goals should be mapped to the capabilities required to achieve them. The model should help leaders see which capabilities are most important to strategic outcomes, which are already strong enough to support those outcomes, and which require improvement before the strategy can be executed reliably.

This mapping should not stop at a high-level statement that a strategy depends on a broad capability area. Where possible, goals should be linked to the specific branch or leaf capabilities that must change, mature, scale, automate, or become more resilient. The resulting view allows strategy conversations to move from aspiration to specific enterprise abilities that can be funded, governed, and improved.

Benefit(s)

Connecting strategy to capabilities makes strategy execution more concrete. It helps executives, strategy teams, architects, and portfolio leaders understand which enterprise abilities must be strengthened to achieve target outcomes.

This practice also improves investment discipline. Instead of funding isolated projects, the enterprise can fund capability improvements that have clear strategic relevance and can be traced to measurable business, operational, regulatory, or technology outcomes.

Best Practice: Distinguish Current-State, Target-State, and Transition Views

Description

The Enterprise Capability Model (ECM) should support current-state, target-state, and transition-state views. The current-state view describes what exists today, including present maturity, health, ownership, application support, data support, operational performance, and known gaps. The target-state view describes what the enterprise needs the capability to become in order to support future strategy, operating models, regulatory obligations, customer expectations, or technology direction.

The transition-state view connects the two. It shows the planned path from current to target, including interim capability improvements, enabling initiatives, sequencing dependencies, investment needs, and risk mitigation activities. These views should be explicit enough to guide planning, not merely implied through project lists or architecture diagrams.

Benefit(s)

Distinguishing current-state, target-state, and transition-state views helps the enterprise avoid confusing the model of what exists with the model of what is desired. It gives decision-makers a clearer understanding of capability gaps and the work required to close them.

This practice also improves roadmap quality because capability change can be staged over time. Leaders can see which improvements are foundational, which are dependent on earlier work, and which can be deferred without undermining strategic objectives.

Best Practice: Build Capability-Based Roadmaps

Description

Capability-based roadmaps should identify which capabilities will be improved, added, consolidated, automated, outsourced, insourced, modernized, retired, or transformed over time. The roadmap should connect capability changes to strategy, portfolio decisions, application and technology changes, value-chain improvements, risk reduction, and operational readiness.

A capability-based roadmap should not replace project, application, or technology roadmaps. Instead, it should provide the business and enterprise context that explains why those roadmaps exist and which enterprise abilities they are intended to improve. The capability roadmap becomes the translation layer between strategic intent and execution work.

Benefit(s)

Capability-based roadmaps connect change work to enterprise abilities rather than only to projects, applications, or technologies. This helps stakeholders understand the intended business and operating-model impact of the work.

This practice also reduces fragmented planning. When multiple projects, applications, data initiatives, process changes, and organizational changes are all linked to the same capability improvement, the enterprise can coordinate work more effectively and avoid duplicative or conflicting investments.