More Software Doesn't Mean Better Operations
Adding software feels like upgrading the operation. Often it just adds a layer of digital friction on top of the human friction you already had.
I build software for operations, so I have a commercial interest in you buying more of it. I am going to argue against that anyway: more software does not mean better operations. The two get conflated constantly — a company adds systems and assumes it has modernized — but software is a tool, and more tools do not automatically make a better operation any more than more instruments make a better orchestra.
Plenty of heavily digitized operations are worse than the simple ones they replaced. They just fail in more sophisticated, harder-to-diagnose ways, with a login screen in front of every problem.
Why the conventional wisdom is wrong
The conventional wisdom equates digital with modern and modern with better, so adding software feels like progress by definition. But an operation is the sum of its processes, its people, and its tools working together — and software only improves it when the underlying process is sound and the people can actually use what you gave them. Bolt software onto a broken operation and you do not get a better operation. You get a broken operation with a steeper learning curve and a subscription.
Software adds its own friction — logins, training, maintenance, downtime — that has to be subtracted from whatever value it brings.
A digital version of a bad process is still a bad process, now with the added cost of the digitization.
Tools that do not integrate create new gaps that humans have to bridge by hand, often slower than before.
The operation grows more fragile, because now it can fail in software ways as well as human ways.
What is actually true
What is actually true is that operational quality comes from the design of the work, not from the amount of technology applied to it. A well-designed operation with minimal software will outperform a poorly-designed one with a sprawling stack every time, because the software does not fix the design — it inherits it. The best operations I have seen are often surprisingly low-tech where it counts: a few well-chosen tools supporting a process that was thought through carefully, rather than a pile of platforms compensating for a process that was not.
Software is a multiplier of whatever operation you already have. Multiply a good operation and you get a better one. Multiply a bad operation and you get an expensive, complicated bad one. The technology is never the thing that makes it good.
What we see at TTGC
When clients ask us to improve their operations, they usually expect us to recommend more software, because we are a tech-capable agency and that is what tech firms sell. Frequently we recommend the opposite. We find operations buckling under software they do not need, where the genuine fix is a better-designed process supported by less technology, not more. We have helped operations get faster and more reliable by removing tools and simplifying workflows rather than adding capability. It is a harder sell — nobody feels modern after being told to use fewer systems — but the results are consistent. The operations that work are not the ones with the most software. They are the ones where the work was designed well and the software stayed out of the way.
How to evaluate an operation honestly
Before you credit your software for your operation — or blame it — separate the tool from the design.
If you stripped the software away, would the underlying process still make sense? If not, the software is hiding the real problem.
How much of your operation's effort goes into managing the tools versus doing the actual work?
Did the last system you added genuinely make the operation better, or just make it more digital?
Could a simpler operation with fewer tools deliver the same outcome more reliably?
The honest take
Do not mistake more software for a better operation. Software is a multiplier, and it multiplies whatever quality of operation you already have — so the work to do is designing the operation well, not buying more technology to sit on top of it. Before you add the next system, ask whether the operation underneath is sound, because if it is not, the software will only make the problem more expensive and harder to see. A great operation with a little software beats a mediocre one with a lot of it. Every single time.
Sources
McKinsey & Company — research on why technology investment alone does not improve operational performance. mckinsey.com
TTGC — patterns across client transformation work.
