Stage 2 of 8
Preliminary Phase and Architecture Vision
This stage turns architecture from a vague ambition into a formally scoped piece of work. It uses Preliminary Phase and Phase A to define the enterprise, the stakeholders, the principles, and the initial vision for change.
Read this stage in sequence on the first pass. The point is to sharpen judgement through one concrete artefact and one practical decision, not to accumulate isolated notes.
What this stage covers
Use the modules in order. The groupings below organise the sequence without changing it.
Define the enterprise and its stakeholders
These modules set the enterprise boundary, the concerns that matter, and the principles that must influence later decisions.
- 40 min. Define the architecture enterprise and its boundary
- 35 min. Map stakeholder groups and their concerns
- 35 min. Write principles with rationale and implications
Frame the problem before you model anything
Use scenarios, scope dimensions, sponsorship, and capability kickoff to stop the work drifting into documentation theatre.
- 35 min. Use business scenarios to frame architecture work
- 30 min. Use TOGAF scoping dimensions to constrain the work
- 45 min. Explain what executive sponsorship must actually provide
Turn direction into authorised work
Finish the stage with the Architecture Vision and the London kickoff pack.
- 40 min. Explain the purpose of Architecture Vision
- 40 min. Apply Preliminary Phase and Phase A to the London case
Why this stage matters
Teams often rush to diagrams without first agreeing the problem, the decision rights, or the architectural scope. TOGAF is strongest when these choices are explicit early.
London threads in this stage
- Connections reform pressure and service redesign
- Why the architecture enterprise includes regulatory and planning interfaces, not only IT
- How the first architecture vision anchors later decisions on data, systems, and delivery
Artefacts you should be able to defend
- Stakeholder concern map
- Architecture principles pack
- Statement of Architecture Work
Primary stage artefact
Stakeholder concern map
Treat this as the main artefact the stage should sharpen. If you can explain who it is for, what decision it affects, and what evidence it depends on, the stage is doing real work.
My view
A strong Phase A does not try to prove every answer. It proves that the architecture work is pointed at the right problem and has the authority to proceed.
Stage workspace
The workspace contains eleven practice tools that reinforce the skills covered in each stage. Use them alongside the reading flow or revisit them during revision.