Study guide
3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
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
3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
Key Takeaways Explain This Topic AI
The Architecture Vision deliverable articulates the high-level baseline and target architecture summaries, value proposition, and solution concept.
The Communications Plan sets out where, how, and when the architects will communicate with each stakeholder group, using the classes from the Stakeholder Map.
The Statement of Architecture Work (SoAW) functions as the binding charter and formal governance contract between the architecture team and executive leadership for Phases B through H.
Formal sign-off on the SoAW by the Executive Sponsor is the mandatory Phase A governance gate required before committing enterprise resources to Phase B.
Last updated: October 2026
3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval
Phase A serves as the critical gating mechanism of the entire TOGAF Architecture Development Method (ADM). Up to this point, the enterprise architect has ingested the triggering business mandate, scoped project boundaries, analyzed stakeholders, and elicited authentic business requirements. The final activities of Phase A assemble these findings into three foundational deliverables: the Architecture Vision , the Communications Plan , and the Statement of Architecture Work (SoAW) . Securing formal executive sponsor approval on the SoAW represents the non-negotiable governance exit gate of Phase A, authorizing the architecture team to commit capital, mobilize subject matter experts, and transition into detailed architectural modeling in Phase B.
Assembling the Architecture Vision Deliverable
The Architecture Vision is the primary public-facing deliverable of Phase A. It provides executive sponsors, operational leaders, and technical teams with a shared mental model of the future state enterprise. Rather than presenting low-level technical specifications, the Architecture Vision communicates strategic business intent and architectural direction in clear, compelling, executive-ready language.
Typical Contents of the Architecture Vision
The TOGAF Standard lists the typical contents of the Architecture Vision deliverable as:
Problem description : the stakeholders and their concerns, and the issues or scenarios to be addressed.
Objective of the Statement of Architecture Work.
Summary views : the views needed for the Request for Architecture Work, plus first-cut (version 0.1) Business, Data, Application, and Technology Architectures.
Business scenario (optional).
Refined key high-level stakeholder requirements.
In practice architects also make the value proposition explicit. Phase A step 9 asks for the business case, value propositions for each stakeholder group, and KPIs, and these are incorporated into the Statement of Architecture Work so performance can be tracked. A common way to communicate the vision is a simple Solution Concept diagram : a high-level picture of the major components of the solution and how they benefit the enterprise, free of vendor or deployment detail so non-technical leaders can follow it.
Formulating and Tailoring the Communications Plan
Communication is not an ad-hoc, informal task; in the TOGAF Standard, it is a managed architectural discipline. The Communications Plan created in Phase A ensures that relevant, accurate, and consistent architectural information reaches the right stakeholders at the right time through appropriate channels.
The enterprise architect builds the Communications Plan by directly cross-referencing the Power/Interest Grid developed during stakeholder analysis: ┌────────────────────┬─────────────────────────────────┬───────────────────┬──────────────────────┐
- │ Stakeholder Group │ Communication Content │ Delivery Channel │ Frequency & Cadence │
- ├────────────────────┼─────────────────────────────────┼───────────────────┼──────────────────────┤
- │ Key Players │ Strategic decision papers, │ Face-to-face │ Bi-weekly sprint │
- │ (Sponsor, CIO, BU) │ milestone reviews, risk logs, │ steering sessions,│ check-ins, monthly │
- │ │ trade-off matrices, budget state│ executive decks │ governance reviews │
- ├────────────────────┼─────────────────────────────────┼───────────────────┼──────────────────────┤
- │ Keep Satisfied │ Statutory compliance briefs, │ Formal executive │ Monthly audit notes, │
- │ (CISO, CRO, Legal) │ security architecture summaries,│ memos, governance │ regulatory milestone │
- │ │ data sovereignty audit proofs │ dashboards │ checkpoints │
- ├────────────────────┼─────────────────────────────────┼───────────────────┼──────────────────────┤
- │ Keep Informed │ Solution roadmaps, operational │ Town halls, demos,│ Monthly release │
- │ (Users, Ops, Devs) │ impact notes, brown-bag demos, │ video walkthroughs│ webinars, bi-weekly │
- │ │ training schedules, API changes │ intranet portal │ team newsletters │
- ├────────────────────┼─────────────────────────────────┼───────────────────┼──────────────────────┤
- │ Minimal Effort │ High-level project milestones, │ Enterprise-wide │ Quarterly digital │
- │ (Peripheral Teams) │ strategic value realization │ newsletter, portal│ bulletin updates │
- │ │ summaries, general announcements│ summary │ │
- └────────────────────┴─────────────────────────────────┴───────────────────┴──────────────────────┘
The Communications Plan also establishes bi-directional feedback mechanisms . It provides formal grievance channels, architecture request-for-clarification portals, and operational feedback loops so that emergent concerns from front-line engineers or business analysts are surfaced and evaluated before designs are finalized.
Developing the Statement of Architecture Work (SoAW)
The most critical governance deliverable produced in Phase A is the Statement of Architecture Work (SoAW) . While the Request for Architecture Work (RfAW) initiated the engagement with informal business aspirations, the SoAW transforms those aspirations into a formal, binding contract between the architecture team and executive leadership.
Typical Contents of the Statement of Architecture Work
The TOGAF Standard lists the typical contents of the Statement of Architecture Work as:
- Statement of Architecture Work title
- Architecture project request and background
- Architecture project description and scope
- Overview or outline of the Architecture Vision
- Managerial approach
- Change of scope procedures
- Roles, responsibilities, and deliverables
- Acceptance criteria and procedures
- Architecture project plan and schedule
- Approvals
Phase A step 11 explains what goes into it. The team decides which domains to develop, to what level of detail, and which views to build. It estimates resources, develops a roadmap and schedule for the ADM cycle, defines the performance metrics the EA team must meet, and develops the Communications Plan. The plans are then reviewed and agreed with the sponsors, formal approval of the Statement of Architecture Work is secured under the appropriate governance procedures, and the sponsor signs off to proceed. Explicit statements of what is excluded from scope are as useful as statements of what is included.
The Phase A Governance Gate: Sponsor Sign-Off and Phase Transition
The conclusion of Phase A is marked by a formal governance gate review . In TOGAF, transitioning from Phase A to Phase B is never automatic; it requires explicit, written approval.
The Review and Sign-Off Process
Architecture Board Conformance Review : Prior to presenting the SoAW to the executive sponsor, the lead architect submits the draft Architecture Vision and SoAW to the enterprise Architecture Board. The Board verifies that the proposed scope complies with enterprise-wide architecture principles, avoids duplicating existing organizational initiatives, and leverages shared enterprise building blocks.
Executive Sponsor Gate Review : The lead architect conducts a formal gate review meeting with the primary business executive sponsor. The architect presents the Architecture Vision, demonstrates alignment with the initiating RfAW, explains the trade-offs evaluated, walks through the resource and budget requirements, and reviews the explicit acceptance criteria.
Formal Contractual Sign-Off : The Executive Sponsor signs the Statement of Architecture Work. This signature represents a binding organizational commitment: it secures the required project funding, authorizes the assignment of departmental subject matter experts, and empowers the architecture team with governance authority across subsequent ADM phases.
If the sponsor refuses to sign due to budget restrictions or scope disagreements, the architect does not proceed to Phase B. The architect iterates within Phase A, adjusting the scope boundaries, reducing the depth of models, or extending the time horizon until an acceptable SoAW is negotiated.
Common Practitioner Traps at the Phase A Gate
Enterprise architects must navigate treacherous failure modes during the final steps of Phase A:
The "Gentleman's Agreement" Fallacy : Relying on verbal executive enthusiasm or informal email confirmations instead of a formally executed SoAW. When project schedules compress or budget cuts occur in Phase C, projects lacking a signed SoAW find their resources confiscated and their authority questioned.
Premature Transition to Phase B Modeling : Commencing detailed Business Architecture process modeling or Application Architecture cataloging before the SoAW is signed. Architecture work performed without an approved SoAW represents unbudgeted, unauthorized effort that frequently must be scrapped when executive priorities shift.
Vague or Subjective Acceptance Criteria : Writing acceptance criteria such as "Deliverables must be acceptable to business leadership." In Phase G compliance reviews, subjective criteria lead to bitter disputes. Acceptance criteria must be objective and measurable (e.g., "The Architecture Definition Document must contain approved catalogs for all core banking capabilities, data entity/business function matrices, and transition roadmaps signed off by the Chief Risk Officer" ).
Treating the Vision as Immutable Dogma : Assuming that once approved, the Architecture Vision can never change. If a major macroeconomic shock, regulatory shift, or corporate merger occurs during Phase D or E, the architect must invoke the change management procedures defined in the SoAW and Phase H to adjust the Vision under formal governance control.