Study guide
2.4 Systems Thinking in Change
APMG Change Management Foundation Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The v3 Foundation Exam and the Organisational Context
1.1 Exam Structure, the Five Syllabus Areas and the Certification Path 1.2 Scene Setting: External and Internal Factors Shaping Change 1.3 Change Management, Benefits and Dis-benefits
2 Chapter 2: Understanding the Change Context
2.1 Kelman's Three Levels of Adoption 2.2 VUCA and the Cynefin Framework 2.3 Planned Change versus Emergent Change 2.4 Systems Thinking in Change 2.5 Organisational Culture and Its Three Levels
3 Chapter 3: Diagnosing and Structuring the Change Approach
3.1 Lewin's Force Field Analysis 3.2 Co-Design 3.3 The ADKAR Model 3.4 Evolving the n-Step Process and Kotter's Eight Accelerators
4 Chapter 4: Delivery Strategy, Agile Practices and the Change Strategy
4.1 Delivery Strategy: Big Bang, Phased, Voluntary and Iterative 4.2 Agile Practices and Agile Change Practices 4.3 The Continuous Change Management Cycle 4.4 The Change Strategy
5 Chapter 5: People and Change — Individual Difference and Response
5.1 Differences in People and Personality Preferences 5.2 Neuroscience and Change: SCARF, Mindset and Insight 5.3 The Change Curve 5.4 Bridges' Transition Model
6 Chapter 6: Motivation, Resilience and Learning
6.1 Rewards, Punishment and Pink's Three Motivators 6.2 Positive Psychology, Resilience and Appreciative Inquiry 6.3 The Beckhard-Harris Change Formula and Schein's Two Anxieties 6.4 Competence, Learning and the Learning Dip 6.5 Learning Preferences: Kolb, Honey and Mumford
7 Chapter 7: Key Roles in Change Leadership
7.1 Key Roles in the Change Process 7.2 The Role of the Change Sponsor 7.3 The Change Agent's Role and Personal Influence 7.4 The Role of Local Leadership in Change
8 Chapter 8: Psychological Safety, Leadership and Culture
8.1 Psychological Climate and Psychological Safety 8.2 Carolyn Taylor: How Leadership Shapes Culture 8.3 Leadership Styles and Organisational Climate
9 Chapter 9: Teams and Change
9.1 Team Structures and Change Agent Networks 9.2 Tuckman's Stages of Team Development 9.3 Lencioni: Assessing and Growing Team Effectiveness 9.4 Harvesting the Value of Team Diversity
10 Chapter 10: Stakeholder Identification, Analysis and Engagement
10.1 Stakeholder Definition and Identification 10.2 Stakeholder Analysis, Segmentation and Empathy Mapping 10.3 Stakeholder Mapping and Sources of Power 10.4 Barriers to Engagement 10.5 Planning Stakeholder Engagement
11 Chapter 11: Communication Theory, Messaging and Emotional Connection
11.1 Communication Theory and the Communication Process 11.2 Barriers to Communication and Cognitive Biases 11.3 Messaging: Setting Context and the Tell, Sell, Include Approach 11.4 Appealing to Hearts and Minds
12 Chapter 12: Communication Channels and Planning
12.1 Ways of Communicating and VARK Language Style Preferences 12.2 Communication Channels: One-Way, Two-Way, Lean and Rich 12.3 Communications Planning
13 Chapter 13: Assessing Change Impact and Severity
13.1 Change Management as Risk Management and the Two-Step Assessment 13.2 Step 1: Categorising Impacts and Identifying Impact Areas 13.3 Step 1 Continued: Gap Analysis, Impact Profiles and Monitoring 13.4 Step 2: Change Impact Severity
14 Chapter 14: Resistance to Change
14.1 Causes of Resistance and Oreg's Four Neural Factors 14.2 Common Reasons for Resistance and How to Deal With Them 14.3 Building a Strategy to Manage Resistance
15 Chapter 15: Change Analytics and Exam Readiness
15.1 Measurement Types and the Change Delivery Scorecard 15.2 Building a Change Analytics Strategy 15.3 Exam Technique and Final Revision
2.4 Systems Thinking in Change
Key Takeaways Explain This Topic AI
Systems thinking treats the organisation as interacting elements rather than independent parts
It helps identify both intended and unintended consequences of a change
Changing one element of a system produces effects in connected elements that were never targeted
Systems thinking underpins impact assessment, where unintended change is a formal impact category
- Feedback loops and delayed effects mean the full consequences of a change often appear well after go-live
- Last updated: September 2026
Systems thinking is the discipline of understanding the smaller interacting elements of a change rather than treating each part in isolation. CM3 places it in the context-setting section for a specific reason: it is how you identify intended and unintended consequences before they arrive.
The core idea
An organisation is not a collection of independent boxes on a chart. It is a set of elements — teams, processes, systems, incentives, relationships, informal workarounds — that interact. Change one element and the connected elements respond, whether or not you intended them to.
A worked example makes this concrete. A finance team introduces an automated three-day payment approval to reduce processing cost. The intended consequence is achieved. The unintended consequences ripple outward:
Suppliers who previously chased the finance team by phone now have no human contact, so complaints route to account managers instead
- Account managers, whose targets do not include supplier queries, deprioritise them
- Two suppliers, unable to get answers, tighten credit terms
- Procurement's negotiating position weakens at the next renewal
Nothing in that chain was in the project scope. Every link is a real interaction between elements of the system, and a systems view would have exposed at least the first two before go-live.
Concepts that make systems thinking usable
Interconnection. Ask, for each part of the change, "what else touches this?" Not just which systems, but which people, incentives, informal arrangements and reporting lines.
Unintended consequences. These are not rare surprises; they are the normal output of intervening in a system you do not fully understand. CM3 treats them as an expected category, which is why unintended or unplanned change is one of the three formal categories in change impact assessment.
Feedback loops. Some effects reinforce themselves. If a change makes a team's work harder and their performance dips, and the dip attracts scrutiny that adds reporting burden, the loop amplifies. Recognising a reinforcing loop early is worth more than any amount of after-the-fact analysis.
Delay. Consequences frequently arrive long after the intervention. Because change teams typically disband at go-live, the delayed effects land on people who have no context for them and no mandate to fix them — which is one of the most common sources of the poor history of change that poisons the next initiative.
Putting systems thinking to work
In practice, three activities carry most of the value:
Map beyond the obvious boundary. Take the change's stated scope and deliberately identify three groups just outside it who interact with the affected process. In the payments example: suppliers, account managers, procurement.
Ask what currently absorbs the strain. Every process has informal shock absorbers — the experienced administrator who fixes exceptions, the phone call that unblocks things. Changes routinely remove these without noticing they existed, because they appear on no process map.
Ask what behaviour the change rewards. If a new metric makes one team's numbers depend on another team's speed, you have created an interaction whether or not you designed one.
Where it connects in the syllabus
Systems thinking is not an isolated model; it underpins several later topics:
Connects to How
Change impact assessment Unintended/unplanned change is one of the three impact categories, and identifying impact areas is a systems exercise
Resistance "Ripple effects — change interferes with the activities of other areas" is a named cause of resistance, addressed by enlarging the circle of stakeholders
Stakeholder identification "Who will be affected by this change?" is broader than "who is in scope", and systems thinking is how you answer it honestly
- Cynefin Interconnected elements with unknown relationships is close to the definition of the complex domain
- The discipline it demands
Systems thinking is uncomfortable because it expands scope. Every ripple you identify is potentially more work, and there is real pressure to keep the boundary tight so the change stays deliverable. The professional answer is not to expand the change to cover every ripple, but to identify it, assess its severity, and make a conscious decision — accept it, mitigate it, or hand it to someone who owns it. An unintended consequence that has been named, assessed and consciously accepted is a managed risk. The same consequence unnoticed is a failure waiting to be discovered by someone else.
Drawing the map
Systems thinking becomes practical when it produces an actual picture. A workable method, usable in a single facilitated session:
Put the changed element in the centre — the process, system or role that the change directly alters.
Draw everything that feeds it — inputs, upstream teams, source systems, the people who supply information to it.
Draw everything it feeds — outputs, downstream teams, reports, decisions that depend on it.
Add the informal connections — the phone call that unblocks exceptions, the person everyone asks, the spreadsheet nobody owns. These almost never appear on process documentation and are frequently what the change removes.
Mark where effects will be delayed — month-end, quarter-end, annual cycles, and anything that only surfaces under peak load.
Step four produces the most value per minute spent, and it requires people who do the work rather than people who designed it. Step five matters because delayed effects arrive after the change team has moved on, and flagging them in advance is the difference between a known consequence and an unexplained problem attributed to the change months later.
The output is not a deliverable for governance; it is an input to the stakeholder list and the impact assessment.