TOGAF Fast-Learning Mind Map

Use this document to build a mental model before memorizing details. Read the map once, redraw it from memory, then use the linked handbook sections only where your recall is weak.

For an editable visual workbook, open the three-page draw.io mind map. A printable PDF version is also available.

The whole framework on one map

mindmap
  root((TOGAF))
    Purpose
      Connect strategy to coordinated change
      Describe baseline and target
      Find gaps and sequence change
      Govern delivery and respond to change
    ADM
      Preliminary
        Establish the architecture capability
      A Architecture Vision
        Agree why scope value and authority
      B Business
        Capabilities value streams organization
      C Information Systems
        Data
        Applications
      D Technology
        Platforms infrastructure standards
      E Opportunities and Solutions
        Group gaps into work packages
        Define transition architectures
      F Migration Planning
        Prioritize and create the executable plan
      G Implementation Governance
        Govern conformance and exceptions
      H Change Management
        Monitor change and start new cycles
      Requirements Management
        Central and continuous
    Architecture Domains
      Business
      Data
      Application
      Technology
      Cross-cutting
        Security risk privacy integration
    Core Reasoning
      Drivers and goals
      Stakeholders and concerns
      Baseline
      Target
      Gaps
      Roadmap
      Delivery
      Outcomes and feedback
    Content
      Deliverables
        Formally reviewed work products
      Artifacts
        Catalogs
        Matrices
        Diagrams
      Building Blocks
        ABB required capability
        SBB implementation
    Reuse and Knowledge
      Enterprise Continuum
        Classifies generic to specific
      Architecture Repository
        Stores and governs assets
    Governance
      Principles and standards
      Decision rights
      Architecture Board
      Architecture Contract
      Compliance reviews
      Exceptions and feedback
    Ways of Working
      Tailor to context and risk
      Iterate instead of treating ADM as waterfall
      Integrate with product Agile DevOps and portfolio
      Produce only decision-useful content

The one-sentence mental model

TOGAF uses a tailored, iterative method to move from why, through what, to how and when, while requirements, stakeholders, governance, and learning keep the change coherent.

If you remember only one flow, remember this:

flowchart LR
    Why[Why change?] --> Who[Who cares and why?]
    Who --> Now[Baseline: where are we?]
    Now --> Future[Target: where are we going?]
    Future --> Gap[Gaps: what must change?]
    Gap --> Sequence[Roadmap: in what order?]
    Sequence --> Govern[Deliver and govern]
    Govern --> Learn[Measure and adapt]
    Learn --> Why

ADM: remember the questions, not just the letters

Mnemonic for the phase sequence:

Prepare A Business; Connect Digital Execution For Governed Horizons.

The ADM is a thinking cycle, not a fixed waterfall. Phases may iterate, overlap, or run at different enterprise, portfolio, product, and solution levels.

The four domains: BDAT

Use BDAT to remember the domains and their dependency:

flowchart LR
    B[Business<br/>value capabilities and operating model]
    D[Data<br/>meaning ownership flow and lifecycle]
    A[Application<br/>services responsibilities and interactions]
    T[Technology<br/>platforms infrastructure and standards]

    B --> D
    B --> A
    D <--> A
    A --> T
    D --> T

Security, risk, privacy, integration, experience, and sustainability cut across all four domains; they are not late additions.

Content: do not confuse these three

flowchart TD
    D[Deliverable<br/>formally reviewed work product]
    A[Artifact<br/>representation of architecture information]
    C[Catalog<br/>lists]
    M[Matrix<br/>relationships]
    G[Diagram<br/>structure or behavior]
    BB[Building Block<br/>reusable capability or component]
    ABB[ABB<br/>required capability]
    SBB[SBB<br/>implementation realization]

    D -->|contains| A
    A --> C
    A --> M
    A --> G
    A -->|describes| BB
    BB --> ABB
    BB --> SBB

• A deliverable is the reviewed package.
• An artifact communicates architecture information.
• A building block is a potentially reusable unit of capability.
• An ABB says what capability is required; an SBB says how it is implemented.

Reuse: continuum versus repository

Memory hook: the Continuum classifies; the Repository contains and controls.

Governance: the decision loop

flowchart LR
    P[Principles and standards] --> DR[Decision rights]
    DR --> D[Decision]
    D --> C[Architecture Contract or agreement]
    C --> I[Implementation]
    I --> R[Compliance review]
    R -->|conformant| O[Outcome evidence]
    R -->|justified deviation| E[Exception with owner and expiry]
    E --> I
    O --> F[Feedback and learning]
    F --> P

Governance is not central approval of every design. Effective governance makes decision authority, evidence, conformance, exceptions, and feedback explicit and proportional to risk.

The eight distinctions worth memorizing

How to reason through a TOGAF scenario

When a question or real situation feels complicated, use SCOPE:

1. S — Stakeholders: Who has concerns, influence, and decision rights?
2. C — Context: What phase, scope, constraints, and evidence are present?
3. O — Outcome: What business result or decision must the work enable?
4. P — Proportion: What is the smallest sufficient technique, artifact, or governance response?
5. E — Evidence: Which option preserves traceability, resolves trade-offs, and creates feedback?

Prefer answers that clarify outcomes and authority, address stakeholder concerns, tailor the method, maintain traceability, and enable governed delivery. Be suspicious of answers that create every artifact, skip directly to technology, centralize every decision, or treat the ADM as a rigid waterfall.

Ninety-minute fast-learning route

Seven-day retention loop

Do not reread passively. Retrieve the model from memory:

• Day 1: redraw the main map and ADM without looking;
• Day 2: explain BDAT, content, governance, continuum, and repository aloud;
• Day 3: answer Foundation questions and record weak topics;
• Day 5: work Practitioner scenarios using SCOPE;
• Day 7: take a timed mock exam and redraw only what you missed.

For each mistake, write one flashcard with a question on the front and a one-sentence distinction or phase purpose on the back.

Self-test: close the document first

1. What problem does TOGAF solve?
2. What question does each ADM phase answer?
3. Why is Requirements Management central?
4. How do the four BDAT domains depend on one another?
5. What is the difference between an artifact and a deliverable?
6. What is the difference between an ABB and an SBB?
7. How does the Enterprise Continuum differ from the Architecture Repository?
8. Why is governance more than Architecture Board approval?
9. Why are transition architectures useful?
10. What makes tailoring responsible rather than incomplete?

If you can answer all ten clearly and apply SCOPE to a scenario, you have the core TOGAF mental model. Continue with the ADM deep dive, quick reference, and mock exam.