The Fragmentation Tax: Death by a Thousand Tools

Too many disconnected tools quietly drain productivity, deepen burnout, & stall adoption. Why the durable answer is consolidation onto domain-specific platforms, each one a single coherent surface.

Jul 02, 2026

This is Part 4 of The AI Reckoning: A Future of Trust Series

There is a particular kind of tired that has nothing to do with how hard you worked.

You sat down at nine with one thing you needed to think through. By noon you had answered messages in three places, approved something in a tool you open twice a month and have to relearn every time, moved a task from one board to another because two teams use different systems, and asked an AI assistant a question, then asked a different AI assistant the same question because the first one could not see the document the second one wrote. None of it was hard. All of it required you to stop, reorient, remember where you were, and start again.

At the end of the day you are depleted, and you cannot point to the thing that depleted you. The work was not the problem. The work was the small part of the day that survived everything around it. What exhausted you was the space between the tools. The seams.

We have built a working life made almost entirely of seams.

This is the cost no one is accounting for, and it is the one I want to talk about, because it leads somewhere that matters for anyone building, buying, or betting on the next decade of this industry.

Here is where it leads, stated plainly, so the rest of this is the proof and not the suspense. Human behavior rejects complexity and overload. The cognitive cost of switching between disconnected tools is real, it is larger than almost anyone accounts for, and it is poorly understood precisely because it hides in the gaps where no one is measuring. That single fact makes consolidation inevitable, not as a trend that comes and goes with budgets, but as something the math arrives at on its own. And once consolidation is inevitable, the only question left that matters is what you consolidate onto: something built to serve the people depending on it, or something that quietly comes to own them.

This is also, if you have been following the series, a familiar shape. The first piece described how we deploy technology faster than we understand its second-order consequences, and pay later for the costs that were knowable in advance. Fragmentation is that pattern again. The cognitive load of tool sprawl was knowable. We moved too fast to count it. Now it is surfacing as burnout, as stalled adoption, as budgets that produce exhaustion instead of output. The bill was always coming. We just declined to read it in advance.

The last piece in this series looked at a danger beneath the people building right now: the ground they do not own, the platforms that can shift under them without warning. This piece is about a danger above them. The limit of the very human they are building for. And the rush to ship one more point solution, the same rush that sends builders onto borrowed ground, runs straight into it.

This is part of the same reckoning the series has been tracing, and it has a specific cause. AI has made it extraordinarily easy to see a single pain point and ship something that solves it. What took an engineering organization a year now takes a small team a weekend. That is a genuine wonder, and it is also the engine of the problem. When solving one narrow thing becomes this cheap and this fast, the world fills with narrow solutions, each one excellent, each one more surface for a human to carry. The same capability that makes this the most exciting moment in the history of building is the thing quietly manufacturing the fragmentation we are all starting to feel. The reckoning is not that the tools are bad. It is that nobody priced what it costs to live among all of them at once.

Human behavior rejects complexity and overload.

The cognitive cost of switching between disconnected tools is real, it is larger than almost anyone accounts for, and it is poorly understood precisely because it hides in the gaps where no one is measuring.

If you are reading this nodding, there is a good chance your next thought is about yourself. That you should be more disciplined. Close the tabs, batch the messages, get organized, try harder. Almost everyone reaches for that explanation, and reaching for it is precisely why the real cause stays hidden. So it is worth asking the question directly.

Why Is This Not a Discipline Problem?

It would be easy to file all of this under personal discipline. Close your tabs. Check messages less. Get organized. And there is some truth in that. But the deeper issue is not a habit. It is the architecture of human attention, and it does not bend to willpower the way we wish it would.

When you switch from one task to another, part of your attention stays behind. The psychologist Sophie Leroy named this attention residue: after a switch, your mind keeps processing the thing you just left, and the performance on what you turned to is measurably degraded until the residue clears. The effect is worse when the first task was unfinished, which describes almost every interruption in a normal workday.¹

This is not a small effect at the edges. Researchers tracking knowledge workers have found they switch tasks every few minutes, and that returning to full focus after a real interruption can take as long as twenty-three minutes. Most of the time, the next interruption arrives long before those minutes are up. The result is not a workday with a few costly interruptions in it. It is a workday that never fully assembles a single sustained thought.²

Put a number on the switching itself and it becomes hard to look away from. One analysis of a large workplace dataset found that people toggle between applications and websites on the order of twelve hundred times a day, and lose something like four hours a week purely to reorientation. Four hours lost to finding their focus again.³ A productivity tax quietly waiting for an answer.

AI has made it extraordinarily easy to see a single pain point and ship something that solves it.

What took an engineering organization a year now takes a small team a weekend.

That is a genuine wonder, and it is also the engine of the problem.

Here is the part that matters for where this is going. That cost is not a function of bad tools. Each tool may be excellent. It is a function of the gaps between them, and those gaps multiply with every tool you add. The friction is not in the apps. It is in the human being asked to hold them all together. And the human has a hard limit that no upgrade cycle will raise.

