Phase A: Architecture Vision — Selling the Future Before You Build It

Phase: Phase A — Architecture Vision Perspective: Enterprise Architect

Architecture Vision is not a technical document. It is a business case wrapped in strategic narrative. Your job in Phase A is to make leadership say 'yes' to a journey they do not yet fully understand.

Key Inputs

Architecture principles from Preliminary Phase
Business strategy and goals
Capability assessments
Existing architecture landscapes
Stakeholder concerns and requirements
Request for Architecture Work

The Process

Identify and engage key stakeholders
Confirm business context and drivers
Define the scope of the architecture work
Create the Architecture Vision statement
Assess capability gaps at high level
Develop Statement of Architecture Work
Obtain formal sign-off

Deliverables

Architecture Vision document
Statement of Architecture Work
Stakeholder Map and concerns register
Refined principles
Communications plan
Approved scope and constraints

Practitioner Perspective

Phase A sets the mandate. If you rush past it, you will spend Phases B through D doing technically brilliant work that nobody asked for. The Architecture Vision must answer three questions clearly: what changes, for whom, and why now?

Map your stakeholders early — identify the blockers as well as the champions. A stakeholder who is not engaged in Phase A will derail you in Phase G. Use value chain analysis to show where architecture creates business value in terms the CFO understands, not the CTO.

The Statement of Architecture Work is your contract with the organisation — treat it with the same seriousness as a legal agreement. It defines scope, constraints, roles, and what "done" looks like.

The most common mistake: Defining the Architecture Vision in a room full of IT people. Business architecture vision requires business voices. If your stakeholder map is IT-heavy, stop and fix it before proceeding.

Practical tips:

Use a "motivation diagram" to connect strategic drivers → goals → objectives → architecture requirements — it creates a traceable narrative
Run a SWOT or PESTLE analysis to surface external drivers that strengthen your case
Write the Vision for a non-technical executive — if they cannot understand it, rewrite it
Get written sign-off on the Statement of Architecture Work — verbal agreement dissolves under pressure

Part of a series: TOGAF from an Enterprise Architect's Perspective