Study guide
4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping
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.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping
Key Takeaways Explain This Topic AI
A Value Stream represents an end-to-end collection of value-adding activities that creates an overall outcome for a customer, stakeholder, or end user, triggered by an external demand and culminating in a distinct value proposition.
A value stream is decomposed into sequential Value Stages, each characterized by an entry condition, participating stakeholders, value items produced, and exit criteria.
While Business Processes model internal operational workflows, detailed decision gateways, and functional orchestration (inside-out), Value Streams model stakeholder-centric value realization (outside-in).
Capability Cross-Mapping connects each value stage to the specific business capabilities required to deliver that stage's value, establishing direct traceability between internal enterprise abilities and customer outcomes.
Identifying capability deficiencies through value stream cross-mapping enables enterprise architects to pinpoint exactly which operational or technical bottlenecks prevent the realization of corporate strategic goals.
Last updated: October 2026
4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping
In the TOGAF Standard, value-driven architecture is realized through the formal modeling of Value Streams and their explicit cross-mapping to Business Capabilities . As documented in the TOGAF Series Guide: Value Streams , an enterprise cannot understand the true value of its internal capabilities without analyzing how those capabilities combine to serve external customers. While capabilities define what the business does, value streams define why those abilities matter by demonstrating how they generate tangible business value from the perspective of an external stakeholder.
The Strategic Role of Value Streams in Enterprise Architecture
A Value Stream is defined by The Open Group as an end-to-end collection of value-adding activities that creates an overall result for a customer, stakeholder, or end user . Value streams provide a stakeholder-centric, "outside-in" perspective on the enterprise, anchoring architectural design directly to value realization.
Historically, enterprise architectures were designed primarily along functional or technical boundaries—optimizing sales systems, warehousing databases, or accounting mainframes in isolation. This functional optimization frequently produced severe cross-functional friction: while each individual department met its internal performance metrics, the customer experienced sluggish service, dropped handoffs, and disjointed communication. Value streams solve this challenge by tracing horizontal value delivery across all departmental and functional silos.
Anatomy of a Value Stream: Triggers, Stages, Value Items, and Outcomes
A value stream is structured with rigorous architectural components:
Triggering Event : The initiating condition or request originated by a stakeholder that activates the value stream (e.g., Customer submits a home mortgage application or Fleet manager detects vehicle engine failure ).
Value Stages : The discrete, sequential steps through which value progressively accumulates. A typical value stream consists of 4 to 8 high-level stages. Each stage represents a meaningful progression toward the end outcome.
Participating Stakeholders : The internal and external personas who engage with or contribute to the value stream at specific stages (e.g., Prospective Homebuyer, Loan Officer, Underwriter, Escrow Agent ).
Value Items (Stage Outputs) : The incremental value produced upon exiting a specific stage (e.g., Validated Applicant Dossier, Credit Risk Determination, Disbursed Loan Proceeds ). A value item is not merely a work artifact; it is an incremental asset of value to the recipient.
Final Value Proposition : The overarching outcome delivered to the initiating stakeholder at the conclusion of the value stream (e.g., Secured Home Ownership Financing ). [Trigger: Home Purchase Contract Signed]
- │
- ▼
- ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐
- │ Apply for │ ──> │ Assess Credit │ ──> │ Underwrite │ ──> │ Settle & │
- │ Financing │ │ & Collateral │ │ Commitment │ │ Disburse │
- └───────────────┘ └───────────────┘ └───────────────┘ └───────────────┘
- │ │ │ │
- [Pre-Approval] [Risk Score] [Binding Contract] [Home Ownership Funds]
- │
- ▼
- [Final Value Proposition]
- Value Streams versus Business Processes: Outside-In versus Inside-Out
A cornerstone topic tested on the OGEA-103 examination is distinguishing between Value Streams and Business Processes. While both involve activities, they operate at different levels of abstraction, serve different audiences, and utilize different modeling conventions:
Architectural Attribute Value Stream (TOGAF Series Guide) Business Process (BPMN / Operational)
Perspective Outside-In : Focuses on value realization from the perspective of the customer, stakeholder, or consumer. Inside-Out : Focuses on the internal execution mechanics, efficiency, and task orchestration of the enterprise.
Focus Value Delivery : What value is being progressively created at each stage of the journey? Operational Workflow : How are tasks executed, routed, automated, and governed?
Linearity & Logic Strictly Linear Progression : Value streams do not contain decision diamonds, conditional branching (IF/THEN), exception loops, or message queues. Branching & Exceptions : Explicitly models alternative paths, error handling, parallel forks, escalation timeouts, and rollback loops.
Level of Granularity Abstract & Strategic : Typically 4 to 8 coarse-grained stages across the entire end-to-end journey. Detailed & Operational : Granular task sequences, system transactions, role assignments, and sub-second execution SLAs.
Primary Audience Business Executives, Enterprise Architects, Strategy Planners, Product Owners. Process Engineers, Software Developers, Workflow Integrators, Operational Line Managers.
Governing Question "What outcome does the stakeholder receive, and why does it matter?" "How does the system or employee execute step 4b, and what happens if a timeout occurs?"
The Technique of Value Stream Mapping
When developing value streams during Phase B, enterprise architects execute a systematic four-step procedure:
Identify the Core Value Streams : Review corporate business strategies, product portfolios, and Phase A business scenarios to identify the primary value journeys (e.g., Concept-to-Market, Lead-to-Quote, Order-to-Cash, Incident-to-Resolution ).
Define the Value Stages : Decompose each value stream into sequential stages. Each stage name should be expressed using a verb-noun or active phrasing reflecting progress (e.g., Select Product, Submit Order, Fulfill Items, Settle Account ).
Specify Entry Criteria, Exit Criteria, and Value Items : For each stage, articulate what condition must be met to enter, what incremental value item is created, and what criteria determine successful completion.
Identify Primary Stakeholders : Document the external customer receiving the final value proposition and the internal organizational personas supporting each stage.
Capability Cross-Mapping: Connecting Outcomes to Enterprise Capabilities
A value stream describes the journey of value creation, but it cannot deliver value on its own. Enterprise capabilities are the operational engines that empower each stage of the value stream. The technique of Capability Cross-Mapping links value stream stages to the business capabilities required to execute them.
The Cross-Mapping Matrix
Architects construct a two-dimensional matrix where columns represent sequential Value Stages and rows represent Business Capabilities:
Business Capability Stage 1: Order Placement Stage 2: Inventory Reservation Stage 3: Payment Processing Stage 4: Order Fulfillment Stage 5: Delivery Logistics
- Catalog Browsing Core - - - -
- Customer Identity Mgmt Core - Supporting - -
- Inventory Management - Core - Supporting -
- Credit Card Settlement - - Core - -
- Warehouse Management - Supporting - Core Supporting
- Carrier Transportation - - - Supporting Core
- Customer Notification Supporting Supporting Supporting Supporting Supporting
In this matrix:
Core : The capability is directly responsible for creating the stage's primary value item.
Supporting : The capability provides necessary auxiliary data, infrastructure, or administrative assistance.
Diagnostic Analysis: Identifying Value Bottlenecks and Investment Targets
The true power of capability cross-mapping lies in its diagnostic utility. When an enterprise suffers from poor customer satisfaction or degraded business outcomes, the root cause is rarely the value stream structure itself; rather, it is a deficient underlying capability.
Tracing Bottlenecks: A Diagnostic Scenario
Suppose a global e-commerce enterprise observes that customer cart abandonment spikes and delivery satisfaction drops during the holiday season. The architect overlays the Capability Assessment Heat Map (from Section 4.2) onto the Value Stream Cross-Mapping Matrix :
Value Stream Stage 2: Inventory Reservation relies on the business capability Inventory Management .
In the capability assessment, Inventory Management was heat-mapped as RED due to batch-mode inventory databases that synchronize only once every six hours (Technology: Low; Information: Low).
Architectural Insight : Because Inventory Management cannot calculate stock availability in real time, Stage 2 frequently confirms orders for out-of-stock items, causing downstream fulfillment cancellations in Stage 4.
Target Architectural Recommendation : Rather than attempting to redesign the customer-facing mobile application, the architect targets Phase C data architecture (real-time distributed event streaming) and Phase C application architecture (event-driven inventory microservice) to resolve the red capability directly.
This auditable chain of causation—connecting customer dissatisfaction at a value stage directly to technical debt within an underlying capability—demonstrates the strategic value of enterprise architecture to corporate leadership.
Practitioner Exam Traps: Avoiding Process-Modeling Habits
The Conditional Branching Anti-Pattern : Inserting decision diamonds (e.g., "Credit Score > 700? Yes/No" ) into a value stream diagram. Value streams represent pure, end-to-end value realization chains. Decision logic, exception routing, and conditional loops belong strictly in business process models.
The One-to-One Mapping Fallacy : Assuming that each capability serves only one value stream. In reality, a mature capability (such as Customer Identity Verification or Payment Settlement ) is reused across dozens of distinct value streams across the enterprise.
Confusing Value Propositions with Work Deliverables : Identifying an internal report, an invoice PDF, or a database record as a value proposition. A value proposition is the tangible benefit delivered to a stakeholder (e.g., Reliable Commercial Transportation or Seamless Digital Checkout ), whereas work products are mere operational artifacts.