Numbers that measure "presence," not "change"
People log in each morning to check the box, then go back to the same shadow spreadsheet. The dashboard says they "use the system," but in reality their working behavior hasn't moved at all.
This is the most dangerous gap — because green numbers make everyone comfortable and stop them asking the questions that matter.
Adoption is a symptom, not the disease
Failed adoption is almost never its own problem. It's a symptom of a deeper layer — unresolved Fear or Identity. Treat only the symptom by forcing usage, and the system gets used for show, then drifts back the moment the pressure lifts.
"If no one forced me, would I still use it?" — the only question that truly measures adoption.
So how do you measure real change?
- Measure behavior, not logins — is work actually done in the system, or just back-filled later?
- Listen to the language — "our system" is worlds apart from "the system they make us use."
- Count the workarounds — every shadow spreadsheet and side chat is proof the system hasn't won people over.
- Diagnose the root when adoption drops — don't add training; ask whether Fear or Identity is still unresolved.
The takeaway
A green dashboard should be the start of a question, not the answer. If the numbers look good but you still sense the organization isn't moving, that's not a faulty instinct — it's a signal that real change is stuck in a layer the dashboard can't see.