Study guide
2.3 Planned Change versus Emergent 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.3 Planned Change versus Emergent Change
Key Takeaways Explain This Topic AI
Planned change has a clear beginning and end point, is highly structured and is associated with a well-defined plan or list of tasks
Emergent change has a clear direction but the end point may be a little fuzzy, and it is less structured and evolves as it goes
Planned change is usually driven from the top, although it may consult widely at all levels for best results
Emergent change is supported from the top but more participative, leaving room for local line leaders to start their own initiatives
Typical planned changes include office relocations, system changes and legislative compliance; emergent changes include drives to improve service, cost, quality or culture
Last updated: September 2026
There are two ways that change happens in an organisation. Change is planned and delivered strategically, usually driven from the top. Or change emerges from somewhere — usually starting small, gaining support and momentum, and growing. CM3 asks you to distinguish them, and the exam tests the comparison line by line.
The full comparison
Planned change Emergent change
Typical examples Relocation of offices, system changes, compliance with new legislation A drive to improve customer service, or costs, or quality; changes to culture, attitude and capabilities
- Beginning and end Clear beginning and end point Clear direction, but the end point may be a little fuzzy
- Structure Highly structured Less structured, evolving as it goes
Planning Associated with a well-defined plan or list of tasks More experimental, step-by-step approach, testing what works and what does not
Direction of drive Usually driven from the top, although may consult widely and at all levels to get best results Supported from the top but more participative in nature; more room for local line leaders and others to start their own initiatives
Read the third row carefully. Planned change may consult widely and at all levels — consultation is not what distinguishes the two. Candidates often assume "planned means imposed" and get caught. What distinguishes them is where the initiative and the shaping come from, and how defined the destination is.
Recognising which one you have
Three diagnostic questions:
Can you describe the finished state precisely? "Every employee is in the new building by 1 March" is planned. "Customer service is noticeably better" is emergent.
Is there a task list, or a direction of travel? A well-defined plan or list of tasks points to planned change. An experimental, step-by-step approach that tests what works points to emergent change.
Where do new initiatives come from? If local line leaders are starting their own related initiatives and the centre is supporting rather than directing them, that is emergent change working as intended.
Why the distinction changes what you do
The two types demand different change management:
Planned change justifies detailed communication plans keyed to milestones, training scheduled close to a fixed go-live, and progress reporting against a task list. The change manager's risk is people arriving at a fixed date unprepared.
Emergent change demands feedback loops, visible sharing of what is working, and mechanisms to spread local successes. The change manager's risk is drift — activity without direction — and the antidote is a clear, repeatedly communicated direction of travel even when the destination is fuzzy.
A practical consequence: in emergent change, success stories are a delivery mechanism, not just publicity . When a team finds a better way of handling a customer complaint and you spread that story, you are literally doing the delivery. In planned change, the equivalent activity is readiness assurance.
Hybrids are normal
Most real initiatives contain both. A digital transformation typically has a planned core — the systems go live on a date — wrapped in an emergent shell, because how people end up working with the systems evolves over months and cannot be specified in advance. The change manager's job is to notice which part they are in and stop applying planned-change discipline to emergent-change problems.
That mismatch produces a recognisable failure pattern: a change team reports 100% of planned activities complete while the business reports nothing has really changed. Every planned output was delivered, and the emergent outcome — how people actually work — was never managed. This is exactly the outputs-versus-outcomes gap, seen from the delivery side.
Emergent change and the wider syllabus
Emergent change connects directly to several later topics. It sits naturally in Cynefin's complex domain, where an experimental, emergent approach is advised. It relies on co-design , because the people doing the work shape the solution. It is supported by the continuous change management cycle , whose feedback-driven loop is built for exactly this situation. And it depends more heavily on personal power sources than positional ones, because nobody is being ordered.
Sponsorship looks different in each type
The sponsor's job does not disappear in emergent change; it changes shape. In planned change the sponsor legitimises a defined destination, holds the deadline and confronts blockers. In emergent change the sponsor holds the direction rather than the destination, protects the space in which local initiatives can start, and resists the pressure to convert a genuinely emergent programme into a plan with dates so it can be reported on conventionally.
That pressure is real and it is where most emergent programmes fail. A steering group asked to oversee something with a fuzzy end point will, in good faith, ask for a plan. Producing one manufactures precision that does not exist, and the programme is then measured against invented milestones. The honest alternative is to report progress in the terms the change actually has — what has been tried, what worked, what spread, and what the direction of travel now looks like.
Measuring each type
The two types also need different evidence:
Planned change Emergent change
Primary question Are we on schedule and are people ready? Is the direction taking hold and spreading?
Typical measures Milestone completion, training coverage, readiness scores against a fixed go-live Adoption spread across teams, number of local initiatives started, qualitative accounts of what has changed
Failure signal A group arrives at go-live unprepared Activity continues but nothing observable changes
Applying planned-change measures to emergent change produces the most misleading report in change management: full completion of every scheduled activity alongside no observable difference in how anyone works.