Playbook 6 — The Change Scorecard
The four numbers that tell you if adoption actually happened
Most rollouts report on the wrong thing. They report the launch — licences issued, sessions held, a survey taken on the last day. None of that tells you whether the change took. Four numbers do.
Usage rate. Not seats purchased; the share of the intended users who actually used the tool on the task it was rolled out for, in a given week. On its own this is the weakest of the four, because it collapses under pressure, which is exactly why it cannot travel alone.
Non-reversion rate. Of the times the task came up, how often did it get done the new way rather than the old one. This is the number that catches the quiet failure: someone using the tool and the old process side by side, choosing the old process whenever it is faster. If reversion is not measured, it is not noticed.
Self-reported confidence. People’s own read on whether they can do the task without help. It is subjective and easy to game, so treat it as a leading indicator, not proof — a drop here usually warns of a usage drop before the usage data shows it.
Manager-observed competence. Whether someone who knows the work would say this person can now do it to standard, unsupervised. This is the most expensive number to collect and the most honest. It is also the one that separates “trained” from “able” in Playbook 4.
Less is more here. Four numbers, read together, beat a dashboard of twenty. And they belong on the same rhythm the rest of the site already uses for value: check at 30 days, 90 days, and 180 days. Thirty days tells you if the launch landed. Ninety tells you if it survived the first busy patch. One hundred and eighty tells you if it is now just how the work gets done.
A scorecard that fits on one screen:
| Measure | What it answers | Cadence |
|---|---|---|
| Usage rate | Are they using it at all? | Weekly |
| Non-reversion rate | Are they using it instead of the old way? | 30 / 90 / 180 days |
| Self-reported confidence | Do they believe they can do it? | 30 / 90 / 180 days |
| Manager-observed competence | Can they, unsupervised, to standard? | 90 / 180 days |
The point of the scorecard is not reporting. It is that the sprint’s scale-or-stop decision needs adoption data to decide with, and without these four numbers the decision gets made on the same thing that started the project — someone’s impression.
The series in one line: awareness and desire earn the right to train; training and coaching build the skill; reinforcement is what makes the first ninety days outlast the rollout’s own momentum.