This is why I do not think tool consolidation is a trend that will come and go with budgets. It is a response to something fixed. The number of disconnected surfaces a person can carry has a ceiling, and we have been pretending it does not exist. When a constraint is rooted in human biology rather than market preference, the pressure against it does not ease. It accumulates until something gives.

Consolidation, in other words, is not a preference anyone gets to debate. It is what a fixed human limit produces once enough tools pile up against it.

The Tax the Enterprise Already Pays

Step back from the individual and the same pattern reappears at the scale of the organization, with zeros attached.

Depending on size and how you count, a company runs somewhere between roughly one hundred and several hundred software applications. Studies consistently find that about half of the licenses paid for go unused, and that the average enterprise wastes a sum measured in the millions every year on software nobody opens.⁴

But the license waste, large as it is, is the part that shows up on a spreadsheet. The more expensive cost is the one we just walked through, now multiplied across every employee. The enterprise pays once for the tool, and then pays again, invisibly, for the human friction of running it alongside forty others. The second bill never appears in procurement. It appears in how long things take, in the quality of thinking people have left after navigating the stack, in the errors that creep in at the seams, and in the quiet erosion of the sense that the work is coherent.

Here is the part that should stop a leadership team cold. Most enterprises adopt these tools chasing two specific outcomes: higher productivity and lower burnout. Those are the words on the dashboard, the goals in the deck, the reasons the budget was approved. And past a certain point, each additional point solution delivers the opposite of both. The switching cost eats the productivity gain the tool was bought to create. The fragmentation feeds the burnout the tool was bought to relieve. The organization is, with the best intentions and a straight face, spending money to manufacture the exact problems it is also spending money to solve.

There is a quieter consequence underneath that one, and it is the one that decides whether any of this technology actually gets used. Human adoption follows the path of least resistance. People take up and keep using the things that reduce friction, and they quietly abandon the things that add it, no matter how capable those things are on paper. Every additional disconnected tool raises the resistance, which is why so much purchased software sits unused and so many rollouts stall after the pilot. A platform that absorbs a domain’s fragmentation into one coherent surface does the opposite. It lowers the resistance, and adoption follows almost on its own. This is the link the spreadsheets miss: the same coherence that relieves the cognitive load is also what makes the technology stick. Fragmentation does not just exhaust people. It is the reason the adoption curve flattens.

This is structural rather than incidental. Most organizations know they have overlapping tools. Their own employees say so. And most have still taken no real steps to consolidate, because every redundant application has an internal champion who chose it and a team that has built its habits around it. The pressure to simplify keeps losing to the easier path, which is to add one more thing.⁵

That standoff cannot hold indefinitely, because the human cost compounds while the political cost of consolidating stays roughly fixed. At some point the first overtakes the second. For investors, this is worth sitting with, because it means the pressure toward consolidation is not sentiment. It is arithmetic with a delay on it.

For the enterprise leader, this reframes the decision on the table. The question is no longer which point solution to buy next. Adding one more best-in-class tool to relieve a pain point is, more often than the business case admits, adding to the very load that is suppressing productivity and driving burnout in the first place. The next defensible move is to look for the platform that owns the whole domain. The one that collapses a dozen scattered tools into a single coherent surface, so the switching cost inside that domain simply disappears.

The switching cost eats the productivity gain the tool was bought to create.

The fragmentation feeds the burnout the tool was bought to relieve.

The organization is, with the best intentions and a straight face, spending money to manufacture the exact problems it is also spending money to solve.

This is not a call to herd everything onto one provider. A person may still move across several platforms in a day, and that is fine. What matters is that each one is coherent within its domain, and that the few which need to talk to each other do so through connections intelligent enough to carry context across, so knowledge entered once does not have to be entered again. Fewer surfaces, each one whole, connected in ways that remember. That is the elegant version of consolidation, and it is a different thing from both the fragmentation we have now and the single dependency the last piece warned against.

The Ceiling Builders Do Not See

Now turn to the people making the tools, because this is where the story gets quietly difficult, and where I have the most sympathy.

A great many of the most impressive products being built right now solve one problem beautifully. A single workflow. A single friction. A single moment in someone’s day handled better than anyone handled it before. That is a real achievement, and it is often how important companies begin.

And it is, now, the easy thing to do. This is the part worth being clear about. AI has made catching a single pain point and solving it faster and cheaper than at any moment in history. Building a platform, one interface that holds many problems together coherently, is the opposite of easy. It demands wrestling with complexity that a point solution gets to ignore: how the pieces relate, what happens at the seams, how the whole thing stays trustworthy as it grows. Most builders cannot take that on, and many who could, will not. The reason is simple. We are wired to take the easier path, and that natural inclination is reinforced by a market actively cheering for the quick win. A customer in pain wants relief this quarter, not architecture that pays off in three years. Every incentive points toward the narrow solution. Almost none point toward the hard, slow, integrative work that would actually reduce the load. So the narrow solutions multiply, and the bigger picture goes unbuilt, not because no one can see it, but because seeing it and building it are very different commitments.

