Theory 20 minutes + Workshop 60 minutes
Duration: 80 minutes. Artefact produced: Architecture Vision one-page brief.
Module Overview
Explain why Architecture Vision is the executive intent layer, not a documentation exercise.
State the decision the architecture must enable and the outcome the sponsor expects.
Define what is in scope, out of scope, constrained, and politically sensitive.
Translate business ambition into measurable architecture success criteria.
Theory
Phase A is where architecture becomes legitimate. The purpose is not to produce a beautiful document; it is to establish why the work exists, what decision it enables, who owns the outcome, what boundaries apply, and what success will look like. A weak vision creates endless rework because every later artefact has to guess the intent.
Workshop
The CIO has asked for a cloud migration, but the executive team is split. Finance wants cost reduction, clinical leaders want reliability, security wants control, and delivery teams want fewer platform constraints.
Create a one-page Architecture Vision brief that states the business driver, decision to be made, target outcome, constraints, stakeholders, scope, and success measures.
Before you design the cloud target state, explain the Architecture Vision you would establish with the executive sponsor.
One-page Architecture Vision brief; stakeholder list; decision statement; five success criteria; three explicit constraints.
Module 3 — BDAT Baseline and Gap Analysis. Planned.