Diagnose adoption by the missing ADKAR outcome
Use ADKAR to identify the adoption barrier behind an ERP user behavior.
The move: diagnose the barrier before choosing the intervention. ADKAR is useful in ERP because adoption failure usually looks like one vague thing: people are not using the system correctly. That phrase hides different causes. A user can understand the business reason and still lack system confidence. A manager can know the new process and still reward the old one. A department can attend training and still reject a workflow because it slows a critical customer promise. Use ADKAR as a five-lens diagnostic. Awareness is the why. Desire is the personal commitment. Knowledge is the how-to. Ability is performance under…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in