Tool Sprawl Fragments the Truth

An inventory at a large IT organization found more than two hundred tools, parallel systems for the same work, and licenses almost nobody used. The cost that mattered most was that no one held a complete picture of the work.

07 SIGNAL
The condition

Four systems each held a slice of the same work, none of them talked to the others, and no one could see the whole.

Layered on top of whatever was already there

Early in the diagnostic, the sponsor described her organization's technology in terms most leaders would recognize. The company was always in some kind of transformation, always adopting the latest tool and layering it on top of what already existed, and nothing connected the way it should. It was the most concentrated version of a problem we see almost everywhere.

Tool sprawl usually gets described as an efficiency problem. The larger damage is to the truth. When individuals, teams, departments, and regions run different tools, the data rarely integrates, and no one holds a complete version of what is being worked on or what is coming next. Executives who cannot see the full picture ask managers and staff to build slide decks explaining progress against commitments. The decks take real time to build, the data in them goes stale quickly, and decisions get made on it anyway.

One request, four possible doors

The member of the client's working team who led the tools research opened his findings bluntly. The work tracking system was in bad shape, and fixing it would take real effort. Incidents and service requests lived in one system. Enhancement requests lived in a second. Project and portfolio work lived in a third. The delivery teams' backlog lived in a fourth. None of them talked to the others. Work submitted in one was invisible in the rest, and a request entering the organization could land in any of the four with no view that pulled them together.

The sponsor was not surprised. The fragmentation had existed for years. What changed was that it was now a finding on the table rather than a frustration people felt and worked around.

Figure 1
Four systems, four slices of the work
SystemWhat it heldConnected to others
System oneIncidents and service requestsNo
System twoEnhancement requestsNo
System threeProject and portfolio workNo
System fourDelivery team backlogNo
Each system held part of the work and none could see the others. A request could arrive in any of the four, and no view put them together.

More than two hundred tools on one page

The first question is simply what tools are in use, and the answer is rarely written down anywhere at the start. The list has to be built, and building it is part of the value, because it forces the organization to look at the whole landscape instead of the slice any one leader has been responsible for. After two weeks the inventory went up on the screen. The IT organization and the business units it supported were running more than two hundred tools. Many had arrived with acquisitions and were never retired. Some were used by two or three people. Several had not been opened by anyone in months and were still being paid for.

Sorting the inventory by capability made the duplication obvious. Three project management tools were in use across business units, each chosen because of what a group had used before rather than any organizational standard. Two enterprise-wide license agreements covered tools that fewer than fifteen people used. Those two licenses alone cost more than one hundred thousand dollars a year.

Figure 2
What the inventory showed
200+tools in useAcross IT and the business units it served
3project management toolsRunning in parallel across business units
$100K+a year for two licensesUsed by fewer than fifteen people
One inventory, built over two weeks, put a number on what leaders had been paying for without seeing it.

The same pattern at a smaller scale

Size does not protect an organization from this. At a much smaller firm of roughly seventy people, the same exercise surfaced more than one hundred active tools, over double the forty to fifty we would expect at that size. For an organization that small, the cost of paying for, administering, and training people across that many tools is significant, and much of it stays hidden because leaders do not know about the redundancy or the unused licenses. Seeing it on one page changes the conversation.

Back at the larger organization, the team asked how much expertise people had in each tool, how much value they got from it, how people were brought on and off it, where data was still stitched together by hand, and who owned each tool at all. Ownership matters more than it looks. Without a named owner, nobody is responsible for asking whether a tool still earns its place or whether the license count matches the people using it, and costs drift upward like a gym membership nobody uses.

When the synthesis was complete, the sponsor was looking at her landscape in a way she had not been able to before: more than two hundred tools, three project management platforms and three communication platforms running in parallel, two enterprise licenses almost nobody used, thin training on the tools people did use, and a work tracking system split across four databases. She said this was what she had been managing without ever seeing it as a whole. She had known there was a tooling problem. She had not known how extensive it was.

Figure 3
Active tools at a firm of about 70 people
Typical for that size 40 to 50
Actually in use 100+
The smaller firm ran more than twice the number of tools we would expect for its size. Most of that cost was invisible until the list existed.
Colleagues sorting printed lists and charts spread across a shared table.

Deciding from evidence instead of guessing

The inventory turned tool decisions into a structured choice. In a workshop, participants used one color of sticky note to mark opportunities to remove redundancy, another for tools that could be retired, another for their replacements, and a fourth for other improvements. Then they sorted every candidate by how hard it would be to change. Ready to change meant low risk, clear ownership, and manageable impact. Possible to change meant more risk and real coordination. Unrealistic to change meant critical dependencies or regulatory and contract constraints. The result was a visible, ordered picture of where the landscape could start to move.

The changes that followed were concrete. At the smaller firm, interviews showed there was no onboarding that covered the tech stack. HR and operations built one that did, and managers now get a notification when someone leaves so licenses can be transferred or canceled. At a global consumer goods enterprise where regions had made their own tooling investments, regional and global leaders put every current technology initiative in view at once, saw where regional solutions were undermining global ones, and consolidated efforts to cut redundant and unnecessary spending.

Neither change depended on one tool for everything. Both depended on the organization treating its tools as part of how work is designed rather than a pile of separate purchases. The tooling landscape can be reshaped faster than almost any other part of the system, but only after someone has looked at all of it. Without that picture, every tool investment is a guess about the next move. With it, leaders can decide what to keep, consolidate, retire, or invest in on evidence, and start building toward one version of the work they can trust.

Technology should express the operating model. It cannot substitute for one.

Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Not sure where to start?

Answer five questions about where work stalls. We send back a starting plan: where to begin and what to look at first.