ENTERPRISEThe system is live. Training is complete. Then pressure rises, and people return to the spreadsheet that got them through yesterday.
Look inside the kit ↗Follow the changeThe team has a signed procedure, training attendance records and a system that works. Those tell you what was delivered.
Now follow one task into the receiving organization.
Watch someone complete the task. Can they use the new process, or do they still need the old spreadsheet to get through it?
This is where adoption becomes visible: in what people actually do.
Perhaps the new way is being used. Does it reduce errors, improve the service or make the work easier? If it adds effort, is the benefit worth it?
Return to the reason for the change. Compare what you expected with what is happening.
You don’t need to complete these in order. Start with what you know. Use the gaps to decide who to involve next.
Why change, why now, and what happens if we do nothing?
Whose work changes, and what will they need?
Who has the authority to lead and back the change?
How will people understand and influence the change?
Can people actually do the new work?
Who keeps the new way working after the project leaves?
I’ll walk you through the six aspects, with real cases, worked examples and templates you can use with your team.
