Pattern Name: Capability-Based Planning Category: Business Architecture / EA Governance Complexity: Medium Stability: high: foundational EA practice
Technology investment decisions in most organizations are made project by project, business unit by business unit, with limited visibility of how proposed investments relate to the broader enterprise capability landscape. Projects are approved on their individual business cases, which rarely account for duplication, dependencies, or the strategic importance of the underlying capabilities being developed. The result is sub-optimal portfolio allocation: over-investment in some capabilities, chronic under-investment in others, and a proliferation of redundant systems.
Capability-based planning uses a structured map of what the organization does: its capabilities: as the primary instrument for investment decision-making.
How do you make technology and operational investment decisions that are consistently aligned with strategic priorities, account for the full portfolio of existing capabilities, and avoid redundancy: across a complex organization where individual business units each have their own investment cases?
Without a shared capability vocabulary and map, different business units describe their needs in incompatible terms. IT investments are justified by project-level business cases that do not surface enterprise-level patterns: such as three different business units each proposing to build their own customer portal. Architecture decisions get made in isolation, and strategic gaps are only visible in hindsight.
Define and maintain a capability map: a stable, hierarchical decomposition of what the organization does, independent of how it is organized, which systems it uses, or which processes it follows. Use the capability map as the primary framework for:
The capability map is a business architecture artefact, not a technology artefact. Capabilities are named from a business perspective (“Customer Onboarding”, “Claims Processing”, “Regulatory Reporting”) and are stable over time even as the systems, processes, and people that realize them change.
Element types to use:
Diagram types: ArchiMate Capability Map diagram (hierarchical layout of capabilities); ArchiMate Motivation viewpoint linking capabilities to strategic drivers; heat map diagram views using color coding on the tagged value ratings; application-to-capability mapping view
MDG considerations: The capability element type with its rating tagged values is the governance instrument for capability-based planning. Create a custom «Capability» stereotype (extending ArchiMate’s Capability) with mandatory tagged values for strategic importance, current performance, and owner. Add validation rules that prevent capabilities from being rated without an assigned owner: ownership accountability is what makes the ratings credible. Build a model search template that produces the heat map data for export to Power BI via EA GraphLink.
Package structure: A Business Architecture package with a Capability Map sub-package (the canonical map), a Strategic Alignment sub-package (capabilities linked to strategic objectives), and an Application Portfolio Mapping sub-package (capabilities linked to supporting applications). Maintain version history through Sparx EA baselines: the capability map should be baselined at each annual planning cycle to enable year-on-year comparison.
EA GraphLink and AI integration: Capability-based planning is where EA delivers its highest strategic value: and where AI assistance is most impactful. With EA GraphLink connected, executives and planners can ask AI tools: “Which capabilities are rated low performance but high strategic importance?”, “What applications support the Customer Acquisition capability?”, “Which strategic objectives have no strongly performing capabilities behind them?”. These are the questions that drive investment decisions. Making them answerable in natural language: without waiting for an architect to produce a report: changes the cadence and quality of strategic planning conversations.
Talk to a Sparx Services architect about where your organization is on the journey and what the next stage looks like.