How to measure adoption after an implementation
Whether people use the thing you installed, expressed as a number you can defend.
Adoption is not logins. A team can log in every day and still keep the real list somewhere else. Adoption is whether the practice the tool was meant to carry is actually being carried, and the only people who know that are the people doing the work.
So you ask them, on a short fixed set of questions, on a schedule, and you compare like with like. The measurement is worthless if the questions drift between rounds, which is why the set is frozen once and the pulses reuse it.
Two rules make the number defensible. The scale describes observable states rather than feelings, so a 3 means there is an agreed way that most people follow, not that somebody feels positive. And individual answers stay aggregate, because a team of four that thinks its answers are identifiable gives you four identical answers.
Do this with Adoption Evidence
One engagement free. Curate the questions, baseline the team, and generate a report where every number traces to a response or a file. No card.
Already have a The Art of Service account? Sign in.