Problem
01
Our last transformation stalled after the kick-off.
02
Teams are not adopting the new ways of working.
03
We cannot tell whether the change is working.
Outcomes
- Adoption, not just go-live
- A measurable shift in how work is done
- A plan the organisation believes in
Scope
In scope
- Change design
- Sequencing and planning
- Adoption support and measurement
Not included
- The underlying software build, which sits under engineering
- Ongoing run, which sits under managed services
Approach
Discovery
We agree the decision you are making, the constraints and how success will be judged.
Delivery planning
We shape options, sequence the work and set out costs and risks.
Build and test
We produce the artefacts and pressure-test them with the people who will own them.
Operational readiness, hypercare and closure
We hand over, support the first weeks of use, and confirm the outcome before we close.
Deliverables
Change planAdoption measuresReadiness assessment
Technologies
Change management frameworksAdoption measurement
Controls
Each change has a named owner and a measure of adoption. Live services are protected during the change. Affected teams are involved in testing the change. Progress and risks are reported in writing.
Frequently Asked Questions
How is this different from a strategy deck?
A deck ends at the idea. This ends when teams are working the new way and the measures confirm it.
Who owns the change?
Each part has a named owner, and we work alongside them rather than around them.
Ready to scope this?
Tell us the change you are trying to make and we will help it land.