Change Management and User Adoption in IT Projects: Getting People to Actually Use the System
Many IT projects deliver exactly what was specified and still disappoint, because nobody uses the new system the way it was intended. People keep their spreadsheets, find workarounds or quietly ignore the new process. Change management is the discipline that deals with this people side of change. It is different from the change control that manages scope changes, and project managers who confuse the two often under-invest in the part that determines whether benefits arrive.
Two Meanings of “Change Management”
| Aspect | Project change control | Organisational change management |
|---|---|---|
| Question | Should we change the project plan? | How do we help people adopt the new way of working? |
| Object of change | Scope, schedule, budget | Behaviours, processes, roles, habits |
| Tools | Change requests, impact analysis, change board | Communication, training, sponsorship, reinforcement |
| Lesson | Scope Creep and Change Control | This lesson |
Why Adoption Fails
- Users learn about the change late, usually just before go-live.
- The benefit for the individual is unclear: “what is in it for me?”
- Training is a single session that does not match real tasks.
- Managers do not model or insist on the new way of working.
- The old system or process stays available, so reverting is easy.
- Support after go-live is thin, so early frustrations harden into rejection.
Two Useful Models
ADKAR (from Prosci) describes change at the level of the individual through five stages: Awareness of the need for change, Desire to take part, Knowledge of how to change, Ability to implement it in practice and Reinforcement to sustain it. Its value for project managers is diagnostic: if people are not adopting, ask which stage is blocked. Training fixes a knowledge gap but will not fix a lack of desire.
Kotter’s eight steps look at change at the organisational level: create urgency, build a guiding coalition, form a vision, communicate it, remove obstacles, create short-term wins, build on the change and anchor it in the culture. Use whichever model suits the organisation. The underlying ideas overlap: a clear reason, visible leadership, practical support and reinforcement.
A Practical Adoption Plan
- Assess the impact. For each group, list what changes in their daily work: tasks, tools, approvals, reporting lines.
- Segment stakeholders. Identify who gains, who loses, who is neutral and who has influence (see Stakeholder Identification and Analysis).
- Secure sponsorship. Visible, active sponsors explain why the change matters and hold managers accountable.
- Communicate early and repeatedly. Share the reason, the timeline and what it means for each audience, using several channels.
- Train for real tasks. Use role-based sessions with scenarios from actual work, plus quick reference guides and short videos.
- Appoint champions. Super users in each team provide peer support and feed concerns back to the project.
- Plan hypercare. Provide intensive support for the first weeks after go-live (see Go-Live, Deployment and Cutover Planning).
- Measure and reinforce. Track adoption and respond to what the data says.
Handling Resistance
Resistance is information, not obstruction. People resist for understandable reasons: fear of losing status or skills, extra workload, distrust of the project, or a genuine problem the project team has not seen. Listen first. Common responses:
| Cause | Useful response |
|---|---|
| Fear of job loss or reduced role | Be honest about impact; involve the person in shaping the future role |
| Extra effort in the short term | Acknowledge the learning dip; give time and support to learn |
| Doubt that the system works | Share pilot results; fix valid issues visibly and quickly |
| Lack of involvement | Invite users to design reviews and testing |
| Manager not supporting the change | Escalate to the sponsor and align leadership messaging |
Measuring Adoption
- Usage: active users as a percentage of intended users; frequency of key transactions.
- Proficiency: error rates, rework, time to complete tasks, training assessment results.
- Workarounds: shadow spreadsheets or manual steps still in use.
- Support demand: volume and type of helpdesk tickets after go-live.
- Sentiment: short pulse surveys and informal feedback from champions.
- Business results: whether the benefits promised in the business case are appearing (see Benefits Realisation and Post-Implementation Review).
Worked Example: Leave and Attendance Portal
A company introduces a self-service portal for leave and attendance, replacing paper forms and emails. The impact assessment shows managers lose a familiar approval routine, administrators lose repetitive data entry and employees gain 24-hour access. The project manager runs short demos, trains managers using their real approval queue, and appoints one champion per department. In the first two weeks she sees that one location still submits paper forms. A quick conversation reveals poor connectivity on the shop floor, so the project provides kiosk tablets. Adoption data guides the intervention, and within six weeks paper forms drop to near zero.
Common Mistakes
- Treating training as the whole of change management.
- Starting communication only when the system is nearly ready.
- Ignoring middle managers, who decide how their teams actually behave.
- Declaring success at go-live rather than when the new way is the normal way.
- Change control manages the plan; change management helps people adopt the change.
- Use a model such as ADKAR to diagnose what is blocking adoption.
- Combine sponsorship, early communication, role-based training, champions and hypercare.
- Measure real adoption and keep reinforcing after go-live.