Transformation Projects Usually Have Too Many Tools
Every new tool promises to simplify operations. Stack enough of them and you build the exact complexity you were trying to escape — only now it has a license fee.
Transformation projects are meant to simplify operations. Too often, they do the opposite. The result is a sprawling collection of platforms. Each one was bought to solve a problem. None of them talk to each other. More tools were supposed to mean more capability. Instead they mean more complexity.
At some point, every new tool stops adding leverage. It starts adding overhead. Most transformation projects sail past that point without noticing. Adding a tool always feels like progress.
Why the conventional wisdom is wrong
The conventional wisdom says the right tool exists for every problem. So the path to better operations is to find the right tool for each one. Each purchase seems rational on its own. But nobody accounts for the cost of the whole stack. The integrations. The context-switching. The overlapping features. The data scattered across a dozen systems. Ten tools that each solve one problem can create a bigger problem than the ten they solved.
Every tool added is another integration to maintain, another login, another source of truth that can disagree with the others.
Features overlap, so teams argue about which tool to use for what, and the same work gets done three different ways.
Data fragments across systems, so nobody can answer a simple question without exporting from four places and reconciling by hand.
The cognitive load of switching between tools quietly taxes every person on the team, all day, every day.
What is actually true
Operational capability comes from coherence, not coverage. A small set of tools that work together beats a large set that each do one thing well. The value of an operation is in how the pieces connect. Not in how capable each piece is alone. The friction that slows teams down is almost never a missing feature. It is the seams between systems. The manual copying, the reconciling, the switching. Every tool you add creates more seams.
The instinct to buy a tool for every problem optimizes each problem locally. It degrades the system as a whole. The best operations are deliberately under-tooled. They choose fewer, better-connected systems. They absorb minor inconveniences rather than buying a new platform every time someone hits friction.
What we see at TTGC
When TTGC is brought in to fix a struggling operation, the most common recommendation is not to add a tool. It is to remove several. Stacks regularly show two platforms doing the same job. A tool bought eighteen months ago sits barely used. The real fix is consolidating onto fewer systems and connecting them properly. Removing a tool is harder than adding one, politically and practically. Someone championed it. Someone learned it. But the audits almost always end the same way. The operation gets faster and calmer. Not because the team got more capability, but because they had less to manage. The goal of a tool stack is not coverage. It is flow.
How to audit your own stack
Before approving the next platform, run the stack you already have through a few honest questions.
Which two tools in this stack have overlapping features, and which one could you drop?
How many tools did you buy to solve a problem that a tool you already own could have handled?
How much of your team's day is spent moving data between systems instead of doing the actual work?
If you could only keep five tools, which would they be - and why are you still paying for the rest?
The honest take
If your operation feels complicated, the answer is almost never another tool. It is fewer tools, better connected. Before you buy the next platform, audit the stack you have. Ask what you could remove. You will usually find more leverage in subtraction than in addition. The goal of a transformation is a coherent operation that flows. Not an impressive collection of software where the whole thing grinds. More tools is not more capability. Past a point, it is just more to manage.
Sources
McKinsey & Company - research on technology sprawl and the hidden cost of fragmented digital tools. mckinsey.com
TTGC - patterns across client transformation work.
Ready to work with Through The Glass Creatives?
Book a free Brand and Growth Assessment and see exactly how Mherie, Ravve, and the TTGC team would approach it.
Related reading: Software Doesn't Fix Broken Processes · More Software Doesn't Mean Better Operations
