Practice : Iterative Change Rollout
Purpose and Strategic Importance
Iterative Change Rollout is the practice of introducing significant organisational change in phases — starting with a contained scope, learning from real experience, and adapting before scaling. It applies the same incremental delivery logic that product teams use for software to the challenge of leading people and organisational change.
Big-bang change implementation is high-risk and low-learning. Leaders who roll out change iteratively create opportunities to surface problems early when they are cheap to fix, build confidence through demonstrated success, and adapt the change based on what they learn from the reality of implementation — not the theory of planning.
Description of the Practice
- Change is implemented in phases with defined scope, duration, and success criteria for each phase.
- Each phase produces learning that is explicitly reviewed before the next phase begins.
- Feedback from those experiencing the change is actively gathered and incorporated.
- Leaders remain visible and accessible during each phase to support adoption and address concerns.
- Scaling decisions are made on the evidence of what has been learned in earlier phases.
How to Practise It (Playbook)
1. Getting Started
- Identify a volunteer or willing group to be the first cohort for the change — early adopters who will provide honest feedback.
- Define what success looks like after the first phase: what would you need to observe to have confidence proceeding?
- After the first phase, conduct a structured review: what worked, what did not, what needs to change before scaling?
- Adapt the rollout plan based on what you learned — not just in formal documents but in actual practice.
2. Scaling and Maturing
- Build a phase gate process: formal checkpoints where scaling decisions are made based on evidence from the previous phase.
- Create feedback mechanisms for each phase: surveys, retrospectives, or observation.
- Document learning from each phase and share it with those implementing subsequent phases.
- Adjust the change itself, not just the rollout, if early phases reveal fundamental issues with the design.
3. Team Behaviours to Encourage
- Early adopters give honest feedback about what is and is not working — they are treated as partners, not test subjects.
- Leaders respond to phase feedback by adapting the change, not defending it.
- Teams in later phases trust the process more because they can see earlier phases were genuinely learned from.
- Rollout participants are given credit for their contribution to the change's success.
4. Watch Out For…
- Phase gates that exist on paper but are never actually used to stop or adjust the rollout.
- Leaders who collect feedback but do not visibly act on it — destroying credibility for the process.
- Selecting early phases that are too easy to produce meaningful learning about the hard parts.
- Treating iterative rollout as slower than big-bang when actually it is faster — failing early is much cheaper than failing at scale.
5. Signals of Success
- Each phase produces learning that visibly improves the next phase.
- Scaling decisions are evidenced by phase outcomes, not just continued according to plan.
- Adoption rates are higher in later phases than earlier ones, as the change has been refined.
- Teams describe the rollout as well-managed and respectful of their experience.
- The final implementation is meaningfully different from the original plan in ways that improve it.