What we do/Change management sprints
Change management sprints
A change management sprint is a short, focused piece of work that gets the teams a change depends on to agree its purpose, who owns what and how work passes between them. It tests that agreement against real situations before anyone calls it done.
When it helps
- Ownership changes at each department boundary.
- Success means something different to each function.
- The initiative moves only when one person chases everything.
- A recurring problem crosses departmental boundaries.
- A new tool is sitting on top of an old operating pattern.
- People need practical ownership, not another transformation deck.
How to choose a provider
They work with the people who will run the change
Change designed by outsiders and handed over tends to be politely ignored. Ask how your own people are involved in designing it.
They look at handoffs, not just plans
Most change fails at the boundary between departments. The provider should map where work actually passes from one team to another.
Decision rights are made explicit
Ask how they establish who decides what. Without that, alignment lasts until the first disagreement.
They test the agreement
A plan everyone nods at is not alignment. Look for a provider who runs the agreement against real cases.
They plan for their own exit
Ask how the organisation keeps ownership once they leave. A good answer includes capability, not dependency.
What goes wrong most often
A new tool on an old way of working
The system changes and the habits around it do not.
One person carries the whole thing
The initiative only moves when a single individual chases every part of it.
Success means something different to each function
Each team reports progress against its own definition.
Another deck
The work ends in a document about change, with no change in who does what.
How INSO runs it
Bring the work into one visible map. Compare the competing priorities, establish decision rights and examine the critical handoffs. Test the agreement against real situations before calling it alignment.
- Length
- 3 days, 5 days, or shaped around your situation
- Delivery
- In person, Live online, Blended
- Where
- Worldwide
Questions people ask
How does this differ from the Alignment Session?
The workshop can settle a focused shared priority. The sprint allows deeper work on multiple functions, dependencies and practical operating agreements.
Do all participants attend every session?
We agree the core team and targeted contributions. The people who decide and deliver must participate at the relevant points.
Will you manage the initiative afterwards?
Ongoing coordination or embedded project support can be agreed separately.
Does this include everything?
It can bring several INSO formats together, but it is never an unlimited commitment. Specialists, deliverables, exclusions and decision points are agreed in scope.
Will you bring in outside specialists?
Where the change needs them, appropriate specialists can be included with clear roles, access and responsibilities.
How do you avoid dependency?
The people who will own the work participate in designing and testing it. Transfer of reasoning, tools and responsibility is part of the engagement.
Start a conversation