Adoption stalls at one place at a time. The five factors are sequential, so the first one that does not hold is the barrier — and every hour spent downstream of it is wasted. This instrument names the barrier, the system condition behind it, and the first move.
Resistance is data about the system, not a verdict on the people in it.
The diagnostic is instrument four in the CHANGE & TRANSFORM register. It runs when the future state is being designed, and again inside any ARC event where adoption has stopped moving. It sits after the Stakeholder Impact & Adoption Map — the map says which population to look at, this says which factor is holding that population back.
Every rating is a statement of evidence, not opinion. If nobody can point to the evidence, the condition is not in place — whatever the intent was.
Run the Diagnostic
Instrument · ADKAR® Barrier Diagnostic
Find the one factor that is gating adoption
The five factors are sequential. Rate each condition on the evidence in front of you — the first factor that does not hold is the barrier, and effort spent downstream of it is wasted.
The read
Overall readiness 0% · a factor holds at 67%
Awareness is the barrier. Until it holds, work on Desire, Knowledge, Ability, Reinforcement will not stick.
Value-stream scorecard · Adoption readiness
Publish this read as 0 against a target of 67. Snapshots build the trend view and stay in this browser.
The business case is inconsistent, undated, or told differently by each leader.
First move
Write one case for change — the risk of standing still, the measures, the date — and have every leader tell the same one.
Owner
Sponsor
AAwareness
0% · does not hold · gating barrier
Does the organization know why the change is happening, and what happens if it does not?
One written case for change exists, with the cost of standing still stated.
Every leader tells the same story, in the same words, without improvising.
The affected populations can repeat why the change is happening.
The measures the change will move are published, not implied.
First move: Write one case for change — the risk of standing still, the measures, the date — and have every leader tell the same one.
DDesire
0% · does not hold
Is it rational for these groups to want the change, given what they stand to lose?
The loss each group carries has been named explicitly, not softened.
Affected groups helped design the future state, not just review it.
What is protected — role, pay, standing, headcount — has been decided and said.
Objections are recorded and answered rather than managed around.
First move: Name the loss out loud, decide what is protected, and put the affected groups inside the design rather than on the receiving end of it.
KKnowledge
0% · does not hold
Is the future-state process and role defined well enough to be taught?
The future-state process is documented at standard-work level.
Roles, handoffs and decision rights are written, not assumed.
Training exists for the actual future-state work, not the software alone.
Exceptions and edge cases have a defined path.
First move: Define the future state to standard-work level — process, role, handoff, decision right — before any training is scheduled.
AAbility
0% · does not hold
Can the work actually be done the new way, today, with what people have?
Proficiency has been demonstrated in the real work, not in a classroom.
Capacity and time to work the new way exist in the schedule.
Tools, access and data quality support the new way.
Workarounds are being counted, and the count is falling.
First move: Remove the physical constraint — capacity, tooling, data quality, practice time — then verify demonstrated proficiency at the workplace.
RReinforcement
0% · does not hold
Does the management system reward the new way, and stop rewarding the old one?
Measures and targets reflect the new way, not the old one.
Leadership routines review the new way at a set cadence.
Recognition, escalation and consequence are aligned to the change.
An owner in operations holds the standard after the project closes.
First move: Change the measures, the routines and the recognition so the old way is no longer the rational choice — then transfer ownership into operations.
Load evidence from a spreadsheet
Evidence is usually gathered by several people at once. Download the template, have each factor rated 0–3 against what can actually be pointed to, and bring the file straight back — the organization, change and population above the table load with it.
Columns are matched by their header name, so a rearranged spreadsheet still lands correctly. Blank cells are left alone, and nothing already on this instrument is deleted by an import.
This is a management instrument, not legal, audit, or personnel advice. Record system conditions and stakeholder groups — never third-party personal data. Entries stay in the browser that created them until you export the read.
ADKAR® is a registered trademark of Prosci, Inc., referenced here with attribution. Compass uses the five factors as a diagnostic of system conditions, not as a personality or performance rating.
Where this leads
The barrier becomes work on the ARC Working Board, and the corrective moves are recorded as commitments on the Project Charter.