Skip to content

Architecture Vision Checklist

Quick reference for Phase A completion.

Prerequisites

Before starting Phase A:

  • Business driver or initiative identified
  • Executive sponsor confirmed
  • Initial scope ideas exist (even rough)
  • Decision made: self-service or guided approach

Deliverables

Architecture Vision Document

Section Completeness

  • Executive Summary - 2-3 sentences, clear purpose
  • Background & Drivers
  • Business context explained
  • At least 2-3 business drivers with priorities
  • Consequences of inaction stated
  • Stakeholders
  • Sponsor identified with contact
  • Key stakeholders listed with concerns
  • Scope
  • In-scope items by domain (Business/Data/Application/Technology)
  • Out-of-scope items with rationale
  • Boundaries defined (organizational, geographic, temporal)
  • Vision
  • Target state described (3-5 sentences)
  • Key capabilities: current vs target
  • Value proposition articulated
  • Goals & Success Criteria
  • At least 2-3 measurable goals
  • Success metrics with baselines and targets
  • Constraints & Assumptions
  • Constraints listed with impact
  • Assumptions with risk if invalid
  • Risks
  • Key risks identified with probability/impact
  • Mitigation strategies defined
  • Architecture Principles
  • Relevant principles listed
  • Implications for this initiative stated
  • Next Steps
  • Recommended phases identified (B/C/D)
  • Immediate actions with owners

Stakeholder Map

  • Stakeholder Register - All stakeholders catalogued
  • Stakeholder Analysis (for each):
  • Type identified (Executive/Manager/Technical/End User/External)
  • Concerns documented
  • Success criteria from their perspective
  • Influence and interest levels
  • Engagement strategy
  • Stakeholder Matrix - Quadrant placement complete
  • Communication Plan - Format, frequency, owner per stakeholder
  • Concerns → Responses - Architecture addresses each concern

Statement of Architecture Work (if required)

  • Purpose stated
  • Objectives listed
  • Scope statement (in/out)
  • Architecture domains checked
  • Deliverables with target dates
  • Team and resource allocation
  • Budget breakdown
  • Timeline by phase
  • Governance structure
  • Review points defined
  • Risks and mitigations
  • Authorization signatures obtained

Quality Checks

Consistency

  • Vision aligns with stated business drivers
  • Scope boundaries support the vision (not too narrow/broad)
  • Stakeholder concerns addressed in vision/goals
  • Success metrics relate to stated goals
  • Constraints don't contradict the vision
  • Risks are realistic given scope and constraints

Completeness

  • No critical stakeholders missing
  • All four architecture domains considered (even if out of scope)
  • Both technical and business perspectives represented
  • External dependencies/parties identified

Clarity

  • Executive summary understandable without context
  • Scope boundaries unambiguous
  • Success criteria are measurable
  • No jargon without definition

Feasibility

  • Vision is achievable within constraints
  • Resources align with scope
  • Timeline is realistic
  • Risks have viable mitigations

Approval Readiness

  • All required sections complete
  • Quality checks passed
  • Stakeholder review completed
  • Feedback incorporated
  • Approvers identified
  • Approval meeting scheduled (if formal)

Handoff to Next Phase

  • Vision Document finalized
  • Stakeholder Map finalized
  • Statement of Architecture Work signed (if required)
  • Next phases identified and prioritized:
  • Phase B (Business Architecture) needed?
  • Phase C (Information Systems) needed?
  • Phase D (Technology Architecture) needed?
  • Open questions documented for next phase
  • Deliverables stored in agreed location

Quick Reference: Minimum Viable Vision

For lightweight projects, at minimum:

  • One-paragraph description of initiative
  • Business driver (one sentence)
  • Sponsor name
  • Key users/beneficiaries
  • In-scope and out-of-scope items
  • 2-3 success metrics
  • Top risk with mitigation

Common Gaps to Watch

Gap Why It Matters How to Fix
No success metrics Can't measure progress Ask "How would you know it worked?"
Vague scope Scope creep risk Force explicit in/out lists
Missing stakeholders Resistance later Ask "Who might be affected we haven't talked to?"
No constraints Unrealistic expectations Ask about budget, timeline, tech restrictions
Single-perspective vision Incomplete picture Validate with multiple stakeholder types