A point solution carries a ceiling it did not choose and usually cannot see. However well it solves its problem, it is still one more surface for the human to hold. One more login, one more place to check, one more thing that does not quite talk to the others. Which means a product can be successful on its own terms and still be structurally temporary. As the market becomes more aware of the fragmentation cost, standalone tools increasingly face the same outcome: integration, absorption, or abandonment. Not because they failed, but because the human on the other end ran out of room.

This is the trap closing from two sides at once. From below, the ground the builder stands on: a point solution runs on a platform it does not own, which can reprice, compete, or change the terms whenever its own survival calls for it. From above, the human it is built for, who has no capacity left to carry one more disconnected surface. Exposed beneath and exposed overhead. Same builder, same speed, and most of them, moving as fast as this market rewards, see neither limit until one of them gives.

A point solution carries a ceiling it did not choose and usually cannot see.

However well it solves its problem, it is still one more surface for the human to hold.

One more login, one more place to check, one more thing that does not quite talk to the others.

The builders who internalize this early make a different choice. They stop asking only whether their product solves its problem, and start asking whether it reduces the total weight the person is carrying or adds to it. Those are very different questions, and they lead to very different companies.

Consolidate Onto What

So consolidation is coming. The human mind requires it, the enterprise math rewards it, and the builders who ignore it are constructing ceilings over their own work. On that much I am confident.

The mistake is assuming that consolidation means putting everything in one place. It doesn’t. The answer to fragmentation is not one giant platform that tries to become your entire stack. That simply replaces one problem with another. The cognitive load disappears, but the dependency remains. You have reduced the number of seams only to discover that everything now depends on a single provider whose incentives, pricing, roadmap, and priorities are not yours. We have already explored that risk in this series.

A better answer is domain-level coherence. A process platform should own a process. A data platform should own data. A communication platform should own communication. Each should reduce the fragmentation within its domain so completely that the person using it rarely needs to think about the seams inside it. The goal is not fewer capabilities. The goal is fewer surfaces. The distinction matters. People do not experience work as architecture diagrams. They experience it as attention. Every unnecessary transition, every duplicated workflow, every place where context has to be manually reconstructed is a tax paid in attention.

The platforms that win over the next decade will not be the ones with the most features. They will be the ones that ask the least of the human being using them. That is what fragmentation is creating demand for. Not more tools. Not bigger tools. Coherent ones.

Where the Value Actually Lands

Follow that logic all the way out and an investment thesis emerges; one investors are already beginning to ask about.

If point solutions are structurally temporary, exposed from below by the platforms they rent and from above by the human ceiling, then the durable value in this market does not accrue to them. It accrues to whatever becomes the layer that best serves human behavior. The fragmentation that exhausts the worker and taxes the enterprise is, read correctly, a demand signal. It is the market generating need for platform solutions faster than anyone is building them. Every new point solution shipped makes that need slightly more acute, which is a strange thing to realize: the flood of narrow tools is not the competition for these unified solutions. It is the thing creating demand for them.

People do not experience work as architecture diagrams.

They experience it as attention.

Every unnecessary transition, every duplicated workflow, every place where context has to be manually reconstructed is a tax paid in attention.

What the smartest investors are starting to ask is not which point solution wins its category. Many will win their category and still be absorbed or abandoned, because winning a category is not the same as being something a human can sustainably carry within the context of a full workday.

The question is, who builds the infrastructure layers that reduce the friction of switching across disconnected tabs, and whether they build it as a neutral peer to the large models.

Those are not the same bet, and only one of them is durable, because only one of them does not eventually turn on the people depending on it.

This is the part that does not fit on the current scoreboard. We are measuring point solutions by adoption and revenue, the metrics that look good right up until the human on the other end runs out of room. What we are not yet measuring is which companies reduce the total load and which ones add to it. That distinction, invisible on today’s dashboards, is where the next decade of value quietly sorts itself out.

What We Were Trying to Protect

It is worth remembering what the goal was, underneath all of this. The point of reducing fragmentation was never efficiency for its own sake. Efficiency is what we say to the CFO. What we actually want is to give the person back the sustained attention the seams have been quietly stealing, hour by hour, for years.

The exhaustion I described at the start is not a personal failing and it is not the price of ambition. It is the predictable result of asking human beings to be the integration layer between tools that were never designed to hold together.

We made the person carry the coherence the systems lacked. Of course they are tired. Consolidation will relieve that weight. The only question that matters is whether we consolidate toward something that serves the human or something that comes to own them.

And that is where we’ll go next. Because every AI initiative ultimately arrives in the same place: A person deciding whether to trust what comes next.

What fragments the day is not the work. It is everything we built around it.

Consolidation is not the risk.

Consolidating onto the wrong thing is.

Sheryl Anjanette

Discussion about this post

Ready for more?