Change and adoption
Define adoption as a behaviour you can see.
Turn a broad adoption target into a small set of observable working behaviours, with clear evidence and practical support.
A hypothetical service business launches a new workflow tool. Training attendance is high and every account is active. Two weeks later, requests still arrive by email, managers keep a parallel spreadsheet and the new system holds only part of the story. The software is available, but the working practice has not changed. For the next launch, or while correcting the current one, define the behaviour that would show useful adoption in the real process. That gives the team something more meaningful to improve than logins or course completion.
Describe the work in observable terms
Choose the few behaviours that matter to the intended outcome. Write them as actions a person could observe in ordinary work: a request starts in the agreed channel, the owner updates its status at the handover, or a decision is recorded in the shared system before the next step begins.
Avoid a broad target such as ‘use the platform consistently’. It hides several decisions about who acts, when they act and what good completion looks like. Keep the first list short enough for a manager and team to use during a real working day.
Choose evidence that matches the behaviour
For each behaviour, identify evidence that is proportionate and available. A completed training module can show preparation, but not whether the new route works under normal pressure. A system record, a sampled handover or a short team review may provide better evidence of the practice itself.
Use measures carefully. A high number of updates may reflect duplicate entry rather than adoption. Pair system data with a small qualitative check so the team can explain why old routes or workarounds remain.
- What should a person do differently?
- At which point in the work should it happen?
- What evidence would show that it happened well?
- Who can remove a repeated obstacle?
Find the friction behind the old behaviour
When people return to email or a spreadsheet, do not assume they are resisting change. Check whether the new route is slower, lacks necessary information, creates duplicate entry or fails during a common exception. The workaround may be evidence about the design of the process, access or guidance.
Give repeated obstacles an owner and a review date. Tell the team which temporary route to use while an issue is being resolved, and what will allow that route to stop. This prevents an informal workaround becoming the permanent process.
Review adoption where the work happens
Use short reviews after people have completed real tasks, not only immediately after training. Ask for one recent example, compare it with the intended behaviour and decide whether the response is better support, a process change or clearer accountability.
Retire behaviours that no longer matter and add new ones only when the service or process changes. Adoption is not a single launch score; it is an agreed way of working that remains useful as conditions move.
Rethink's ongoing senior advice, scoped by agreement, can help teams connect technology change to practical working behaviours and follow-through.
