All courses
Manager7 hrsIn person / Live online / Blended

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.

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

Modules

4 modules, 7 facilitated hours.

  1. 1.Who has to change

    2 hrs

    Mapping the rollout onto the people whose work actually changes.

    • Map a rollout onto the people it affects
  2. 2.Champions and blockers

    2 hrs

    Finding the group that decides adoption, and what they need.

    • Identify and equip the group that decides adoption
  3. 3.Measuring adoption

    1.5 hrs

    Metrics that show use rather than deployment.

    • Measure adoption rather than deployment
  4. 4.Reading the early signals

    1.5 hrs

    Spotting a failing rollout while it can still be fixed.

    • Diagnose a struggling rollout early

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.