Running a Rollout That Sticks
Most technology failures are adoption failures. This is about the twelve weeks after go-live: who champions it, what you measure, and how to tell early that it is not landing.
Runs most often inHealthcare and life sciencesPublic sectorFinancial services and bankingEducation
What participants can do afterwards
- Plan a rollout around the people who have to change how they work
- Identify and support the group that will decide whether it sticks
- Measure adoption rather than deployment
- Recognise a failing rollout in week three instead of month six
- Turn each rollout into a better next one
Modules
5 modules, 8 facilitated hours.
1.Who has to change
2 hrsMapping the rollout onto the people whose work actually changes.
- Map a rollout onto the people it affects
2.Champions and blockers
2 hrsFinding the group that decides adoption, and what they need.
- Identify and equip the group that decides adoption
3.Measuring adoption
1.5 hrsMetrics that show use rather than deployment.
- Measure adoption rather than deployment
4.Reading the early signals
1.5 hrsSpotting a failing rollout while it can still be fixed.
- Diagnose a struggling rollout early
5.The rollout retrospective
1 hrsClosing the loop: what the last rollout taught, captured while it can still shape the next one.
- Run a retrospective that improves the next rollout
How it is delivered
A facilitator runs the course live, in person or live online or blended. Attendance is taken per session, participants submit work against the modules above, and a facilitator grades it. Those records stay with the organisation and can be exported.
