Five blocks, with the focus on the second
Awareness, desire, knowledge, ability and reinforcement. Projects spend almost their entire change budget on knowledge — training, manuals, videos — and virtually nothing on desire. Yet desire is where adoption is decided: if a supervisor believes the new platform exposes their performance or removes their discretion, they will not use it no matter how well they know how.
Diagnose by group, not by organization
The broken block differs by population, and so does the intervention.
- Executives: awareness is usually covered; the risk is reinforcement, they stop asking
- Middle management: desire almost always fails, because change costs them control
- Frontline: ability fails, not knowledge — there is no time or equipment to practice
- Support functions: reinforcement fails, they revert at the first workload peak
Measure adoption, not attendance
Training attendance, satisfaction surveys and opened emails are not adoption. Adoption is the share of transactions running through the new process, real cycle time and the decline of workarounds. That metric must exist before deployment, with a baseline.
Reinforcement: the first ninety days
Backsliding happens between week four and week twelve, once the project team has demobilized. Leaving budget and named owners for that window costs a fraction of relaunching the initiative a year later.
Key takeaways
- The broken block is rarely knowledge; it is usually desire or ability.
- Diagnose by population: middle management is the most common failure point.
- Adoption is measured in transactions and cycle time, not attendance.
NS frameworks and reference sources
- Prosci — ADKAR change management model
- McKinsey — Why transformations fail
- Kotter — Leading Change
This article develops proprietary NS Business Strategy frameworks, drawing on our project base and on public industry literature and studies cited above. Figures are reference ranges; each project is measured against the client's actual data.