Study guide
4.1 Delivery Strategy: Big Bang, Phased, Voluntary and Iterative
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
4.1 Delivery Strategy: Big Bang, Phased, Voluntary and Iterative
Key Takeaways Explain This Topic AI
Big bang means everybody goes live at the same time, with no chance to learn from mistakes
A phased approach rolls out across parts of the organisation over time, allowing learning between phases and staggered training
Voluntary adoption lets individuals or teams adopt at a time of their choosing, provided everyone transitions by a given date
Many small incremental or iterative releases are typical of agile delivery, where not all releases will even be noticed by users
- Real-world implementation strategies are often a hybrid of two or more of the basic approaches
- Last updated: September 2026
How change is delivered should be considered before designing the approach. The delivery strategy determines when training must land, how much support resource is needed at go-live, whether learning between groups is possible, and how communication is paced. CM3 examines four basic approaches, each with named examples and change management implications.
The four delivery strategies
Type What it is Examples Implications for change management
Big bang Everybody goes live all at the same time New legislation such as a sales tax — what was illegal at the end of one month becomes mandatory the next; everyone moving into new premises on Monday No chance to learn from mistakes. Careful consideration of the timing of training and whether some stakeholders face a large gap between learning and doing. Could require a lot of support resource, both technical and change, in the early days after go-live
Phased A planned roll-out across various parts of the organisation over a period of time "We will roll this out across the three regional centres — one centre every two months"; useful for new software, machinery, processes Allows learning between phases. Allows success stories from early phases to be communicated across the organisation. Allows training to be staggered, so training can take place closer to implementation
Voluntary adoption Individuals or teams adopt the new thing at a time of their choosing, as long as everyone transitions by a given date Adoption of a new desktop operating environment standard; new working-from-home arrangements Track adoption rates and consider publishing them. Watch for issues that derail momentum, such as demand outstripping the ability to deliver the transition. Look for success stories among early adopters. Consider strategies for people waiting until the last moment
Many small incremental / iterative releases In highly agile projects, especially software, small changes released at the end of each timebox or sprint, for example every two weeks Major upgrades to an existing system delivered by a Scrum team; a move from paper-based to digital delivered by a Scrum team A lot of change management focuses on the end goals. Lengthy training courses over a day or more are unlikely to be practical or necessary. Not all releases will even be noticed by users. The change manager must become adept at spotting releases needing more change management
- What each strategy demands of you
- Big bang
The defining constraint is that there is no second chance . Because nobody goes first, nobody has learned anything before the whole organisation is live. Two practical consequences follow.
First, the learning-to-doing gap becomes the critical risk . If you train 800 people over six weeks and everyone goes live on the same Monday, the first group trained has a six-week gap before using anything, and by then most of what they learned has decayed. Bridging that gap — refresher material, quick-reference guides, practice environments kept open — is a named change management concern.
Second, support resource peaks sharply . A lot of support resource, both technical and change, is likely to be needed in the early days after go-live. Under-resourcing this window is one of the most reliable ways to convert a workable change into a failed one, because every unresolved early problem becomes a story that travels.
Phased
Phasing buys you the thing big bang cannot provide: learning between phases . That advantage is only realised if you actually build a mechanism to capture and apply it — a structured lessons review after each phase, feeding into the next.
It also produces success stories from early phases that can be communicated across the whole organisation, which is powerful because it is peer evidence rather than change-team assertion. And it allows training to be staggered so it happens closer to implementation , which directly addresses big bang's decay problem.
Voluntary adoption
Voluntary adoption is the only strategy where you are managing a rate rather than a date. The change management work shifts to tracking adoption rates and considering publishing them — visible adoption numbers create their own social pressure.
Two risks are named. Demand can outstrip the ability to deliver the transition , so an enthusiastic early surge overwhelms the support capacity and creates a bad experience precisely among your most willing adopters. And late holdouts need a deliberate strategy, because the people who wait until the final week are typically those with the most concerns and they will all need support simultaneously.
CM3 also notes that voluntary adoption invites consideration of a diffusion curve when thinking about adoption rates over time.
Incremental and iterative releases
Agile delivery inverts the usual change management pattern. Because releases are frequent and small, lengthy training courses are unlikely to be practical or even necessary , and not all releases will even be noticed by users .
The skill becomes triage : spotting which releases need change management and which do not. CM3 gives the sharp warning that five minutes' work for a software developer could lead to a major process rewrite — technical effort is a terrible proxy for change impact. This is also where minimum viable change practice applies, keeping the change intervention proportionate to each release.
Hybrids
Often the real-world implementation strategy is a hybrid of two or more of the basic approaches . A common pattern is a phased roll-out where each phase is itself a big bang for that site, or a voluntary adoption period followed by a mandatory cut-over date. Identify which characteristics apply to which part rather than forcing a single label onto the whole programme.