Why won’t my team use the software we paid for?
Usually because it was set up to show everything the product can do, and each person needs a few things when the work reaches them. The vendor’s product stays as it is. I strip your setup back to what each person needs, or build a short screen on top that feeds it.
How common is this?
It’s common at companies of every size. SHRM, citing a 2022 Gartner survey, reports that the average HR system “is used by only 32% of employees.” That’s a system the company chose and paid for, and most of its people still don’t use it.
In my experience it rarely means you bought the wrong product. Software sold to a whole industry has to cover every company in it, so it arrives with every feature and every field switched on. Whoever set yours up was thinking about the information the business wanted to collect, and nobody checked what that did to someone’s Tuesday.
A team that has drifted back to paper, texts or the old spreadsheet is showing you where the software asks for more than the job does. That helps, because it points at specific screens that can be changed.
Is it a training problem?
Usually it has little to do with training. Training shows people where things are. It can’t make a slow process fast, and people will use whichever way finishes the job sooner.
You can check this yourself in ten minutes. Ask one of your best people to do a common task in the software while you watch, then ask them to do the same task the way they used to. If the old way is quicker, more training won’t change anything, and the setup is what needs to change.
While you’re there, ask to see their workarounds: the spreadsheet they keep on the side, the notes they email to themselves. People build those when the software is missing something or makes a step harder than it should be. I ask about them on my first day with a team, because they add up to a specific list of what to fix, written by the people who know the work best.
Why can’t the vendor’s rep fix it?
Because the rep’s job is to teach the product, and the fix comes from watching the work. A trainer walks your people through every screen over a video call or a day on site, then moves on to the next customer. They show what the software can do. They don’t see the dispatcher at seven in the morning with the phone ringing, or the step your bookkeeper skips because the information isn’t in yet.
The support line has the same limit. It answers the question you ask. Why nobody opens the thing is a different question, and it gets answered by sitting beside the people doing the work.
None of that is a knock on the vendor. They sell one product to a whole industry and can’t rebuild it around your company. Most of them do leave a lot adjustable: which fields are required, what each person sees, what order the steps come in. Few small companies have anyone whose job is to adjust it.
How do you fix software you can’t change?
I change your setup of it, and where the setup runs out I build a short screen on top.
I spend a normal working day with the team at your office, in Parker County or west Fort Worth, and watch. I note each point where the software slows someone down, asks for information they don’t have yet, or gets skipped. Then I sort the notes by how much time each one costs and start with the worst.
Most fixes are in the settings. A screen shows forty fields when the person needs six, or a required field can’t be filled in until later in the job. When the settings can’t fix it, I build one short screen for that person. It asks for what they know and sends it into the software you bought.
The new way has to be faster for the person doing the work, and until it is, I leave the old way available. If the product can’t be made to fit at all, having your own built is the other option, and I’ll say so.
What does this look like in a field service company?
Usually the company bought a field service package to run dispatch, work orders and invoicing, and the techs were meant to close out every job on their phones. Closing a job in the software often means a long run of screens: parts used, photos, notes, a signature, payment. A tech in an attic in August, or under a house with no signal, texts the photos to the office and writes the rest on a paper ticket.
So the office retypes. Tickets come in at the end of the day or the end of the week, invoices go out late, and parts that never got written down never get billed. The owner’s reports only show what made it into the system.
I’d start by watching a few techs finish a call. Often the software can be cut down to the handful of things a tech has to enter on site, with the office completing the rest from the same record. Where it can’t, a one-screen closeout on the phone that feeds the package does the job.