The Modern Tech Stack Is Overbuilt (and Underused)
In the last piece, I argued that most technology problems are not technology problems. They are operational ones that become visible once a system is introduced.
Since then, the question I keep getting is a practical one: If the tool is not the solution, why do we keep buying more of them?
In most cases, it comes down to a simple confusion. We mistake capability for capacity.
A Common Pattern
I recently worked with a team that was frustrated they were not “data-driven.” They had done what most organizations are told to do. They invested in strong tools. Slack for communication. Asana for task management. Salesforce for revenue. A dedicated BI platform for reporting.
From the outside, it looked like a well-built system. But when we walked through how work actually happened, the picture shifted.
The issue was not that the team lacked access to data. It was that there were too many places for it to live. Different systems held different versions of the same information. Over time, people stopped trying to reconcile it.
They simplified instead. Important updates moved into private messages. Quick spreadsheets filled the gaps. “Temporary” workarounds became part of the process.
The system still existed. It just was not the one anyone relied on. They did not have a technology gap. They had a technology surplus.
The Cost of “More”
Adding a tool feels like progress. It suggests improvement. It creates the sense that the organization is becoming more sophisticated. But each addition introduces a new layer of friction.
A new system has to be configured. It has to be maintained. It has to be understood. Most importantly, it has to fit into the way people actually work. When that fit is unclear, people do what they always do. They find the simplest path forward, even if it sits outside the system.
That is where things start to break down.
Strategy Over Software
The tools themselves are rarely the issue. The issue is that they are often used in place of a defined way of working. A technology surplus creates a quiet paradox. The more tools you have, the less clarity you get.
Data fragments across systems. Ownership becomes ambiguous. Decisions slow down because no one is fully confident in what they are looking at. At that point, adding another platform does not solve the problem. It just distributes it further.
The more useful move is usually less intuitive. Ignore the software for a moment and map the work.
What is the goal of this workflow?
Where does it start and where does it end?
Who owns each step along the way?
What is the simplest way to support that with technology?
Only after those questions are clear does it make sense to evaluate tools.
A Different Kind of Discipline
In many cases, the highest-leverage decision is not selecting a new system. It is deciding what to remove.
At Guazu, that often means identifying the tools that are duplicating effort or creating unnecessary complexity and stepping them back. Because a system that works is not the one with the most features. It is the one that people understand and use consistently.
If your team has invested in good tools but still struggles to get clear answers, it is often a signal that simplifying the system will create more value than expanding it.
