Somewhere in your office there's a spreadsheet that isn't supposed to exist. The system you pay for was meant to replace it. Everyone knows about it, nobody mentions it, and if it disappeared tomorrow a job would slip by Thursday. That spreadsheet is not a failure of discipline. It's the most honest piece of information in the building about where your software doesn't fit the way you work.
What workarounds look like
- The side spreadsheet, usually tracking something the system can't show in one view.
- Double entry: the same job typed into the estimating program, the scheduling board and the accounting system by three different people.
- The sticky note on the monitor with the step the software forgets.
- The group text that is, in practice, where job information actually lives.
- The extra steps inside the software itself, the clicks everyone learned to make because the screen was built for a different kind of shop.
- The one person who knows where everything is, which is a workaround with a name.
Over time these become the norm. Nobody remembers that they were improvised. New hires are trained on the workaround as if it were the process, and in a sense it is.
What they're telling you
Each workaround marks one of three gaps. A process the tool was never built for, so your people carry it by hand. A view or report the tool can't give you, so somebody rebuilds it every Monday. Or a handoff the tool doesn't know about, so the information travels by text. Read the workaround and you've read the gap, far more accurately than any software demo will.
This matters because the usual response is to feel bad about the purchase and push people to "use the system." That treats the signal as the problem. Your office manager didn't build the spreadsheet for fun. She built it because the business needed something the tool couldn't do, and she was the one standing there.
Cut the fluff. What's left is the heart of how your shop runs.
Three ways to answer a workaround
1. Change the process
Sometimes the workaround is the process, and the best move is to make it official. Write it down, give it an owner, and stop pretending the system does it. Nothing to buy.
2. Change the setup
Sometimes the tool can do the thing and nobody configured it, because training happened once and the person who set it up has moved on. Worth checking before anything else. This is also where an honest read before any purchase pays for itself.
3. Build the missing piece
When the workaround is the heart of how your shop runs, when the side spreadsheet is really the job board, or the group text is really the dispatch system, that's the case for a small custom build. Not replacing everything. Building the one piece around your process and connecting it to what you keep. With today's pricing that's weeks, not a year, and your accounting, billing and project software stay put.
How to find yours
- Ask your people one question: what do you do by hand that the system should do for you?
- List the spreadsheets, the group texts and the sticky notes. Don't judge them yet.
- For each one, name the gap: process, view, or handoff.
- Pick the one that would take the most weight off if it went away. Start there.
Workarounds should not tax you, your people or your business anymore. But the first step isn't buying anything. It's listening to what the workaround has been trying to tell you.