Getting your team to use new software when the office resists

Staff take to new software when it removes a job they dislike, starts with one task rather than everything, and has a named owner on the team. Explain why you're changing, involve the person most likely to resist, run the old and new way side by side for two weeks at most, then switch the old one off. Most rollouts in small firms fail by drifting, not by refusal.

Why does the office resist new software?

Usually because it adds work before it removes any, and because the people asked to change weren't asked about it. An office manager who has kept the business running from a spreadsheet for years has reason to be wary: the spreadsheet works, and the new system makes them a beginner again.

He brought in a new system because quoting air conditioning work was eating his weekends. His air con quotes went from four or five hours to about 20 to 25 minutes. The early frustrations were real and small: the inbox, a footer rule that got forgotten, the wrong time zone, and admin staff resisting the change. None of those were reasons to stop, and all of them needed fixing quickly, because each one gave the doubters a reason to go back to the old way.

What does a half-used system cost?

More than either system on its own. While the team is split, someone has to enter work twice, check two places and reconcile the gaps. That's why the side-by-side period needs an end date.

The £16 an hour is an assumed cost for office time including employer costs; it's above the National Living Wage of £12.71 an hour for workers aged 21 and over from 1 April 2026. Use your own figure.

How do you introduce it to the team?

Talk to them before you buy, not after. Explain the problem it solves, what changes for each person, and what stays the same. Acas guidance on changing employment contracts says employees are more likely to support change when they understand the reasons and feel their views count. A new app usually isn't a contract change, but the same approach works.

Morning all,

From date we're trying software name for one task, e.g. job sheets.

Why: the problem in plain words, e.g. we lose about an hour a day chasing job sheets and some never reach the invoice.

What changes for you: e.g. at the end of each job, fill in the job sheet on your phone. Photos, materials used and time on site. About two minutes.

What doesn't change: e.g. the diary, how you order parts, your hours.

Name is testing it first and will help anyone who gets stuck. For two weeks we'll keep the paper sheets as a backup. From date, paper stops.

Tell me what's annoying about it. If something's slower than before, I want to know.

Your name

What does a four-week rollout look like?

One task, one champion, a hard switch-off date. Don't roll out quoting, scheduling, invoicing and timesheets in the same month.

1. Week 0: choose the task and the champion.

   Pick the job everyone dislikes most. Ask the person most likely to object to test it with you. Their objections in week 0 are cheaper than their resistance in week 3.

2. Week 1: set it up with real data.

   Load your real customers, price list and templates. A demo full of fake jobs proves nothing. Fix the obvious annoyances, such as email footers, time zone and notification settings, before anyone else logs in.

3. Week 2: two people, live jobs.

   The champion and one engineer use it on real work. Keep the old way as a backup. Note every complaint.

4. Week 3: everyone, with the old way as a backup.

   Short show-and-tell at the morning brew, ten minutes, on a phone, not a laptop.

5. Week 4: switch off the old way.

   Bin the paper sheets, archive the old spreadsheet as read-only, and say so.

6. Weeks 5 to 8: check usage weekly.

   Who's filling it in, and who isn't. Fix the reason, not the person.

How do you get engineers to report time and materials?

Make it shorter than the old way, do it on the phone they already carry, and close the loop so they see why it matters. A gas firm we spoke to named getting engineers to report materials and time as one of its main problems. A WhatsApp voice note or a photo of the merchant receipt is easier than a form, and any system that accepts those will get more of the data back.

Close the loop by showing the team what the data does: the invoice that went out the same day, the job that turned out to lose money, the van stock that no longer runs out. Engineers' job sheets for time and materials covers the details to capture.

How do you know the rollout is stalling?

Look for drift in the first month. Nobody announces they've stopped using a system; they quietly go back to what worked.

If you see two or more, go back to step 3 with the person who's drifted. Ask what's slower than before and fix that first. Once it's working, keep files and photos in the same predictable place too; see organising job files. Our guide to the six morning numbers is a good first use for a new system, because the owner sees the benefit every day.

Common questions