Overview
Architecture Change Management is Phase H of the ADM. Once an architecture has been implemented, the enterprise keeps changing: new business needs, new technology, lessons learned and compliance findings all create pressure on the architecture. Phase H makes sure the architecture continues to deliver its intended value and that changes are handled in a governed way.
The area has three Understanding-level outcomes: the inputs that trigger change management, the activities that make it effective, and the outputs needed to proceed. Activities include establishing the value realization process, deploying monitoring tools, managing risks, analysing changes, developing change requirements to meet performance targets, managing the governance process and activating the process to implement change. A central skill is classifying change. A simplification change can usually be handled through change management, an incremental change may be handled by change management or partial re-architecting, and a re-architecting change needs a new ADM cycle through a new Request for Architecture Work.
How it's tested
A typical stem describes an architecture already in operation and an event that may affect it. You decide how significant the change is and how to respond. Best answers classify the change, assess impact and value, involve the Architecture Board and produce the right output, from an architecture update to a new Request for Architecture Work.
-
Change classification
You decide whether a change is a simplification, incremental or re-architecting change, which determines whether a new ADM cycle is needed.
-
Value realization
Measured benefits fall short of the KPIs set earlier. Strong options analyse why, develop change requirements to meet targets and govern the response.
-
Proportionate response
Options range from doing nothing to restarting the ADM. The best answer matches the scale of the response to the scale of the change.
Two years after a retail bank completed its digital channels architecture, a new open banking regulation requires external access to account data. A routine document update is too small, and redoing the entire enterprise architecture is excessive. Because the change affects several domains and the target state, the best option classifies it as re-architecting for the affected scope and issues a new Request for Architecture Work through governance.
Learning outcomes 3
Official learning outcomes from the The Open Group outline, in outline order.
6.1 Understand the inputs that trigger architecture change managementBloom level 2. What starts Phase H activity.
- What it means
- Phase H inputs include change requests arising from technology changes, business changes and lessons learned, together with compliance assessments, the Architecture Contract, the Implementation Governance Model, the architecture deliverables and the Architecture Repository.
- What to understand
- Triggers can be external, such as regulation, competition or new technology, or internal, such as poor performance against KPIs, compliance findings or new strategy. Monitoring is meant to detect these early so the enterprise responds deliberately rather than reacting to crises.
- How it shows up
- Scenarios describe an event and ask whether it should enter Phase H; most significant business, technology or compliance changes should.
- Common confusion
- Thinking Phase H only responds to technology changes.
6.2 Understand the activities needed for effective architecture change managementBloom level 2. Phase H steps and change classification.
- What it means
- Phase H establishes a value realization process, deploys monitoring tools, manages risks, provides analysis for change management, develops change requirements to meet performance targets, manages the governance process and activates the process to implement change.
- What to understand
- Changes are classified: simplification changes are usually handled by change management; incremental changes may be handled by change management or partial re-architecting; re-architecting changes require a new ADM cycle. The Architecture Board reviews significant changes and decides the response, recording decisions in the Governance Log.
- How it shows up
- The best options classify the change before acting and involve governance for anything beyond simplification.
- Common confusion
- Assuming every change needs a new ADM cycle, or that none do.
6.3 Understand the outputs needed to proceed from Phase HBloom level 2. What Phase H produces.
- What it means
- Outputs include architecture updates for maintenance changes, changes to the architecture framework and principles, a new Request for Architecture Work to start another cycle, and updates to the Statement of Architecture Work, Architecture Contract and Compliance Assessments.
- What to understand
- The output depends on the classification. Small changes lead to updated architecture content. Significant changes lead to a new Request for Architecture Work. Lessons learned may change the framework or principles themselves, improving the Architecture Capability.
- How it shows up
- Questions ask what Phase H should produce for a given change; match the output to the change class.
- Common confusion
- Producing a new Statement of Architecture Work directly instead of a new Request for Architecture Work.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Simplification change
Change that reduces investment or simplifies, often handled through change management.
- Remember
- Usually no new ADM cycle.
- Tested as
- Classification questions.
- Trap
- Starting a full cycle for it.
-
Incremental change
Change that adds value to existing investment.
- Remember
- May be handled by change management or partial re-architecting.
- Tested as
- Middle-ground scenarios.
- Trap
- Treating it as purely routine.
-
Re-architecting change
Change that requires restructuring the architecture.
- Remember
- Needs a new ADM cycle via a new Request for Architecture Work.
- Tested as
- Major business or regulatory shifts.
- Trap
- Handling it as a document update.
-
Value realization process
Process to check that expected business value is achieved.
- Remember
- Uses KPIs from Phase A.
- Tested as
- Benefits shortfall scenarios.
- Trap
- Ending measurement at go-live.
-
Monitoring tools
Means of tracking technology and business change and performance.
- Remember
- Deployed in Phase H.
- Tested as
- Early detection of triggers.
- Trap
- Relying on ad hoc reports.
-
Change request
Formal request to change the architecture, from technology, business or lessons learned.
- Remember
- Key Phase H input.
- Tested as
- Routing changes.
- Trap
- Making changes without one.
-
New Request for Architecture Work
Output that starts a new ADM cycle.
- Remember
- Used for re-architecting change.
- Tested as
- Output questions.
- Trap
- Confusing with Statement of Architecture Work.
-
Governance Log
Record of governance decisions and compliance history.
- Remember
- Phase H decisions are recorded.
- Tested as
- Traceability options.
- Trap
- Keeping decisions in email only.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Simplification vs. incremental vs. re-architecting change
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Simplification | Reduces or simplifies; often driven by cost reduction | Handled by change management | Over-governing it |
| Incremental | Adds value to existing investment | Change management or partial re-architecting | Ignoring architectural impact |
| Re-architecting | Requires restructuring of the architecture | New ADM cycle | Handling it as a minor update |
Architecture update vs. new Request for Architecture Work
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Architecture update | Maintenance change to existing architecture content | Stays within the current cycle's scope | Using it for major shifts |
| New Request for Architecture Work | Formal trigger for a new ADM cycle | Starts with Phase A for the new scope | Skipping sponsor involvement |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Quiet update
- What candidates pick
- The architecture team updates the target models to reflect the new regulation.
- Why it looks right
- It keeps documents current quickly.
- Why it's wrong
- A change affecting several domains and the target needs classification, governance and possibly a new ADM cycle.
Clue to watch for New regulation, merger or strategy affecting multiple areas.
-
Full restart for everything
- What candidates pick
- Issue a new Request for Architecture Work for a minor platform simplification.
- Why it looks right
- It seems rigorous.
- Why it's wrong
- Simplification changes are normally handled through change management without a new cycle.
Clue to watch for Small scope, cost reduction, no change to target capabilities.
-
Go-live is the end
- What candidates pick
- Close the architecture once systems are deployed.
- Why it looks right
- The project is finished.
- Why it's wrong
- Phase H continues to monitor value, risk and change so the architecture stays relevant.
Clue to watch for Benefits are below KPIs after deployment.
-
Technology-only triggers
- What candidates pick
- Monitor only new technology releases for change triggers.
- Why it looks right
- Technology changes fast.
- Why it's wrong
- Business changes and lessons learned are equally valid triggers.
Clue to watch for A business reorganization or new market is mentioned.
-
Skip the Board
- What candidates pick
- Let the operations manager decide whether the change is significant.
- Why it looks right
- Operations knows the systems.
- Why it's wrong
- Significant architecture changes are reviewed through the Architecture Board and recorded.
Clue to watch for The change affects standards or multiple projects.
Answer framework
Use these steps when a post-implementation event appears in a scenario.
- Identify the trigger: business change, technology change, lessons learned, compliance finding or a value shortfall against agreed KPIs.
- Assess the scope and impact of the change on the current architecture, its target state and other architectures in the landscape.
- Classify the change as simplification, incremental or re-architecting, because the class decides the proportionate response; incremental changes can usually be handled within existing governance.
- Route significant changes through the Architecture Board and record the decision, rather than letting a single team decide.
- Choose the matching output: an architecture update, a change to framework or principles, or a new Request for Architecture Work for a new cycle, which starts the ADM cycle again from Phase A.
Practice question
Want more like this? The TOGAF Practitioner practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Phase H is compact, so aim to master it rather than skim it. Start by reading its objectives, inputs, steps and outputs, and write the steps as a short list you could recite.
The most tested concept is change classification. Make a three-row table for simplification, incremental and re-architecting change with an example of each from your own experience, such as decommissioning a duplicate system, adding a feature to an existing platform, or responding to a merger. Next to each, write the expected response and output.
Then link Phase H backward and forward. Backward, connect it to the KPIs and value propositions from Phase A and the compliance assessments and change requests from Phase G. Forward, connect it to Requirements Management and to the new Request for Architecture Work that starts another cycle.
Finally, practise scenarios set after implementation. Before reading options, decide which class the change belongs to and who should decide. With only three outcomes here, a few focused hours of practice should make these scenarios reliable points, and the same reasoning helps in implementation and requirements questions.
FAQ
What weight does Architecture Change Management have on OGEA-102?
No weight is published for Architecture Change Management. It is one of the eight syllabus areas the 8 scenarios draw on, and Phase H ideas often appear in scenarios set after implementation.
When is a new ADM cycle needed?
For re-architecting changes that require restructuring the architecture, and sometimes for incremental changes with wide impact. Simplification changes usually are not.
What does Phase H monitor?
Business and technology changes, performance against agreed KPIs, value realization, risks and compliance, so that the architecture stays fit for purpose.
Who decides how a change is handled?
Significant changes are reviewed through Architecture Governance, normally the Architecture Board, and decisions are recorded in the Governance Log.
Can Phase H change the TOGAF framework itself?
Yes. Lessons learned can lead to changes to the organization's tailored architecture framework and principles, improving the Architecture Capability.
How is Phase H related to Requirements Management?
Changed requirements arising in Phase H are handled through Requirements Management, which assesses their impact and passes them to the right phase or cycle.
Other Enterprise Architecture & IT Governance certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
You have studied Phase H triggers, activities, change classification and outputs. Check whether you can choose a proportionate response under exam timing.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the TOGAF Practitioner AI tutor Get any concept explained your way