Buying the software is the easy part. Getting a busy team to use it takes an owner, steady training, and a date to shut off the old system.
TL;DR: New software doesn't usually fail on launch day. It just stops getting used. Everyone sits through the training, the old system stays on "just in case," nobody owns making the new one work, and a few months later, people are back to their old habits. Gartner found that 60% of workers have been frustrated by new software at work, and after a bad experience, 40% use as little of it as they can or avoid it altogether. Buying something else won't solve it. What works is a person with real time to own the rollout, training that doesn't stop after week one, a hard date to shut off the old system, and leaders who use the new one where everyone can see them.
Walk into almost any firm, and there's at least one piece of software everybody agreed to buy, and hardly anybody uses. It got demoed, approved, and rolled out with a lunch-and-learn. Then the busy season hit, and the old workarounds came right back.
It's the January gym membership of the tech world. You sign up full of good intentions, buy new shoes, maybe even book a session with a trainer. By March, you've been twice, the charge still hits your card every month, and the only thing getting a workout is your bank account.
It's not cheap, either. Per-seat pricing adds up fast, and every unused license is money spent on good intentions. The higher cost shows up later, when someone pitches the next upgrade, and a partner says, "Remember the last one?"
And it's harder than it used to be. Tools change every few months, AI features show up in updates nobody asked for, and even people who like technology have trouble keeping up. Getting people to use a new system used to be a launch-week job. Now it never really ends.
The good news is that unused software is almost never the software's fault. It comes down to how the tool was introduced and who's looking after it once the trainer leaves, and any firm can fix that.
In IT, we call it shelfware, and it rarely looks like a tool nobody opens. More often, people open it grudgingly, use it for one or two things, and work around the rest. The document system has a perfectly good search, but half the office still emails files to themselves. The practice management tool can send deadline reminders, but someone still keeps a calendar on the whiteboard. It's like paying for the whole house and living in the kitchen.
And the subscription is only part of what it costs. There's the time that went into the rollout, the double work when people keep both systems going, and the reports that never quite add up because half the data lives somewhere else. Give it a few years, and a mostly ignored tool can end up costing more than if the firm had never bought it.
Gartner surveyed nearly 5,000 workers and found that 56% wished management would just bring back the old system after a rollout. That's not people being stubborn. They're protecting their workday from something that hasn't made it easier yet.
So before you blame the software, look at how it showed up. Most of the time, the platform can do the job. The rollout is what fell short.
And if you're still deciding whether a new platform is the answer at all, start with our post on why new software can't fix a process that's broken or was never there.
Launch day usually goes fine. The vendor runs a training session, everybody gets a login, and there's a little buzz about finally having something modern. Then a big deadline hits, people get busy, and the questions start piling up with nobody around to answer them.
Most of the time, the problem is ownership. The vendor set it up, IT installed it, and nobody inside the firm is on the hook for whether people use it. Without an owner, little annoyances turn into habits, and habits are tough to break. That person doesn't need to be technical. They need to be someone people already go to with questions, who can make small calls about how the system gets used and has the time to follow up when something's off.
Training's the other half. One session on launch day covers the basics, and most of it's gone within a few weeks. Nobody's going to master everything at once, and they shouldn't have to. Start with the handful of things each role does every day, get people comfortable with those, and build from there.
And when people struggle, give them some grace. Most were never shown more than the basics, and you can't blame anyone for sticking with what they know. What helps is more teaching in smaller doses. A quick refresher around the 30-day mark, once people have used the system enough to have real questions, usually does more good than the big launch session did.
This one comes up all the time. The new platform goes live, but the old one stays on as a backup. Within a month, people are back in it for anything urgent, because that's where they know where everything is.
It makes sense from where they sit. When the pressure's on, people reach for what's familiar. Gartner found that 36% of business leaders say their teams tend to hold back and wait to see whether a change will stick before committing to it. Leaving the old system running answers that question for them.
The fix is a firm retirement date, announced early, repeated often, and kept when it arrives. Move the data the firm needs, flip the old system to read-only on the day you promised, and then shut it off. Leaving it available to look things up for a month or two after the cutoff is fine, as long as nobody can enter new work in it. That gives people a safety net without an escape hatch, and it eases the worry that something important got left behind. Moving that data the right way comes with its own costs and decisions, which we cover in our look at what a platform migration really costs.
People take their cues from the top. If a managing partner keeps asking for the old weekly report instead of pulling it from the new dashboard, everyone else figures out pretty fast that the old way is still the real way. Nobody says it out loud. They just follow the leader.
And it's not just reports. A partner emails a document instead of saving it to the new system, or asks someone to update the spreadsheet that the platform was supposed to replace, and months of training go out the window with one request. Most of the time, they don't even realize they're doing it.
The other piece is letting go. The partners who pushed for the purchase often want to stay in charge of the rollout, but they're also the busiest people in the building. Hand it to someone who has the time to own it. At first, they might run it at 60% of how you would, then 80%, and before long, they'll probably know the system better than you do. We went through the same thing at Heroic, handing off work we'd always done ourselves, and it wasn't easy. Handing it off also means backing that person up when someone pushes back.
The simplest thing leaders can do is use the new system where people can see it, ask for things through it, and stop making exceptions for themselves first.
A technology implementation that sticks doesn't need a big budget. It needs somebody paying attention after the vendor packs up. Prosci, which has studied change management for decades, found that projects with excellent change management were about seven times more likely to meet their objectives than those where it was poor.
Start small. Pick a handful of people to try the system on real work before everyone else does, and make sure a couple of skeptics are in the group. If they come around, the rest of the firm usually follows. If they don't, you've found out early. Then find someone in each department who's a few steps ahead of their coworkers and doesn't mind fielding quick questions. They don't need to be experts. They just need to be easy to ask.
After that, check in at 30, 60, and 90 days. Logins and records created will tell you fast whether people are using the thing, and sometimes the answer surprises you. We've had clients convinced their team wasn't using AI, and when we looked, a lot of people were already on the free versions. Go by what the numbers show, then ask the people doing the work what's in their way. Sometimes those conversations turn up a bigger risk, like an aging system still running in the background past its support date, which is what we're tackling in the next post in this series.
Most of the time, unused software comes down to how it was brought in and who looked after it afterward. Nobody owned it, training stopped after the first session, the old system stayed on as a backup, and leaders kept doing things the old way. None of that's hard to fix once someone takes it on. Start with a small group, keep teaching in small doses, set a date to shut off the old system, and check in on how things are going. That's how a purchase becomes something people rely on.
If you've been through one of these, you know the feeling. The renewal invoice shows up for a tool you're pretty sure half the firm ignores. People groan when they hear they have to learn something new. And the next time somebody pitches an upgrade, the partners get a little gun-shy.
We've been there at Heroic, too, with tools of our own that never got off the ground. So when we help a firm bring in something new, we stay with it past go-live. We help plan the rollout, train people in ways that stick, shut old systems down on schedule, and keep an eye on how the new ones are being used. And through our Guide engagements, we can help figure out whether the tool you already have just needs a better rollout before you buy another one.
If there's software at your firm collecting dust, connect with Heroic Technologies and let's get it working. The membership's already paid for, so you might as well use the gym.
1. Why don't employees use new software?
Usually, because the rollout stopped too soon. People get one training session, the old system stays on, and nobody inside the firm owns whether the new tool is working for them. When things get busy, they fall back on what they know. It's rarely stubbornness. Most people just haven't been shown enough to trust the new system yet, and nobody's checking in to help them get there.
2. What should a software rollout plan include?
A good rollout plan names an owner with real time to manage it, starts with a small pilot group, and sets a firm date for retiring the old system. Training should come in short, role-based sessions over the first few months, with someone in each department people can go to with quick questions. Build in check-ins at 30, 60, and 90 days to see who's using the system and where they're stuck.
3. How long does it take a team to adopt a new system?
It depends on the size of the firm and how much the new system changes daily work, but most teams need a few months before new habits feel natural. It goes faster when the old system is shut off on schedule and training keeps going. The effort pays off, too. Prosci found that 88% of projects with excellent change management met or beat their goals, compared with 13% of those where it was poor.