I once worked with a business owner who was on the brink of losing the entire business over a falling out with his partner. In the final board meeting before it all came apart, he wanted to spend most of the allotted time discussing which workflow app the business should adopt. The following month, he lost everything.

This happens more often than owners like to admit, because "tool" conversations feel like progress in a way that "people" conversations rarely do. Choosing between two pieces of software produces a clean decision, a demo, a rollout plan, a sense of forward motion. Confronting a partner about a broken working relationship, or a manager about tolerating underperformance, produces none of that. It's slower, more uncomfortable, and far less likely to end in a satisfying decision by five o'clock. So it gets deferred, again and again, in favour of the conversation that feels easier to have.

There's also a quieter version of the same avoidance that has nothing to do with a crisis at all. Announcing a new system to a board, a partner group, or a team can function as a signal of progress even when nothing about how the business is actually run has changed. It's visible, it's easy to describe in a meeting, and it lets everyone feel that something is being done. That feeling is worth being suspicious of. Genuine progress in a business usually looks less like an announcement and more like a hard conversation that finally happened, or a standard that's finally being enforced consistently.

The best business I've seen had the weakest tech stack

The best-run business I've ever encountered had one of the smallest, most out-of-date technology setups I'd ever seen, almost laughably simple by industry standards. Its metrics were the kind most owners only dream about: margins exceeding forty percent, write-ups exceeding twenty percent, double-digit growth year after year, a stable senior team that had been in place for years, and client satisfaction scores consistently in the highest band.

Here's the thing; none of that came from software. It came from a level of management discipline, clarity of standards, and consistency of leadership that most businesses, regardless of how modern their tech stack looks, simply don't have. The tools were almost irrelevant to the result. What mattered was that everyone in the business knew exactly what was expected of them, knew where they stood, and worked inside a culture that had been deliberately built rather than left to develop on its own.

What that discipline actually looked like day to day was unremarkable to watch: a consistent rhythm of meetings that were kept short and specific rather than skipped or left to ramble, direct reporting lines so nobody was unsure who they answered to or who answered to them, and leadership that had clearly been in the habit of addressing small issues while they were still small, rather than letting them accumulate into the kind of problem that eventually needs a system to paper over. None of it required a purchase order.

Software has a place, it's just not this one

None of this is an argument against technology. Plenty of good businesses, including ones I'm personally involved in building, exist specifically to help owners run their operations better through software, and it genuinely helps, particularly when a business needs to scale quickly and consistently. The issue isn't the existence of good tools. It's what they get asked to do.

If you notice yourself hoping a new piece of software will be the quick fix for a problem that's actually about leadership, management, or the discipline to have a hard conversation, it's worth pausing and looking more closely at what's really going on. There's no easy fix hiding in a new app. Software can make good processes faster and good decisions easier to track. It cannot make a decision for you, have a difficult conversation on your behalf, or substitute for a manager who has never clearly defined what good work actually looks like.

Someone still has to define good, bad, and excellent

Every business, regardless of its tech stack, runs on a simple underlying logic: if someone does a poor job, there should be a consequence. If they do a good job, they keep progressing. If they do an excellent job, that should be recognised and rewarded, whether through promotion, additional responsibility, or a bonus. This logic doesn't require any software at all. What it does require is a manager who has taken the time to define, specifically and in advance, what a poor job, a good job, and an excellent job actually look like in this particular role.

This is the part that's genuinely difficult, and it's exactly the part no piece of software can do on a manager's behalf. Standards have to be thought through, written down, communicated clearly, and applied consistently, which takes real time and real discipline. It's far easier to install a new system and hope that visibility alone will drive better performance. Visibility helps. It doesn't replace the judgment of a manager who has actually done the work of defining what good looks like.

What to check before you buy anything

Before adopting a new system, it's worth asking a more uncomfortable question first: is the problem I'm trying to solve actually a tooling problem, or is it a leadership problem I've been avoiding because that kind of problem is harder to face? A business with unclear standards, an avoided conversation, or a genuine partnership dispute will still have that same problem after the new software is fully rolled out. It will simply have it inside a nicer-looking system.

The businesses that consistently perform well aren't the ones with the newest stack. They're the ones where leadership did the harder, slower work first, defining standards, having the difficult conversations, holding people to what was agreed, and then used whatever tools made that already-solid foundation run a little more smoothly.

What's the last piece of software your business adopted, and honestly, was it solving a real operational gap, or was it standing in for a harder conversation that still hasn't happened?