Change Management Guide
The ADKAR Model for Digital Transformation
Roughly seven in ten enterprise digital transformations fail to deliver their intended business outcome. The technology is rarely the root cause — people, behaviour and reinforcement are. The ADKAR model, originally developed by Prosci, gives leaders a practical sequence for moving every individual through change. Here is how to apply each step to a corporate digital shift.
Awareness
People need to understand why the digital change is happening before they engage with it.
- Communicate the business case in plain language — the cost of standing still, the customer or safety outcomes at risk, the competitive shift.
- Use executive sponsors and front-line leaders, not just project comms. Repeat the message across formats: town halls, short videos, team huddles.
- Surface data: declining NPS, manual rework hours, lost tenders, regulatory exposure. Concrete numbers beat abstract vision slides.
Desire
Awareness explains the why; desire is the personal choice to support and participate.
- Map stakeholder groups and identify what each one gains or loses — power, status, autonomy, workload, career relevance.
- Address resistance early through listening sessions, not policy memos. Capture concerns and feed them back into the programme design.
- Align incentives, performance objectives, and recognition with the new ways of working — not just the old KPIs.
Knowledge
Once people want to change, equip them with the know-how to operate in the new environment.
- Build role-based learning paths — finance users don't need the same training as field engineers.
- Blend formats: short async videos, hands-on labs, sandbox environments, peer-led sessions. Avoid 90-minute generic webinars.
- Document new processes in the tools people already use (intranet, chat, in-app guidance), not just a one-off PDF.
Ability
Knowing what to do is not the same as being able to do it under real workload and pressure.
- Run parallel-running periods and pilot sites so people practise on real work without breaking production.
- Stand up visible coaching and floor-walking support in the first 30–90 days after go-live.
- Remove friction: clean data, fixed integrations, working hardware, simplified approvals. Most 'resistance' is actually broken plumbing.
Reinforcement
Without reinforcement, organisations quietly revert to the pre-transformation workflow within 6–12 months.
- Track adoption metrics, not just deployment metrics — active users, process compliance, time-to-task, defect rates.
- Celebrate teams and individuals who model the new behaviours; make examples visible across the business.
- Hold leaders accountable in operational reviews. Retire legacy tools, dashboards, and reports on a published timeline.
Common pitfalls when applying ADKAR to digital transformation
- Treating ADKAR as a training plan. It is a sequence of individual transitions — every employee moves through all five steps.
- Skipping Awareness and Desire because 'leadership has decided'. The decision doesn't transfer; the conviction has to be earned.
- Declaring victory at go-live. Reinforcement is the longest phase, not the shortest.
- Running change management as a workstream parallel to delivery. It needs to be embedded in every sprint, release, and operational review.
How SHES-Q applies ADKAR with clients
We embed ADKAR into the delivery plan from day one — not as a separate change workstream. That means change readiness in business cases, stakeholder maps in every release plan, and adoption metrics in operational reviews long after go-live.