Adoption Dashboard¶
Monitoring artifact — instantiates Change Resistance Diagnosis and Support
A live instrument panel of lived-use signals — uptake, friction, relapse, workarounds — that shows where adoption is real and where it is only theater.
An Adoption Dashboard is the standing instrument that watches a change after it goes live and reports, continuously, whether people are actually using it or only appearing to. Its defining idea is that it measures lived behavior, and only measures — it neither diagnoses why adoption is stuck nor does anything to fix it. It converts the vague reassurance of a rollout into a small set of tracked signals: who has crossed over, where friction is concentrating, whether quality is holding, and — most diagnostically — whether people are quietly reverting to old routines or building shadow processes on the side. The dashboard's whole value is that it makes non-adoption visible and located rather than discovered months later when the numbers finally come due.
Example¶
A B2B sales organization replaces its aging contact system with a new CRM, and leadership declares the migration "complete" once every rep has logged in. The Adoption Dashboard tells a different story. Seat logins sit at 98% — but deals with notes entered in the CRM hover at 40%, and that lived-use gap is the whole point. Segmented by region, the shortfall clusters in one district where the sales director still runs the weekly forecast off a personal spreadsheet. The dashboard also tracks a deliberate workaround proxy: volume of records exported to spreadsheet, which spikes every Thursday before forecast calls — a shadow process hiding in plain sight. None of this says why the district resists. What it does is turn "everyone's on the new tool" into "adoption is real in four regions and cosmetic in the fifth, and the workaround is the Thursday export" — a located signal the diagnosis and support work can now aim at.
How it works¶
What distinguishes the dashboard from a generic rollout report is the choice of signal:
- Lived-use over vanity metrics. It privileges evidence of real practice (records created, tasks completed in-system, quality of output) over attendance, logins, or sign-off, which are the metrics most easily faked into looking healthy.
- Segmentation to locate, not average. Uptake is broken out by role, site, and workflow point, because resistance clusters — a fleet-wide average of 70% hides a site at 20%.
- Relapse and workaround instrumentation. It carries explicit proxies for reversion (old-tool activity that should have gone to zero) and for shadow processes (off-platform exports, duplicate entry, exception volume), treating these as the earliest and most honest signals.
- Signals as questions. A red cell is a prompt to go ask why, not a verdict on the people behind it.
Tuning parameters¶
- Signal fidelity — vanity metrics (logins) versus lived-use metrics (in-system work of adequate quality). Higher-fidelity signals resist gaming but cost more to instrument and can lag.
- Segmentation granularity — fleet average versus role-by-site-by-workflow breakdown. Finer cuts locate resistance precisely but multiply noise and can single out individuals.
- Refresh cadence — real-time, weekly, or monthly. Faster refresh catches early relapse but invites overreaction to noise.
- Alert thresholds — how far a cell must drift before it flags. Tight thresholds surface trouble early but cry wolf; loose ones stay calm until the relapse is entrenched.
- Workaround-proxy breadth — how many shadow-process signals are tracked. More proxies catch more evasion but risk feeling like surveillance.
When it helps, and when it misleads¶
Its strength is that it makes the difference between compliance and use observable, and it catches relapse while it is still cheap to reverse — the moment a district reverts to spreadsheets, not the quarter the forecast misses.
Its central failure mode is metric theater: the moment a tracked number becomes the goal[1], people optimize the number rather than the behavior, and the dashboard turns green while practice stays unchanged — a textbook instance of Goodhart's Law. Its classic misuse is worse: reading a red cell as a roster of laggards to shame, which converts a diagnostic instrument into a moralizing one and destroys the honest signal it was built to collect. The discipline that guards against both is to keep the metrics anchored to lived use, treat every signal as a question routed to diagnosis rather than a judgment on a person, and rotate the tracked measures before they ossify into targets.
How it implements the components¶
adoption_monitoring— the dashboard is the standing tracker of uptake, friction, quality effects, and unintended harms across roles and sites; it is this component made concrete.relapse_and_workaround_signal— its old-tool and shadow-process proxies detect reversion and workarounds as first-class, early signals rather than surprises found at audit time.
It does not explain the resistance it detects: resistance_source_map and barrier_classification are the work of Barrier Interview Protocol, which supplies the "why" behind a red cell. Nor does the dashboard change adoption conditions — it neither builds skill (transition_support, Training and Practice Program) nor realigns rewards (incentive_and_metric_alignment, Incentive Realignment); it only tells them where to aim.
Related¶
- Instantiates: Change Resistance Diagnosis and Support — the dashboard is the archetype's monitoring loop, the sensor that keeps implementation honest.
- Sibling mechanisms: Barrier Interview Protocol · Incentive Realignment · Migration Assistance · Pilot Rollout · Training and Practice Program · Trust-Building Communication · Participatory Design Session · Transition Support Plan · Change Readiness Assessment
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: The mechanism is a live instrument panel of lived-use signals — uptake, friction, relapse, workarounds — that shows where adoption is real and where it is only theater, so its operative form is repeated observation and operational signaling.
Independent corroboration: The frozen evidence defines Adoption Dashboard as 'A live instrument panel of lived-use signals — uptake, friction, relapse, workarounds — that shows where adoption is real and where it is only theater', so its operative form is Monitoring, Sensing & Alerting.
Nearest alternative: Interface, Display & Cue — The display is fed by repeated observation of actual state, so sensing and signaling—not the visual surface alone—is operative.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Monitoring uptake, reversion, workarounds, and quality after a rollout is a standard organizational change-management control.
Related originating lineages:
- Data Science & Analytics — Telemetry, cohort tracking, and trend panels provide the dashboard implementation.
- Human-Computer Interaction — Behavioral usage measures and friction signals contribute the product-use perspective.
- Sociology & Anthropology — Shadow practices and ceremonial compliance contribute the distinction between visible and lived adoption.
Review resolution: Both reviewers identify organizational change management as primary and agree that analytics, HCI, and sociology are integrated to distinguish lived adoption from vanity metrics. The only ambiguity was boundary-setting between measurement and diagnosis, not provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
A dashboard is only diagnostic if its red cells route somewhere. Left on its own it degrades into a scoreboard; paired with Barrier Interview Protocol — dashboard locates where, interview surfaces why — it becomes the front half of a learning loop rather than an accusation.
References¶
[1] Strathern, M. "‘Improving Ratings’: Audit in the British University System". European Review 5(3), 305–321 (1997). States Goodhart's law that a measure ceases to be reliable when it becomes a target, as target-driven assessment reshapes the activity being measured. registry ↩