Why Your Team Isn’t Using the Software You Bought
Five reasons adoption fails — and the two moves that recover it
By Steele Consulting
It’s six months after the rollout. You picked the tool carefully. You bought the licenses. You ran the training session. The vendor delivered what they promised.
Usage is at 40% of target. You can’t quite tell which 40%. Half the team says they’re using it; the other half says they are too, but their definition of “using it” is logging in weekly to check something. The workflows the tool was supposed to replace are still running on the old spreadsheets, the old email threads, and the old process documents.
You bought a solution. You got a very expensive tab in people’s browsers that mostly stays closed.
In our 24 years at Steele Consulting building software for growing businesses, we’ve watched this exact failure mode play out so often that we can usually predict it before the rollout starts. The reasons the team isn’t using the tool are almost always the same five. And they’re almost never software problems.
This post is about those five reasons, how to recover a rollout that’s already stalling, and how to set up the next one so this doesn’t happen again.
Why this isn’t a software problem
The first move is giving up on the hope that another feature, another training session, or another vendor fix is going to change the adoption number. It isn’t.
Adoption is a people-and-process problem that software vendors are specifically bad at solving — because solving it would require them to intervene in the client’s organization, which they can’t. The vendor delivered a tool that works. Whether anyone uses it is downstream of decisions you made (and didn’t make) before, during, and after the rollout.
Buying the software is the easy part. Buying is a one-decision procurement event. Adoption is an ongoing organizational change — and most rollouts don’t treat it that way.
The 5 reasons adoption fails
Five patterns show up reliably. Any two in the same rollout means usage will be weak. Three or more means the rollout is in trouble.
1. There’s no clear “why” for the team
The tool solves leadership’s problem — better visibility, better reporting, lower cost — but it doesn’t solve the user’s problem. The user is being asked to change their workflow for somebody else’s benefit. Their incentive to adopt is zero or negative.
The fix starts with naming the specific benefit for the person using the tool. Not “it gives us better data.” Something concrete: “it eliminates the manual reconciliation step you’ve been doing every Friday afternoon for three years.” If that sentence doesn’t exist for a given user, that user isn’t going to adopt.
2. The old way still works
The new tool was layered on top of the existing workflow instead of replacing it. The spreadsheet still gets updated. The email thread still runs. The process document still gets referenced. The new tool is an addition — one more place to put the same data — not a replacement.
Humans are extraordinarily efficient at reverting to the familiar when the familiar still functions. Rollouts that leave the old way intact are rollouts that don’t land.
3. Nobody owns adoption
The software was bought by a specific person. The deployment was managed by IT or a vendor project manager. The training was run by the vendor. Then — on go-live day — the project ends. Nobody in the organization has adoption as an ongoing responsibility.
Rollouts need a named internal owner for 90 days post-launch. That person tracks usage, chases down the users who aren’t engaging, surfaces the real blockers, and reports to leadership. If nobody’s job is adoption, adoption isn’t anybody’s problem — and nobody’s problem means nobody’s win.
4. The tool makes someone’s job harder
One group benefits. Another pays. The new sales tool gives leadership better pipeline visibility but adds 15 minutes a day of data entry for the reps. The new ops tool simplifies reporting but adds a reconciliation step for finance. The new HR tool streamlines leadership approvals but adds a form managers now have to fill out.
The group that pays almost always has more power than the rollout plan assumes. Reps will stop entering data. Finance will keep their own spreadsheet. Managers will route around the form. The tool rolls out looking successful on day one and quietly erodes to 40% usage by month six.
5. Leadership isn’t using it either
Senior leaders asked for the tool. Senior leaders bought the tool. Senior leaders don’t log into the tool. They still ask for the old reports, reference the old dashboards, make decisions in meetings based on the old data.
The team reads that signal. Loudly. If leadership doesn’t operate from the new tool, nobody below them will either. This is the single most reliable predictor of adoption failure we see in client rollouts — and the single hardest one to say out loud in the organization.
How to recover an adoption failure already in progress
If you’re six months in and usage is below target, two moves recover most situations.
First, pick one specific workflow and kill the old way. Not all of them — one. Pick the workflow where the new tool is actually better, assign a named owner who is accountable for making the switch stick, and formally retire the old process. Announce it. Measure usage on that one workflow. When it lands, do the second one.
Rollouts that try to switch everything at once usually switch nothing. Rollouts that switch one thing at a time build momentum and credibility for the next switch.
Second, interview the five people whose adoption matters most and ask what would make them use the tool. Not “how do you like the tool?” Specifically: “what would have to be true for you to be using this every day?” Their answers are almost always specific and fixable. Fix them. If what they describe is unfixable — the tool doesn’t do what they actually need — that’s important information too. Better to find out now than in another six months.
How to set up the next rollout to avoid this
Four moves at the start of the next rollout materially improve the odds.
- Include the end users in the selection. Not as token participants — as real voices. If the people who will use it every day didn’t help pick it, they won’t own it.
- Name the specific benefit for each user group before you buy. If you can’t name it, you’re not ready to buy.
- Plan the retirement of the old way at the same time as the deployment of the new way. A rollout isn’t complete until the old way is gone.
- Assign an internal adoption owner before go-live. Give them 90 days of explicit responsibility and real measurement.
How this connects to the other decisions you’re making
Adoption failure is the specific reason “the software works, but the ROI never showed up.” It’s a Friction Cost in the DRIFT framework — labor spent working around a tool instead of with it. It’s the same failure pattern we described in Why Most Dashboards Get Ignored, generalized to any internal tool. And it’s usually downstream of a vendor that was strong on Delivery and weak on Discovery, which we covered in Discovery vs. Delivery — the gap between “what we built” and “what will get used” is exactly the discovery work most vendors skip.
Book a call
Twenty-four years of building custom software. Both sides of the table on more decisions than we can count. And a track record of telling clients honestly when the answer is us and when it isn’t.
If you’re sitting in the middle of this decision right now, that’s the conversation we’re built for. Book a 30-minute call and we’ll walk through it with your specific situation. No pitch. No pressure. You’ll leave with a clearer picture of what to do — whether you work with us or not.