What This Guide Covers
Capability models provide a stable, business‑centric view of what an organization does, independent of how it is organized or which systems it uses. They are a powerful tool for planning, prioritizing, and communicating change — especially in complex transformation programs.
This guide explains how to define, structure, and use business capabilities in a way that is practical, lightweight, and aligned with TOGAF Business Architecture concepts such as capabilities, value streams, and organization mapping.
1. What Is a Business Capability?
A business capability describes what the organization must be able to do to achieve its objectives. It is intentionally independent of processes, organization, and technology. This separation makes capabilities a stable anchor for planning and communication.
- What: The ability to perform a business function or outcome.
- Not: A process, system, department, or project.
- Stable: Capabilities change slowly compared to org charts and applications.
In TOGAF terms, capabilities sit at the heart of the Business Architecture and provide a bridge between strategy, value streams, organization, and information systems.
2. Capability Modeling in TOGAF Business Architecture
TOGAF positions Business Architecture as the link between strategy and execution. Capabilities are one of its core artifacts, alongside value streams, organization, and information concepts.
Key TOGAF Business Architecture Elements
- Capabilities: What the business does or needs to do.
- Value Streams: How value is delivered to stakeholders across capabilities.
- Organization: Who is accountable for capabilities and value delivery.
- Information: The information required to support capabilities.
A capability map becomes more powerful when it is explicitly linked to value streams, organization units, and applications. This creates a coherent Business Architecture view that supports transformation decisions.
3. How to Build a Capability Map
Capability modeling should be collaborative, iterative, and business‑led. The goal is not to produce a perfect model, but a shared language that supports decision‑making.
Step 1 – Define Scope and Purpose
- Enterprise‑wide vs. domain‑specific capability map.
- Use cases: strategy alignment, portfolio planning, application rationalization, etc.
Step 2 – Identify Top‑Level Capabilities
- Start from strategy, operating model, and value streams.
- Use business language, not system or department names.
- Aim for 20–40 top‑level capabilities for an enterprise view.
Step 3 – Decompose into Sub‑Capabilities
- Break down capabilities where more granularity is needed for planning.
- Use 2–3 levels of depth; avoid over‑engineering.
- Keep decomposition consistent across domains.
Step 4 – Validate with Stakeholders
- Review with business owners and domain experts.
- Resolve overlaps and ambiguous naming.
- Align with existing strategic and operating model language.
4. Using Capability Maps for Planning and Prioritization
Once established, capability maps become a powerful analysis and communication tool. They provide a neutral canvas to overlay strategy, initiatives, technology, and risk.
Common Use Cases
- Strategic Alignment: Map strategic objectives to impacted capabilities.
- Portfolio Planning: Visualize which capabilities are targeted by projects.
- Application Rationalization: Map applications to capabilities to identify redundancy and gaps.
- Risk and Control Mapping: Identify critical capabilities with high risk exposure.
In TOGAF‑aligned Business Architecture, capabilities are often used as the anchor for roadmaps, showing how capability maturity and enablement evolve over time.
5. Linking Capabilities to Value Streams and Organization
TOGAF emphasizes the relationship between capabilities, value streams, and organization. This linkage turns a static capability map into a dynamic view of how value is delivered.
Capabilities and Value Streams
- Identify which capabilities support each value stream stage.
- Highlight capability gaps that limit value delivery.
- Use this view to prioritize investments where they impact value most.
Capabilities and Organization
- Map capabilities to accountable business units or roles.
- Identify fragmentation or unclear ownership.
- Support operating model design and role clarity.
6. Practical Tips and Common Pitfalls
Capability modeling is as much about facilitation and language as it is about structure. A few practical guidelines can help avoid common issues.
Good Practices
- Use clear, business‑friendly names (verb + noun where possible).
- Keep the model visually simple and easy to explain.
- Document definitions for key capabilities.
- Iterate — don’t aim for perfection in the first version.
Common Pitfalls
- Confusing capabilities with processes or systems.
- Over‑engineering the hierarchy with too many levels.
- Building the model in isolation without business input.
- Letting the model become stale by not linking it to real decisions.
Downloadable Assets
- Capability Map Template (PDF)
- Capability Definition Worksheet (PDF)
- Capability to Value Stream Mapping Template (PDF)
- Capability to Application Mapping Template (PDF)