Study guide
4.2 Business Capabilities, Capability Mapping, and Assessment
TOGAF Enterprise Architecture Practitioner OGEA-103
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Mechanics & Foundation Overview
1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise
2 Chapter 2: Preliminary Phase & Establishing the EA Capability
2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools
3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)
3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
4 Chapter 4: Business Architecture (Phase B)
4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates
5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)
5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements
6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)
6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions
7 Chapter 7: Technology Architecture (Phase D)
7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models
8 Chapter 8: Opportunities and Solutions (Phase E)
8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management
9 Chapter 9: Migration Planning (Phase F)
9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps
10 Chapter 10: Implementation Governance (Phase G)
10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists
11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management
11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict
12 Chapter 12: Architecture Governance, Boards, and Dispensations
12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts
13 Chapter 13: Architecture Content Framework & Architecture Repository
13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository
14 Chapter 14: EA Capability, Tailoring, and Iteration
14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security
4.2 Business Capabilities, Capability Mapping, and Assessment
Key Takeaways Explain This Topic AI
TOGAF defines a Business Capability as a particular ability that a business may possess or exchange to achieve a particular purpose: it describes what the enterprise does, not how or by whom.
Capabilities are named with nouns or noun phrases (e.g., Policy Administration, Customer Relationship Management, Payment Settlement), deliberately avoiding organizational department names.
Capability maps are organized hierarchically across levels (Level 1 broad domains, Level 2 operational capabilities, Level 3 granular building blocks) and stratified into Strategic, Core, and Supporting tiers.
Capability assessment evaluates each capability across four fundamental dimensions—People, Process, Technology, and Information—scoring maturity, business value, risk, and performance gaps.
Capability Heat Mapping visualizes assessment results through color-coded matrices (e.g., red for high gap/critical priority, yellow for moderate, green for satisfactory), directing strategic investment to areas of highest architectural leverage.
Last updated: October 2026
4.2 Business Capabilities, Capability Mapping, and Assessment
In modern enterprise architecture practice, the Business Capability is the central building block of Business Architecture. As articulated in the TOGAF Series Guide: Business Capabilities , business capability mapping bridges executive strategy and technological execution. By abstracting enterprise abilities away from organizational politics and technical implementation details, business capabilities provide an enduring architectural foundation that withstands corporate reorganizations, mergers, and technology refresh cycles.
Understanding Business Capabilities: The Anchor of Architecture
The TOGAF Enterprise Metamodel defines a Business Capability as a particular ability that a business may possess or exchange to achieve a particular purpose . It defines the general term Capability as an ability that an organization, person, or system possesses . Capabilities represent the fundamental capacities an enterprise requires to deliver value to its customers, partners, and internal stakeholders.
The defining characteristic of a business capability is its long-term stability:
Corporate leadership and organizational charts change frequently (often annually).
Software applications, databases, and programming languages are upgraded or replaced every three to seven years.
Infrastructure platforms transition from on-premises mainframes to virtual machines, private clouds, and public cloud containers.
Yet, an international commercial airline's capability to Manage Flight Reservations or an insurance company's capability to Adjudicate Claims remains fundamentally unchanged over decades.
Because capabilities evolve slowly, they serve as the ideal baseline against which enterprise architects align IT investments, evaluate strategic gaps, and plan multi-year digital transformations.
The "What" versus "How" and "Who" Architectural Separation
A critical distinction tested on the OGEA-103 examination is the boundary between capabilities, processes, organizations, and technologies:
Capability = What : Defines what the enterprise does to create value (e.g., Fraud Detection ). It describes an intrinsic capacity or ability, completely independent of how that ability is currently executed.
Process = How : Defines how the capability is delivered through orchestrated, sequential tasks, decision gateways, and workflow handoffs (e.g., Automated Transaction Screening Procedure via Rule Engine ).
Organization = Who : Defines who is accountable for or executes the capability (e.g., Financial Crimes Investigation Unit ). Organizational structures can be reorganized without altering the underlying capability.
Application / Technology = With What : Defines the technological systems and tools that automate and support the capability (e.g., Machine Learning Anomaly Detection Microservice ).
Conflating these concepts is an architectural anti-pattern. If an architect models "Billing Department" or "SAP Ledger System" as a business capability, the capability map will immediately degrade upon the next corporate restructuring or software migration.
Capability Naming Conventions and Common Anti-Patterns
The TOGAF Series Guide: Business Capabilities recommends naming conventions that keep capabilities stable and distinct from organization units, systems, and processes:
Standard Syntax : Capabilities must be expressed as a Noun or a Noun followed by a qualifying Verb/Gerund or Noun Phrase .
Valid Examples : "Customer Account Management," "Risk Underwriting," "Product Engineering," "Inventory Optimization," "Regulatory Compliance Reporting."
Avoid Departmental Names : Never name a capability after an organizational silo (e.g., "Human Resources Department," "Marketing Team").
Avoid Software Product Names : Never name a capability after an IT asset or vendor product (e.g., "Salesforce Platform," "Oracle Financials").
Avoid Process Action Sentences : Never name a capability as a procedural command or process step (e.g., "Send Invoices to Clients," "Review Daily Log Files").
Structuring the Capability Hierarchy: Levels and Stratification
To manage complexity across large corporations, business capabilities are structured into hierarchical decompositions and functional stratifications.
Hierarchical Decomposition (Levels)
Capability mapping decomposes capabilities from broad enterprise domains down to fine-grained building blocks:
Level 1 (Top-Level Domains) : Broad functional categories that collectively define the total scope of the enterprise. A Level 1 map is usually a small set of broad capabilities (e.g., Customer Relationship Management, Financial Resource Management, Supply Chain Management ).
Level 2 (Operational Capabilities) : Distinct, self-contained business capabilities nested under each Level 1 domain. Level 2 capabilities provide the primary level of granularity for enterprise portfolio management, investment allocation, and architectural gap analysis (e.g., under Customer Relationship Management : Customer Acquisition, Customer Service Delivery, Loyalty Program Administration ).
Level 3 (Execution Building Blocks) : Granular capabilities providing specialized support to Level 2 capabilities (e.g., under Customer Acquisition : Lead Scoring, Identity Verification, Know-Your-Customer [KYC] Screening ).
Stratification Tiers (The Three Bands)
To ensure balanced coverage, capability maps are stratified into three distinct horizontal categories:
Stratification Tier Strategic Purpose Core Enterprise Characteristics Typical Examples
Strategic Capabilities Direction & Oversight Focus on long-range vision, executive governance, capital allocation, and market positioning. Strategic Planning, Enterprise Architecture, Corporate Brand Management, Mergers & Acquisitions.
Core Capabilities Value Creation & Delivery Directly deliver products, services, and experiences to external customers; represent the primary competitive advantage of the firm. Product Design, Loan Origination, Manufacturing Operations, Retail Order Fulfillment.
Supporting Capabilities Enterprise Enablement Provide essential shared services and infrastructure that enable Core and Strategic capabilities to function smoothly. Human Capital Management, Legal Counsel, Corporate Procurement, IT Infrastructure Operations.
Multi-Dimensional Capability Assessment: People, Process, Technology, and Information
A business capability is not merely an abstract box on a slide; it is realized in practice through the orchestration of four interdependent enterprise dimensions:
People : The personnel, leadership, organizational culture, professional skillsets, competencies, and talent pipelines required to execute the capability.
Process : The documented business processes, operational policies, control frameworks, and standard operating procedures that govern how work is performed.
Technology : The business applications, software tools, integration infrastructure, and physical hardware that automate and support the capability.
Information : The underlying data entities, knowledge assets, analytics models, and data governance standards utilized and generated by the capability.
When assessing a capability's health, architects evaluate all four dimensions simultaneously. A common failure in digital transformation occurs when an enterprise invests $50M in modern Technology (cloud software) while ignoring People (lack of skilled engineers) and Information (fragmented, inaccurate legacy data), leaving overall capability maturity unchanged.
Capability Heat Mapping: Visualizing Gaps to Guide Investment
Once the capability hierarchy is established and assessed across the four dimensions, architects conduct Capability Heat Mapping . Heat mapping applies color-coded visual overlays to the capability map to convey complex analytical findings to executive stakeholders:
Heat Mapping Criteria :
Maturity Gap : Comparing Current Maturity (e.g., Level 1 Ad-Hoc) against Target Maturity (e.g., Level 4 Quantitatively Managed).
Strategic Importance : Differentiating between core competitive differentiators (High Importance) and commodity back-office capabilities (Low Importance).
Operational Risk / Technical Debt : Identifying capabilities vulnerable to cyber threats, single points of failure, or severe regulatory non-compliance.
Business Value Potential : Estimating the return on investment (ROI) derived from capability uplift.
Color-Coding Semantics
Red (Critical Investment Priority) : High strategic importance combined with severe capability deficiencies (low maturity, fragile technology, or poor data quality). Red capabilities receive top priority in candidate roadmap components.
Yellow / Amber (Moderate Attention) : Moderate gaps or capabilities undergoing controlled evolution.
Green (Healthy / Differentiating) : Operating effectively at target maturity with robust technical and process enablement.
Blue / Gray (Commodity / Candidate for Outsourcing) : Low strategic differentiation and acceptable performance; prime candidates for commercial SaaS adoption or third-party business process outsourcing (BPO).
Enterprise Case Scenario: Retail Banking Modernization
Consider an international retail bank executing a digital modernization program. The enterprise architect models the Level 2 capability Commercial Loan Underwriting under the Level 1 domain Credit Operations :
Strategic Context : Executive leadership mandates reducing commercial loan approval times from 14 days to under 4 hours to defend market share against agile fintech lenders.
Capability Assessment Findings :
People Dimension (Maturity: High) : Highly experienced senior credit analysts with deep risk assessment expertise.
Process Dimension (Maturity: Medium) : Rigorous underwriting guidelines, but laden with manual document handoffs and paper signing steps.
Technology Dimension (Maturity: Low) : Core underwriting calculations executed in disconnected desktop spreadsheets and legacy 3270 terminal green-screen applications.
Information Dimension (Maturity: Low) : Applicant credit histories manually re-keyed from PDF attachments; absence of automated API connections to corporate credit bureaus.
Architectural Diagnosis & Heat Map Result : The capability is designated RED (Critical Gap) . Despite outstanding human capital, technological obsolescence and manual information flows create a catastrophic operational bottleneck.
Downstream ADM Impact : In Phase B, the architect specifies target automated underwriting processes. In Phase C, the architect mandates RESTful credit bureau integration and unified borrower data schemas. In Phase E, this capability is packaged into a high-priority work package named "Automated Credit Decisioning Engine."
Practitioner Exam Traps and Level-of-Detail Pitfalls
The Granularity Explosion : Decomposing capability maps down to Level 5 or 6 during Phase B. Decomposing beyond Level 3 in enterprise-wide architecture creates unwieldy, unmaintainable models that confuse stakeholders. Fine-grained functional decomposition belongs in detailed solution design.
The Technology-Centric Assessment : Evaluating capability maturity purely by inspecting server ages or software release versions. A capability supported by brand-new software can still be failing if staff lack training or if business data is corrupted.
Ignoring Strategic Weight : Allocating equal transformation funding to every red box on a heat map. If an operational capability is red but carries low strategic significance (e.g., Cafeteria Meal Scheduling ), it should receive minimal investment compared to a red core revenue-generating capability.