Implementing new technology in an organization succeeds or fails on people, not software. Study after study puts technology project failure rates between 60 and 70 per cent, and the root cause is almost never the technology itself — it is resistance, unclear ownership and poor communication. This playbook combines Kotter’s 8-step framework and the ADKAR model into a practical sequence Malaysian enterprise teams can follow from kick-off to measurable adoption.
Why do technology rollouts fail in most organizations?
They fail because leaders treat deployment as the finish line when it is actually the starting line. A new ERP, CRM or workflow system does not create value the moment it goes live — it creates value only when the majority of intended users change their daily behaviour to use it properly. That change is hard, and it does not happen by accident.
The top five reasons rollouts stall, in our experience across ten years and 180+ projects since 2012:
- No clear executive sponsor — senior leadership delegates and disengages
- Weak case for change — staff do not understand why the old system is being retired
- Undertrained users — a two-hour webinar is not a training programme
- No feedback loop — complaints pile up with no visible response
- Measurement gap — adoption is not tracked, so nobody knows if the project worked
Every one of these is a change-management problem, not a technology problem. The good news: all of them are solvable with a disciplined playbook.
What is Kotter’s 8-step change model?
John Kotter’s 8-step framework remains the gold standard for organisational change. It maps cleanly onto technology rollouts in Malaysian enterprises:
- Create urgency — why must we change, and why now?
- Form a guiding coalition — a cross-functional steering committee with real authority
- Develop a vision — a one-page picture of the future state everyone can understand
- Communicate the vision — repeat it across town halls, newsletters, Teams channels
- Empower action — remove blockers, reassign budget, protect the team from politics
- Generate short-term wins — ship something visible in the first 60 days
- Sustain acceleration — build on early wins with expanded scope
- Anchor in culture — make new behaviours part of performance reviews and onboarding
Skipping any of these steps — especially steps 1, 6 and 8 — is the fastest way to kill a project.
How does ADKAR complement Kotter?
Where Kotter operates at the organisational level, Prosci’s ADKAR model works at the individual level. It describes the five sequential states every single employee must move through for change to stick:
| Stage | What it means | What to deliver |
|---|---|---|
| Awareness | I understand why the change is happening | Town halls, CEO emails, FAQs |
| Desire | I want to participate and support it | Incentives, peer champions, manager 1:1s |
| Knowledge | I know how to operate in the new way | Formal training, e-learning, job aids |
| Ability | I can actually do it on the job | Coaching, sandbox access, shadow sessions |
| Reinforcement | The change sticks | Metrics, recognition, continuous feedback |
Most Malaysian enterprises over-invest in Knowledge (classroom training) and under-invest in Awareness, Desire and Reinforcement. The fix is to spread effort evenly across all five stages.
What does a practical rollout sequence look like?
Combining the two frameworks into a real-world sequence for a Malaysian enterprise deploying, say, a new field service app across 400 technicians:
- Weeks 1 – 2: Stakeholder mapping — identify executive sponsor, department heads, influential line managers and sceptics
- Weeks 3 – 4: Vision and communication plan — one-page vision, FAQ document, comms calendar
- Weeks 5 – 8: Pilot programme — 20 users from one region, daily standups, visible fast fixes
- Weeks 9 – 10: Pilot retrospective and adjustments — incorporate feedback into training and UX
- Weeks 11 – 16: Phased rollout — region by region, with in-person super-users present
- Weeks 17 – 20: Reinforcement — dashboards, recognition programmes, management KPIs updated
The pilot is the single most important element. It generates the short-term win Kotter calls for, builds credibility for sceptics, and surfaces integration issues before they scale. You can see how we run pilots inside our system integration service and our broader digital transformation service.
How do you measure whether adoption is actually working?
Adoption is a number, not a feeling. The metrics that matter:
- Active users — daily and weekly, as a percentage of licensed seats
- Feature depth — how many of the core workflows each user touches
- Time-to-task — how long common jobs take compared to the legacy system
- Support ticket volume and trend — spiking up is a warning sign
- User sentiment — quarterly pulse surveys with Net Promoter Score
Set targets at kick-off and review them weekly during rollout, monthly afterwards. A healthy benchmark for Malaysian enterprise rollouts: 70% weekly active usage within 90 days of go-live, rising to 85% within 180 days.
Common Malaysian enterprise pitfalls to avoid
A few patterns we see repeatedly with local clients:
- English-only training materials — provide BM versions where the workforce expects it
- No line-manager buy-in — if supervisors keep using the old Excel sheet, staff will too
- Hybrid/remote gaps — in-person training sessions that exclude remote staff
- Under-invested super-users — give your champions time off regular duties, not just a title
Talk to Us
If your organisation is preparing to roll out a new ERP, field service app, customer portal or workflow system, the hardest part will not be the software — it will be getting people to use it. Book a free consultation and we will help you design the change-management playbook, pilot programme and adoption metrics that turn your technology investment into measurable business outcomes.
