
Tool proliferation starts with a simple question: how many collaboration tools does your organisation currently use?
If you work in a mid-sized enterprise, the answer is probably close to a hundred. The average company ran 106 SaaS applications in 2024, down slightly from 112 the year before. Individual employees switch between roughly thirteen different tools a day, and across the same organisations, sixty percent of knowledge worker time is consumed by what Asana calls “work about work,” chasing updates, switching applications, sitting in status meetings, and searching for information that should be findable in seconds.
More tools. Less clarity.
The Tool Proliferation Trap
The logic that leads to tool proliferation is seductive. A team has a problem. Someone finds a tool that solves it. The tool gets adopted. Six months later, a different team has a slightly different version of the same problem, finds a different tool, and adds it to the stack. Multiply that across departments, geographies, and years of hybrid-work experimentation, and you arrive at the mess most programme leaders are now trying to manage.
Gartner gave a version of this phenomenon a name: collaboration drag. Their survey of marketing leaders and the other functions they work with found 84% report experiencing high collaboration drag when working across functions, and organisations with high collaboration drag are 37% less likely to achieve their revenue and profit goals. The finding is scoped to marketing specifically, but the mechanism it describes, too many meetings, too much feedback, unclear decision-making authority, is not unique to marketing. It is the same failure mode showing up everywhere tools multiply faster than agreements do.
The problem is not that the tools are bad. Many of them are genuinely excellent. The problem is that organisations keep adopting solutions before diagnosing the actual fault.
What the Tool Conceals
When a team cannot collaborate effectively, the instinct is to look at infrastructure. The meeting cadence is wrong. The documentation is scattered. Nobody knows who owns what. So a new tool gets procured, onboarded, and rolled out with a training session and a communications plan. Six months later, the same problems exist, but they are now distributed across an additional platform.
What the tool purchase never addresses is the underlying communication breakdown: unclear accountability structures, governance that was never designed for distributed teams, leaders who model the old behaviours while mandating the new platform, and a cultural assumption that visibility equals productivity.
The tool inherits that dysfunction. It was never built to fix it.
This matters most for programme leaders and transformation professionals, because they are the ones asked to demonstrate value from technology investment. When adoption stalls or collaboration metrics do not improve, the tool gets blamed. Procurement cycles begin again. The stack grows heavier and the underlying dysfunction remains invisible.
The Governance Gap
This points to a governance failure, not a procurement one.
Effective collaboration at scale requires decisions that tools cannot make: who communicates what, through which channel, at what point in a workflow. It requires norms that are agreed, modelled from the top, and reinforced over time. It requires leaders who understand that a collaboration platform is a surface, not a strategy.
The organisations that get this right do not have fewer problems. They have clearer agreements about how work moves between people. The tool becomes the infrastructure for those agreements, not a substitute for them.
What Good Looks Like
The most coherent digital workplaces share a few characteristics that have nothing to do with the tools themselves.
First, they have explicit communication governance: decisions about which platform serves which purpose, enforced consistently. Not guidelines buried in an intranet page, actual operating norms that leaders visibly follow.
Second, they have resisted the temptation to solve behavioural problems with technical features. When a team is not communicating well, the answer is not a new notification setting or integration. The answer is a conversation about how that team wants to work.
Third, they regularly audit and retire. Not just tools, habits, meetings, and processes. The question is not “what should we add?” but “what is creating friction and why?”
The Honest Conversation
The collaboration tool industry will continue producing impressive products. AI-driven workflow assistants, context-aware communication, integrated digital workspaces, the roadmaps are genuinely compelling. But none of it matters if the organisation adopting it has not first asked the harder questions.
Why do people switch between thirteen tools in a day? Because the information architecture is fragmented. Why is it fragmented? Because nobody owns the decision about where work lives. Why does nobody own that decision? Because governance was never built for the way teams actually operate.
Fix that, and most tools will work fine. Leave it unaddressed, and the next platform will fail in exactly the same way as the last one.
The tool is never the solution. It is a test of whether the solution already exists.


