Change Management Fundamentals

Why Technology Projects Really Fail

When a new system or process doesn't stick, the instinct is usually to blame the tool. Most of the time, the tool isn't the problem. The project skipped the human side of the change — and the technology just happens to be the visible thing that "failed."

A well-known model in this field — ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) — breaks the human side of change into stages people move through, in order, before a change actually sticks. The four fundamentals below cover the same ground in plain language, built for a small or growing business rather than a large enterprise change program.

The Four Fundamentals

People accept change faster — and resist it less — when they understand the problem a change is solving, not just the solution being handed to them. "We're switching systems because the old one takes three extra steps to do X" lands completely differently than "we're switching systems next month," with no reason attached.

Formal authority (a manager announcing a change) and informal influence (the person on the team others quietly ask "what do you think?") are not the same thing. A change can have full management buy-in and still stall if the informally influential people on a team haven't bought in. Identify those people early, and bring them into the conversation before the rollout, not just after.

Knowing a change is coming and being able to do the new thing are different states. A manual or a one-time announcement builds awareness, not capability. People build real capability by doing the task — ideally more than once, with someone available to answer the question that only comes up in the moment of actually trying it. See "Preparing Your Team for a System Rollout" in this Resource Centre for the practical checklist version of this.

This is the fundamental most projects skip entirely. If the old way is still technically available, still easier in a pinch, or if nobody ever checks whether the new way is actually being used, people drift back to what they already know — quietly, without announcing it. A change sticks when going back is harder than moving forward, and when leadership visibly uses the new way themselves.

What Actually Predicts Whether a Change Sticks

A few honest, practical signals, drawn from the fundamentals above:

- Leadership visibly uses the new system too — not just directs others to. - The old way is genuinely retired, not quietly left running "just in case," which it rarely is in practice once that's the understanding. - There's a real feedback loop, and people can see that what they report gets acted on — not a form that collects complaints no one ever responds to. - Someone checks in before people complain, rather than waiting for frustration to build to the point someone raises it unprompted.

The Honest Limit of This Guide

This is a framework for thinking about change, not a guarantee. Every organization has its own politics, history, and personalities that no four-point model fully captures. What this guide is reliable for is this: if a rollout is struggling, these four fundamentals are the right place to look first, before assuming the technology itself is the problem.

---