Jared Lukes. Start here

Where to start · Updated 2026-10-19

We bought software and nobody uses it. What now?

The tool is almost never the problem. The rollout was. Software gets used when it fits the way people already work, when the people were involved in picking it, and when somebody made it the easy path. Fix those three and the same tool usually works. Buy another one and you will be here again.

I hear this one with a sigh. Somebody spent real money, there was a kickoff, everybody logged in once, and now it is a line item.

Why does nobody use it?

Three reasons, usually all at once:

  • It does not fit the work. The tool assumes a process your team does not actually follow. So they do the real process the old way and update the tool later, or never.
  • Nobody asked them. It was picked in a meeting they were not in and rolled out in a memo. People do not adopt things done to them.
  • The old way is still easier. If the spreadsheet is open and the tool needs a login, the spreadsheet wins every single time.

None of those are fixed by training. Training is what companies do when they do not want to admit the rollout was the problem.

Is it the tool or the rollout?

Ask three people who are supposed to use it to show you how they do their job. Not how the tool wants them to. How they actually do it. If their real process could live in the tool with a few changes, it is the rollout. If their real process and the tool are describing two different jobs, it is the tool, and no amount of nagging will fix it.

Most of the time it is the rollout.

What is the fix?

  1. Put the real work on the wall. The people who do it, in a room, mapping what actually happens. This takes a day and it is the workshop.
  2. Change the tool to fit the work, not the other way around. Turn off the parts nobody needs. Rename things to what your team calls them. Connect it to the spreadsheet instead of fighting it.
  3. Make it the easy path. The tool has to be where the work starts, not an extra step at the end. If the order comes in by email, the tool reads the email. If the day starts with a list, the tool makes the list.
  4. Let the team pick what goes first. They know which part of the tool would help on Monday. Start there, and only there.

Should we just buy something else?

Not until you have done the four steps above, because you will buy the new one the same way and it will sit there too. The exception is when it is genuinely the tool, and you will know that in the first hour on the wall.

What does this cost to fix?

A day in the room is $3,500. If the fix needs ongoing hands, getting the team using it properly is $3,500 a month for as long as it takes, usually a quarter. Compare that to what the unused subscription has cost so far, and what another one would.

Answered by Jared Lukes, Minneapolis. Twenty-five years in brand, UX, and technology, currently holding fractional AI and technology seats at three companies. About Jared.

Quick answers

Is this an AI problem or a software problem?
Same problem. AI tools get bought and ignored for exactly the same three reasons, just faster.
Can you fix it without the vendor?
Usually. Most of the fix is configuration, workflow, and making it the easy path. If the vendor needs to change something, I handle that call.
What if the team just refuses?
In twenty-five years I have never met a team that refused a tool that made their own day shorter. They refuse tools that make someone else's day shorter at their expense.
How long before people are actually using it?
Two to four weeks after the workshop for the first group, a quarter for everybody. Measured by whether the old spreadsheet is still open.
Should we cancel the subscription in the meantime?
Check the contract first. Then decide after the day on the wall, not before.

Got a version of this question that is more specific?

A 30-minute call, no deck, no pitch. Tell me what is stuck and I will tell you straight if I can move it.