- What Domain 3 Actually Covers
- Why This Domain Matters More Than Its Weight Suggests
- The ADM Cycle: What You Must Memorize
- Adapting the ADM to Different Situations
- How OG0-091 Tests This Domain
- Building a Focused Study Block for Domain 3
- Common Mistakes Candidates Make
- How Domain 3 Fits With the Rest of the Exam
- Frequently Asked Questions
- Domain 3 is worth 7.5% of OG0-091, roughly 3 of the 40 scored questions.
- You must know the ADM's phase sequence, the Requirements Management hub, and iteration concepts cold.
- Questions are simple multiple-choice, so exact TOGAF 9.2 terminology matters more than general PM knowledge.
- Domain 3 knowledge underpins Domain 5 (ADM Phases), which carries 22.5% of the exam.
What Domain 3 Actually Covers
Domain 3, "Introduction to the ADM," is the conceptual on-ramp to everything else you'll be tested on in the ADM Phases domain later in the exam. Where Domain 5 drills into the specific inputs, outputs, and steps of each phase, Domain 3 asks a narrower but foundational question: do you understand the Architecture Development Method as a whole - its purpose, its structure, and the principles that let it flex across different organizations and projects?
This domain sits at 7.5% of the OG0-091 blueprint, tied with Domain 1: Basic Concepts and Domain 2: Core Concepts. On a 40-question exam, that translates to approximately three questions - small in raw count, but conceptually load-bearing because nearly every later domain assumes you already understand the ADM cycle's shape.
Why This Domain Matters More Than Its Weight Suggests
It's tempting to deprioritize a 7.5% domain when you're staring down Domain 5's 22.5% weight. That would be a mistake. The ADM introduction material is the scaffolding every other domain hangs on. If you can't describe the ADM as an iterative cycle with a central Requirements Management activity, you'll struggle to answer questions in Domain 5, Domain 7 (Architecture Governance), and even Domain 10 (ADM Deliverables), because those questions assume fluency with the ADM's overall shape.
Think of Domain 3 as the map legend before you study the map itself. Skipping it and jumping straight to phase-by-phase memorization is a common reason candidates feel lost when questions blend concepts from multiple phases into a single scenario. For a broader view of how all eleven domains interact, see the complete guide to all 11 content areas.
Domain 3: Introduction to the ADM
Candidates must understand the ADM at a structural level before drilling into individual phases.
- The ADM as an iterative, cyclical method - not a rigid, linear waterfall process
- The role of the Requirements Management phase as the central hub connecting all other phases
- Why the ADM produces a "specific architecture" tailored to organizational needs
- The relationship between the ADM and the TOGAF Architecture Content Framework
- How the ADM can be adapted, scoped, and iterated for different engagement types
The ADM Cycle: What You Must Memorize
At its core, Domain 3 wants you to know that the ADM is presented as a circular diagram with a Preliminary Phase feeding into Phase A (Architecture Vision), which flows through Phases B, C, and D (Business, Information Systems, and Technology Architectures), into Phase E (Opportunities and Solutions), Phase F (Migration Planning), Phase G (Implementation Governance), and Phase H (Architecture Change Management) - all orbiting a central Requirements Management activity.
You don't need to memorize every deliverable at this stage (that's Domain 10 territory), but you absolutely need to know:
- The order of the phases and that the cycle is continuous, not a one-time project.
- Requirements Management sits at the center of the cycle, meaning requirements are identified, stored, and fed into every other phase throughout the engagement - not just gathered once at the start.
- The Preliminary Phase establishes the architecture capability and principles before any specific architecture work begins.
- Phase A kicks off the actual project by establishing scope, constraints, and stakeholder expectations.
- The cycle is repeatable - organizations move through multiple ADM cycles over time, and each cycle can itself be broken into iterations.
Key Takeaway
If a question describes requirements being captured once and never revisited, that answer is wrong by TOGAF's own definition. Requirements Management is continuous across the entire ADM cycle.
Adapting the ADM to Different Situations
A recurring theme in Domain 3 material is that the ADM is not a fixed, one-size-fits-all checklist. TOGAF 9.2 explicitly frames the ADM as a generic method that architects must tailor. Expect exam questions that test whether you understand the various ways the ADM can be adapted:
- Iteration: A single ADM cycle can be executed multiple times at increasing levels of detail rather than attempting to complete every phase exhaustively in one pass.
- Different styles of architecture engagement: Baseline-first vs. target-first approaches, or starting from existing capability assessments rather than a blank slate.
- Scoping decisions: Breadth (which parts of the enterprise), depth (level of detail), time period, and architecture domains (business, data, application, technology) can all be adjusted based on the engagement's purpose.
- Integration with other frameworks: The ADM can coexist with other process frameworks (project management methods, other architecture frameworks) rather than replacing them outright.
This flexibility is a favorite exam theme because it's easy to test with a distractor answer that describes the ADM as rigid or mandatory in sequence. If you see an answer choice implying phases must always be completed strictly in order with no skipping or looping back, be suspicious - TOGAF's own guidance supports iteration and adaptation.
How OG0-091 Tests This Domain
The overall exam format applies here just as it does everywhere else: 40 simple multiple-choice questions delivered in 60 minutes at a Pearson VUE test center or via OnVUE remote proctoring, closed-book, with a passing score of 60% (24 out of 40 correct). Domain 3 questions typically look like straightforward recall or single-concept application items rather than complex multi-part scenarios - that heavier scenario style is more common in Domain 5 and Domain 6.
Expect phrasing such as:
- "Which of the following best describes the role of Requirements Management within the ADM?"
- "What is the purpose of the Preliminary Phase in relation to the ADM cycle?"
- "Which statement about the ADM's structure is correct?"
Because these are single-answer, definitional questions drawn directly from the TOGAF 9 Standard, Version 9.2, the fastest path to reliable points is precise reading of the standard's own language rather than outside architecture experience. If your background is in enterprise architecture practice but not specifically TOGAF terminology, don't assume prior job experience will carry you through this domain - the exam rewards exact TOGAF phrasing.
Key Takeaway
Domain 3 questions reward memorized definitions more than judgment calls. Read the relevant chapters of the TOGAF 9.2 standard directly rather than relying solely on paraphrased study notes.
Building a Focused Study Block for Domain 3
Because Domain 3 is foundational, it deserves an early slot in your overall preparation schedule - before you tackle the dense phase-by-phase content in Domain 5. A short, focused block works better than spreading this material thin across your whole prep window.
Build the ADM Mental Map
- Sketch the ADM cycle diagram from memory: Preliminary through Phase H, with Requirements Management at the center
- Write one sentence describing the purpose of each phase at a high level
- Read the TOGAF 9.2 chapter introducing the ADM before reading individual phase chapters
Reinforce Adaptability Concepts
- Review the scoping dimensions (breadth, depth, time, architecture domains)
- Practice distinguishing "iteration" from "starting over"
- Attempt practice questions and note any Domain 3 items you miss for targeted review
This is also a good point to revisit your broader plan. If you haven't mapped out how much time to give each of the eleven domains, the OG0-091 Study Guide 2026 walks through a first-attempt-focused approach, and the exam domains guide breaks down how much attention each content area deserves relative to its weight.
Common Mistakes Candidates Make
- Treating the ADM as strictly linear. Candidates who picture the ADM as Phase A → B → C → D in a straight line without loops or iteration miss questions about adaptability.
- Confusing Requirements Management with a single project phase. It's a continuous, central activity - not a step you complete once and move past.
- Skipping the Preliminary Phase's purpose. Candidates sometimes conflate it with Phase A; the Preliminary Phase is about establishing capability and principles, while Phase A launches a specific architecture effort.
- Ignoring scoping concepts. Breadth, depth, time period, and architecture domain scoping show up more often than candidates expect for a domain this small.
- Studying phases before understanding the cycle. Jumping into Domain 5 detail without first internalizing the ADM's overall shape makes memorization harder, not easier.
If you're unsure how difficult this domain feels relative to others on the exam, the OG0-091 difficulty guide discusses where candidates typically lose points and how the ADM-related domains compare to more definitional ones like Domain 1 and Domain 2.
How Domain 3 Fits With the Rest of the Exam
Seeing Domain 3's weight next to the other ten domains helps calibrate how much time to invest relative to everything else on the blueprint.
| Domain | Weight | Relationship to Domain 3 |
|---|---|---|
| Domain 1: Basic Concepts | 7.5% | Provides vocabulary Domain 3 relies on (architecture, enterprise, stakeholder terms) |
| Domain 2: Core Concepts | 7.5% | Introduces the framework structure that houses the ADM |
| Domain 3: Introduction to the ADM | 7.5% | The subject of this guide - the ADM cycle and its adaptability |
| Domain 4: The Enterprise Continuum and Tools | 10% | Builds on ADM outputs as they move into the continuum |
| Domain 5: ADM Phases | 22.5% | The largest domain; expands each phase Domain 3 introduces at a high level |
| Domain 6: ADM Guidelines and Techniques | 15% | Details the techniques used to adapt the ADM, echoing Domain 3's flexibility theme |
Notice how Domain 3's concepts - iteration, scoping, the central role of requirements - reappear as building blocks in Domain 5 and Domain 6, which together account for well over a third of the exam's total questions. Mastering Domain 3 early genuinely pays dividends later.
Frequently Asked Questions
Domain 3 is weighted at 7.5% of the exam, which works out to roughly three of the 40 scored multiple-choice questions.
No. Domain 3 covers the ADM at a conceptual level - its cyclical structure, adaptability, and the role of Requirements Management. Domain 5 goes deep into the objectives, steps, and outputs of each individual phase and carries a much larger 22.5% weight.
No prior experience or prerequisites are required for OG0-091. Domain 3 questions are drawn directly from the TOGAF 9 Standard, Version 9.2, so studying the standard's own language is more valuable than general job experience.
Treating the ADM as a strictly linear, one-pass process. TOGAF presents the ADM as iterative and adaptable, with Requirements Management continuously feeding all phases rather than occurring only once at the start.
Early. Because Domain 3 establishes the ADM's overall shape, understanding it before studying Domain 5 and Domain 6 in detail makes those larger, higher-weighted domains easier to absorb. See the OG0-091 Study Guide 2026 for a full sequencing approach.
Domain 3 may only carry 7.5% of the OG0-091 blueprint, but it's the conceptual key that unlocks nearly a third of the exam's remaining content once you reach ADM Phases and ADM Guidelines and Techniques. Build a solid mental model of the cycle now, and the rest of your preparation - including practice runs on our OG0-091 practice test platform - will move noticeably faster.