Less is More: Options vs. Adoption

I've sat in a lot of technology meetings. The one that repeats itself in every organization, regardless of size or industry, goes something like this: someone in leadership pulls up a dashboard, squints at it, and says, "Can we get more data on this?"

The answer is always yes. Whether anyone will actually use it never comes up.

Leaders are paid to anticipate problems, spot trends, and have answers ready. More data feels like more control. More fields, more filters, more reporting columns — these feel like responsible decisions. So the system gets customized. Fifteen fields get added to the job record. A reporting module gets bolted on. The tool that used to take thirty seconds to log a call now takes four minutes and involves dropdown menus nobody agreed on.

Leadership feels good. They have options.

The technician in the field needs to close the job ticket before his next appointment. The dispatcher needs to know which jobs are open and who's closest. The office manager isn't building pivot tables — she's doing whatever is fastest and moving on.

When a system gets complicated, frontline workers don't complain about it. They route around it. They keep a notepad. They use a group text. They carry the job details in their head and hope nothing falls through. The data leadership wanted never gets entered. The dashboard fills up with garbage. Decisions get made on information that doesn't reflect reality.

I've seen this enough times to know that adoption is the only number that matters. A system five people actually use beats a system twenty people were supposed to use. The best workflow is the one that disappears into the background — because it fits how work actually gets done, not how leadership imagined it would.

The technology sales cycle never shows you this. Demos are designed for decision-makers. They're optimized for the person with the budget, shown in a conference room to someone who will open the system twice a week. Nobody demos it for the person logging forty interactions a day from a truck.

The first question I ask when working with a small business isn't what data do you want. It's who has to enter it. If the answer is someone busy, distracted, or moving between job sites all day — the system has to be nearly invisible to work.

I spent years watching businesses spend real money on technology that sat unused six months after launch. The problem was never the software. It was that nobody built it for the people doing the work.

When your team actually uses the tools, the data takes care of itself. Everything else follows from that.

Devin Elder is the founder of Ark40 Consulting, a San Antonio-based firm helping small businesses build technology that works for the people using it — not just the people buying it.