Companies rarely buy software because they want more software.
They buy it because something is not working.
Sales follow-up is inconsistent, so they add a CRM. Projects are slipping, so they add project management software. Teams are hard to reach, so they add another communication platform. Leadership cannot see the numbers clearly, so they add dashboards. Documents are scattered, so they add a new knowledge or file-management tool.
Individually, each decision can make sense.
The problem begins when every operational problem is treated as a software problem.
A company can end up with a respectable technology stack and still have leaders manually stitching together what is happening across the business. The CRM knows the opportunity. The project platform knows the task. Finance knows the invoice. HR knows the staffing issue. Email knows the conversation. The meeting notes know the decision.
But who knows what all of that means together?
That is where more software can create less operating clarity.
The Hidden Cost of a Fragmented Technology Stack
The problem is not simply that employees have too many browser tabs open. Fragmentation creates a coordination cost.
Microsoft’s 2023 Work Trend Index, based on a survey of 31,000 people across 31 countries, found that 62% of respondents struggled with spending too much time searching for information during the workday. The same research found that the average employee spent 57% of time in Microsoft 365 communicating through meetings, email, and chat, compared with 43% creating in documents, spreadsheets, and presentations.
That does not mean communication tools are bad. It means the work required to coordinate work can begin consuming the work itself.
Asana’s 2023 Anatomy of Work Global Index reported a similar pattern. In a survey of more than 9,600 knowledge workers across six countries, respondents estimated that 58% of their day was spent on “work about “work”-coordination, communication, searching for information, switching tools, and related administrative activity rather than the skilled work they were hired to perform. Respondents estimated that better processes could save 4.9 hours per week.
The important word there is processes.
When companies experience coordination problems, they often respond by buying another tool. But software does not automatically create a process, clarify ownership, define an escalation path, or decide what leadership should pay attention to.
A new platform may simply become one more place where part of the truth lives. Software is good at storing information. Operating systems create context. Most business software is designed around a specific object.
A CRM revolves around contacts, opportunities, and accounts. A project management tool revolves around projects and tasks. An HR platform revolves around employees, benefits, payroll, or performance. An accounting system revolves around transactions. A communication platform revolves around messages and channels.
That specialization is useful. It is also why no single application automatically gives leadership the operating picture.
An executive usually needs a different set of answers:
- What changed since the last review?
- What is off track?
- Which decision is blocking progress?
- Who owns the next move?
- What are we waiting on?
- Which customer or project has become a risk?
- Which commitment is overdue?
- Which issue needs executive attention, and which one does not?
Those questions cross software categories.
In my own operations work, I have repeatedly seen companies with plenty of technology but no clean place where those questions come together. The problem is not that the tools are incapable. It is that the operating design between the tools is missing.
That distinction matters.
If the information exists but leadership still has to ask three people, check four systems, and sit through a status meeting to understand what is happening, the business may not have a software shortage. It may have a clarity problem.
Context Switching Turns Small Inefficiencies Into Organizational Drag
Fragmented systems also create cognitive costs.
Gloria Mark, a professor of informatics at the University of California, Irvine, has studied digital attention for years. Her research, summarized by UC Irvine in 2023, found that people spend an average of only 47 seconds on a screen before shifting attention elsewhere. Her work has also found that returning fully to a project after an interruption can take up to roughly 25 minutes.
A single software switch may seem trivial. Across an entire day, repeated switching between email, chat, spreadsheets, CRM records, project boards, dashboards, meeting notes, and files becomes something else.
Harvard Business Review has described this broader problem as collaboration overload. Research cited by HBR has found that time spent in collaborative work such as meetings, email, and messaging has risen dramatically over the past decade. In a 2023 article focused specifically on collaboration tools, HBR described workers as navigating a fragmented and often overwhelming collection of technologies that were originally adopted to improve productivity.
This creates a paradox: every tool may be useful on its own, while the combined environment becomes harder to operate.
Before Buying Another Tool, Ask Whether the Problem Is Functionality or Operating Design
This is the most useful question I know for evaluating another software purchase:
Are we missing a capability, or are we missing an operating design?
If your accounting system cannot process multi-currency payments and you now operate internationally, you may genuinely need new functionality.
If your support team needs ticketing and you have no ticketing system, you need software.
If your sales team needs a CRM and customer information is currently living in individual inboxes, a CRM is probably appropriate.
But consider a different situation.
The CRM already exists. Deals are being recorded. The project tool already exists. Tasks are being assigned. Slack or Teams already exists. People are communicating.
Yet new customers are still being handed off poorly after the sale.
Buying another platform may not solve that.
The real questions may be:
- Who owns the handoff?
- What information must be transferred?
- When is the handoff considered complete?
- What must happen before implementation begins?
- Who is accountable if information is missing?
- What reaches leadership?
- What gets escalated, and when?
Those are operating-design questions.
Software can support the answers. It cannot invent the answers for you.
Five Questions to Ask Before Adding Another Software Tool
Before approving another subscription, leaders should pressure-test the problem.
1. What Exact Failure Are We Trying to Fix?
Avoid answers such as “we need better visibility” or “we need more efficiency.” Be specific.
Are client handoffs breaking? Are approvals taking too long? Are managers missing deadlines? Is leadership spending hours collecting status updates? Are customer issues sitting unresolved because ownership is unclear?
If the problem cannot be described operationally, it is difficult to know whether software is the right response.
2. Does the Information Already Exist Somewhere?
Sometimes a company is about to buy a new dashboard even though the underlying information already exists in five current systems.
The real problem is that nobody has designed how those systems should feed the leadership view.
Before creating another source of truth, determine whether you actually need a new source or a better way to connect the sources you already have.
3. Who Owns the Workflow After the Software Is Implemented?
This is one of the most overlooked questions in technology buying.
Software needs an operating owner.
Who makes sure the process is followed? Who handles exceptions? Who decides when the workflow changes? Who monitors adoption? Who is responsible when two departments interpret the process differently?
Without ownership, new tools often reproduce old problems in a cleaner interface.
4. What Decision Will Become Easier Because of This Tool?
Dashboards can display enormous amounts of information without improving a single decision. Ask what leadership will actually do differently.
Will the tool make it easier to decide where capacity should move? Which client needs intervention? Which deal is at risk? Which initiative should be paused? Which vendor requires escalation?
If there is no decision attached to the information, the organization may be adding visibility without adding clarity.
5. What Can We Stop Using If We Add This?
Every new application creates some level of adoption, administration, training, security, integration, and attention cost.
If the answer to every problem is “add one more tool,” software sprawl is almost guaranteed.
A better question is whether the new platform consolidates work, replaces an existing application, removes manual coordination, or materially reduces the number of places employees need to check.
If it does none of those things, its true cost may be higher than the subscription price.
The goal is not fewer tools. It is a clearer operating model.
The Goal Is Not to Eliminate Specialized Software
There is an easy way to take this argument too far: conclude that companies should aggressively reduce their software stacks.
That is not the point.
Modern businesses need specialized systems. A CRM should be good at CRM work. Accounting software should be good at accounting. HR systems should be good at managing employee information. Project tools should be good at coordinating projects.
The goal is not to force every function into one giant application.
The goal is to make sure the business has a clear operating model across those systems.
That means defining:
- which system owns which information,
- who owns each workflow,
- how work moves between functions,
- where decisions are recorded,
- how commitments are tracked,
- what gets escalated,
- and what leadership should be able to see without reconstructing the business manually.
This is the difference between a technology stack and an operating system.
One is a collection of tools.
The other explains how the business runs.
A Practical Test: What Happens When the CEO Asks One Simple Question?
A useful diagnostic is to imagine the CEO asking:
“What needs my attention right now?”
How many steps does it take to answer?
If someone has to check the CRM, message a department head, open a spreadsheet, search email, review a project board, and then schedule a meeting to reconcile the answers, the company may have plenty of technology and very little operating clarity.
The more a company grows, the more expensive that problem becomes.
Growth adds people, customers, vendors, systems, locations, and decisions. Without an intentional operating layer, the founder or executive team often becomes the human integration point between all of them.
That is not a sustainable technology strategy.
Before Buying the Next Tool, Fix the Operating Model
Before buying the next tool, companies should first ask whether the missing piece is software at all.
Sometimes the best technology decision is not adding functionality.
It is designing the operating system that makes the technology already in place easier to use, easier to trust, and easier to act on.
About the Author
Radiance Mack is the founder and CEO of The Mack Standard, where she works on executive operations and operating infrastructure for growing businesses.
Learn more at The Mack Standard.
Research Sources
- Microsoft – 2023 Work Trend Index:
Will AI Fix Work? - Asana – 2023 Anatomy of Work Global Index:
Anatomy of Work Global Index 2023 - Harvard Business Review – Collaborative Overload:
Collaborative Overload - Harvard Business Review – Are Collaboration Tools Overwhelming Your Team?
Are Collaboration Tools Overwhelming Your Team? - University of California, Irvine – Regaining Focus in a World of Digital Distractions:
Regaining Focus in a World of Digital Distractions
