What I learned leading a transformation with fewer tools, not more

When I joined a major retail digital transformation project as a senior specialist with a consulting firm, the first meeting went exactly as I expected: “We need more tools.” Every discussion about efficiency seemed to end with another vendor demo or platform suggestion — a new SaaS for workflow, a chatbot for customer service, an AI dashboard for analytics.

It’s a reflex many organizations have developed. Digital transformation has become synonymous with tool adoption and executives often measure progress by the number of technologies purchased. But as I listened to the project sponsors enthusiastically list the “missing systems,” one question came to mind: Were we transforming the business or simply expanding the toolbox?

I had seen this pattern before — a well-intentioned accumulation of platforms that ultimately increased complexity rather than capability. So I proposed something that sounded contrarian at the time: Instead of adding more, let’s first see what we can remove.

The suggestion earned a few surprised looks, but that conversation became the turning point of one of the most effective transformation programs I’ve been part of.

The hidden cost of tool sprawl

In the modern enterprise, tool sprawl is a quiet but costly epidemic. Across industries, organizations accumulate overlapping software faster than they can integrate it, creating confusion, duplicating data and raising subscription costs.

The retail client I supported was no exception. Over time, every department had picked its own favorites — project management boards here, customer feedback tools there and a half-dozen collaboration apps in between.

During my first month, I conducted an audit of the digital ecosystem. The result was startling: 142 separate applications in active use across the organization, with more than a dozen dedicated to collaboration alone. Some departments used three tools to manage the same process, creating duplicate records and confusion about ownership.

In one workshop, a team leader joked that “finding the right file is harder than finding a new employee.” It was meant humorously, but it captured the frustration perfectly. Instead of driving productivity, technology was slowing people down.

Leaders often try to fix this kind of chaos by layering on new software. But as Harvard Business Review notes, more tools don’t automatically equal more productivity — they often amplify the noise.

Choosing subtraction over addition

I started with two simple questions:

1. What tools do people actually use every day?
2. What measurable value does each tool provide?

Those questions changed the conversation. Instead of “what’s missing?” we began asking “what’s working?”

We hosted a series of discovery sessions where employees anonymously rated the tools they used by usefulness and ease of adoption. The results were eye-opening. Nearly 40% of tools had fewer than 15% active users. Some were bought for pilot programs that never scaled; others replicated capabilities already available in enterprise systems.

For example, three departments paid for separate survey tools even though their CRM could already handle feedback collection. Another analytics platform generated reports nearly identical to what finance could produce internally.

When I presented the findings, one executive asked, “So you’re saying we could cut a third of our software and no one would notice?”

I replied, “You might notice — in a good way.”

That comment led to our first pilot consolidation: collaboration and analytics, the two most fragmented areas. The pushback came not from IT, but from end-users attached to their preferred systems. We countered that by focusing on the user experience. We showed how simplification would mean fewer logins, consistent data and faster response times. Slowly, the idea gained traction.

Streamlining the stack

Our first step was to standardize the collaboration environment. We reduced 13 communication platforms down to four, implemented single sign-on and integrated the approved tools with the company’s intranet. Teams no longer had to jump between chat windows, task trackers and document portals to find information.

Next, we rationalized analytics and reporting. Instead of maintaining multiple dashboards across BI tools, we centralized key metrics into one unified view. We created a data-governance checklist and automated report scheduling to eliminate manual reconciliation.

The process took about five months, but the results were immediate and measurable:

• 25% reduction in software licensing costs within the first year.
• 38% increase in active usage across remaining tools.
• Simplified security posture, reducing the number of vendor integrations by half.
• Improved employee satisfaction scores, especially among frontline retail managers who no longer needed to toggle between systems.

One of my favorite moments came a few months later when a department head told me, “I can finally find what I need without calling three people.” That’s when I knew simplification had worked.

Research supports this experience. According to Reworked.co, employees forced to juggle multiple collaboration tools lose up to an hour of productive time per day. Our data lined up almost exactly with that estimate.

Lessons from a less-is-more approach

Looking back, what surprised me most wasn’t how much we saved, but how much clarity we gained. Simplification forced alignment. Once redundant tools disappeared, teams began to talk more — not through software, but through collaboration. Decisions became faster because everyone used the same data and systems.

One executive commented that it felt as if “the fog had lifted.” They weren’t just working with fewer tools — they were working with purpose.

The hardest part of the project wasn’t technical execution. It was changing the perception that transformation equals accumulation. For years, digital maturity was measured by how many tools an organization deployed. But as Harvard Business Review points out, tools don’t create productivity — people and processes do. Our experience mirrored that insight exactly.

Here’s what I learned:

• Simplification enables innovation. You can’t innovate when your foundation is unstable. Consolidation frees up both mental and operational capacity.
• Tool governance matters. Every new platform should justify its existence — what value does it add beyond what’s already in place?
• Culture drives adoption. Removing tools can feel threatening unless employees understand the why. Transparent communication makes all the difference.

Digital transformation isn’t a race to deploy more technology. It’s a discipline of ensuring the right technology delivers consistent value.

Building for the long term

After the consolidation phase, the client’s IT roadmap looked dramatically different. Instead of dozens of disconnected platforms, they invested in optimizing integrations, training and analytics literacy. By strengthening the foundation first, they could later introduce new technologies — AI forecasting, advanced personalization and process automation — with confidence that the systems underneath would support them.

That’s a crucial shift many organizations overlook. As tempting as it is to chase the next big tool, real transformation comes from improving how people and processes work together.

A year later, when I reconnected with the client’s CIO, she told me, “Our best decision wasn’t the AI tool we added. It was everything we removed before it.”

That’s the paradox of transformation: progress sometimes starts by taking things away.

[Note: The views expressed in this article are my own and do not represent the views of Deloitte or its clients.]

This article is published as part of the Foundry Expert Contributor Network.
Want to join?