New Systems Don’t Fail. Old Habits Win: Why Change Is a People Problem

Most businesses don't struggle to buy new systems. They struggle to get people to use them.

The software gets chosen, the contract gets signed and the go-live date arrives. Six months later, half the team is still keeping their own spreadsheet "just in case", the shared inbox is still where the real work happens, and the new system holds a partial, out-of-date picture that nobody fully trusts.

The system didn't fail. Old habits won.

Why habits beat systems

Habits exist for a good reason. They let people get through a busy day without thinking about every step. The problem is that a habit doesn't care whether a better way now exists. When someone is under pressure, they reach for what's familiar.

A few patterns come up again and again:

• Familiarity feels safer. The old way might be slow, but people know exactly how it works and where it goes wrong.
• Workarounds become the process. Over the years, teams build their own spreadsheets, notebooks and email chains. These quietly become the real system, whatever the official one says.
• "We've always done it this way." This is rarely stubbornness. Usually it means the old way has never been shown to be worse in a way that matters to the person doing the job.
• Nobody wants to look incompetent. Learning something new means being slow and making mistakes in front of colleagues. Plenty of capable people would rather avoid that.
• There's no time to learn. If the new system is introduced on top of a full workload, the old way wins by default because it's quicker today.

None of these are technology problems. They are people problems, and they need people solutions.

Signs your rollout is stalling

Adoption problems rarely announce themselves. Look out for:

• Data in the new system is incomplete or lags behind what's actually happening.
• Staff ask a colleague to "put it in the system" for them.
• Managers still ask for updates by email or in a spreadsheet.
• The same handful of people do all the logging while everyone else stays away.
• Reports from the system get questioned in meetings, so nobody acts on them.

If you recognise two or three of these, the issue isn't the software. It's that the new way hasn't yet become the normal way.

How to make change stick

There's a well-known model from the psychologist Kurt Lewin: unfreeze, change, refreeze. People first need a reason to let go of the old way, then support while they make the switch, then something that locks the new behaviour in so it doesn't slide back. The ADKAR model makes a similar point: awareness, desire, knowledge, ability and reinforcement. Training alone covers only one of those five.

In practice, that looks like this:

1. Start with the why. Explain what problem the change solves for the people doing the work, not just for the board. "Fewer chasing emails" lands better than "improved visibility".
2. Involve users early. The people who'll use the system every day know where the old process breaks. Ask them before you decide, not after.
3. Make the new way the easiest way. If logging an incident takes five clicks in the new system and one text message the old way, the text message will win. Remove friction ruthlessly.
4. Retire the old option. As long as the old spreadsheet is still available, it'll still get used. Set a date, archive it and stick to it.
5. Find your champions. Every team has someone others go to for help. Get them on board first and give them time to support colleagues.
6. Celebrate small wins. Share the first audit closed on time or the first report that didn't need chasing. Visible results build momentum.
7. Train in the flow of work. Short, practical guidance at the moment someone needs it beats a long training session they'll have forgotten by Friday.
8. Lead by example. If managers keep asking for updates by email, staff will keep sending them. Leaders need to use the system visibly and ask for information through it.
9. Measure adoption, not go-live. Go-live is the start, not the finish. Track how many people are actually using the system and how complete the data is.

What this means when you choose software

If adoption is the real challenge, it should shape how you choose systems in the first place. Features matter, but so do the questions that decide whether people will actually use it:

• Is it simple enough to use on a busy day? If it needs a manual, it'll lose to habit.
• How many logins will people need? Every extra password is another reason to avoid it.
• Does it guide people through the process? Built-in workflows mean people don't have to remember every step.
• Does it remind people what's due? Automatic reminders replace the chasing that used to rely on one person's memory.
• Can people see the benefit quickly? The sooner someone saves time, the sooner the new habit forms.

This thinking sits behind how we build our products at DMG. Everything runs from one account and one sign-in, with guided workflows and reminders built in, so teams can start getting value in days rather than months.

The bottom line

New systems are the easy part. The hard part is helping people let go of the way they've always worked, and making the new way so straightforward that going back feels like more effort.

Get the people side right and the system will do its job. Get it wrong and even the best software becomes an expensive place to store half your data.

If you're weighing up a change, take a look at our one-minute product tours to see how simple each tool is to use, try the product finder, or get in touch for a chat about what would work for your team.