Guide: An Adoption Ownership Check If the Champion Exits
A simple adoption-ownership check for seeing whether a new tool or way of working can continue without one visible champion carrying it.
What Happens If the Champion Leaves?
A simple adoption-ownership check for seeing whether a new tool or way of working can continue without a visible champion carrying it.
A champion can start momentum but the organisation still has to inherit the work.
What this Guide helps with
Use it when usage, confidence or participation seems closely tied to one person who reminds, explains, organises, chases or rescues adoption.
Keep it small
Pick one tool, practice or changed behaviour, not to be used to assess the whole transformation. Follow one key thing people are expected to keep using.
The Pattern behind this Guide
Champion Vacuum: this public Pattern post contains the quiz that leads into this Guide.
The check
Choose something specific: using an AI assistant, entering deals in CRM, following a new workflow, using a portal or completing a new approval step.
Record the reminders, demonstrations, office hours, fixes, escalations, encouragement and informal support they provide.
Write down the role expected to own adoption after launch. Avoid names such as “the business” unless a real role sits behind them.
Ask what happens if the champion is unavailable for four weeks. Which routines continue, which questions return and which usage drops?
Look for team routines, manager expectations, onboarding, support routes, metrics and local ownership that exist without the champion.
Choose one activity currently carried by the champion and place it with a named operational owner, routine or support channel.
Use this small log
| Adoption activity | Champion currently does | Normal owner | What happens if absent? |
|---|---|---|---|
| Weekly AI drop-in | Answers every question | Team capability lead | Questions wait or move to private chats |
| CRM usage follow-up | Chases missing updates | Sales manager | Data quality falls |
| Workflow exceptions | Explains how to route them | Operations owner | Old email process returns |
Where this commonly hides
Quick examples
| What you see | Question to ask |
|---|---|
| Usage falls during the champion’s holiday | Which activity or decision was never transferred into the SOP? |
| Everyone asks who the new champion will be | What permanent role should own the work instead? |
| Managers are not involved after launch | Which local routine would make adoption part of normal management? |
| The champion answers every difficult question | What capability or support route is still missing? |
The Satire
Ensure your rollout and your champion are not one and the same.
Field Note
The Blue Blob and the Finished Transformation
The room where the strange post-transformation clues appear.
Pattern quiz
The Champion Left. Why Did Adoption Leave Too?
Five quick questions about person-shaped adoption.
More Patterns
Keep spotting what returns.
Use the public Patterns tag/archive to keep spotting what repeats.
Want the deeper version when it lands?
The deeper Champion Vacuum Insight and future Toolkit are coming later. Subscribe for the next Pattern drop.
This is a lightweight Guide, not an organisational diagnosis or an instruction to remove useful support. Champions can be valuable. The useful question is whether ownership, routines and capability remain when the person steps away.
