Your organization has never had more tools. More channels, more platforms, more dashboards, with AI layered on top of all of it. Global IT spending is on track to hit $6.15 trillion in 2026, up 10.8% since 2025. The average enterprise runs 275 SaaS applications and spends $49 million a year on software.
And yet the share of projects that actually meet their original goals has barely moved; workplace productivity is more or less flat. A decade of dramatic investment in how work gets done, and the outcomes look almost identical to where they started.
You likely know the feeling: You’re sitting in a meeting talking about what you talked about last meeting. Familiarity creeps in and finally you find yourself asking, "wait–didn’t we talk about this two weeks ago? I thought we already decided?" People in the meeting nod along, and someone explains they wanted to re-confirm before they move ahead on the project.
So what gives?
What’s really dragging down workplace productivity
Here’s what the data is actually telling us.
The constraint in enterprise performance isn’t speed: Information moves in real time. It’s not investment: Software budgets are at historic highs. And it’s not access: Our teams have more tools than any prior generation of workers.
The constraint is continuity, and whether the decisions your organization makes (and the reasoning behind them) survive the journey across teams, handoffs, and time.
There’s a name for what happens when they don’t: the Alignment Tax.
The Alignment Tax is what your organization spends in time, decisions, and dollars to rebuild a shared understanding that nothing in your system preserved. It’s not a line item; no one budgets for it. But every organization pays it in forms that feel frustratingly familiar:
-
Meetings held to re-establish what attendees already agreed on the week before
-
Handoffs where the receiving team gets deliverables but is left to rebuild the context that led to those deliverables
-
New hires who spend their first month piecing together context from fragmented sources because there’s no single source of truth
-
Senior leaders who can’t delegate because the reasoning behind decisions only lives in their head
-
Projects that stall because the the person who held all the rationale is off sick or on vacation
Individually and in the moment, none of these feel like crises. They might even feel normal if your organization has been absorbing the cost and working around it for years.
A tax you can calculate
Knowledge workers lose an average of 7.47 hours per week to miscommunication: rewriting, clarifying, redoing, resolving. That’s around a full workday, every week, for every person in your organization, spent recovering from broken understanding rather than advancing work.
Translate that to headcount:
-
500 employees: 3,735 hours lost per week
-
5,000 employees: equivalent to more than 900 full-time employees doing nothing but rebuilding context that already exists
-
50,000 employees: 373,500 hours per week, or approximately 9,338 FTEs
In dollar terms, the Alignment Tax costs organizations roughly $12,506 per employee, per year. For a company of 500, that works out to about $6.2 million annually. That number for a 5,000-person company is 10x bigger at $62.5 million annually.
No board would ever sign off on that number to get flushed down the toilet. It just quiety accumulates quarter after quarter.
Six signs your organization has a continuity problem
There’s no Alignment Tax at the bottom of each purchase order, invoice or contract. It shows up in the patterns you’ve learned to live with. See how many of these feel familiar:
-
Decisions keep getting revisited. The decision was made, everyone agreed. Three weeks later, the same question is back on the agenda with a different group, starting from zero.
-
Teams ask for context that already exists. It exists, but it lives somewhere in a disjointed system: in a document, a Slack thread, a shared drive, comments in an app or platform your team relies on for project management. The person who needs it either can’t find it, or they can but they can’t tell if it’s current.
-
Coordination meetings keep multiplying. Monthly check-ins become weekly because alignment keeps degrading between sessions. The calendar fills with recovery, and the actual work gets whatever time is left.
-
Handoffs strip the reasoning out. Deliverables transfer along with documentation, but the decisions, tradeoffs, and constraints that shaped all of it don’t travel with them. The receiving team inherits the output and has to reverse-engineer the thinking as soon as something’s unclear.
-
The documentation exists but doesn’t carry enough to act on. Everyone’s looking at the same record and drawing different conclusions. The gap between what’s written and what it takes to act on it has to be bridged by a human being, in real time, every time.
-
Post-mortems keep resurfacing the same root causes. Rework, miscommunication, unclear handoffs. Your lessons-learned archive from this year reads the same as it did two years ago.
If more than two of these feel familiar, your organization may have a continuity problem. This is a structural condition: an environment where shared understanding degrades faster than your organization can rebuild it.
Continuity is the next operating discipline
There’s a pattern in how enterprises adopt new disciplines. Quality started as a nice-to-have. Then it became a competitive differentiator. Then it became table stakes: infrastructure that every serious organization builds into how it operates.
Security followed the same arc, and so did compliance. Accessibility is in the middle stages of this pattern, too.
Continuity is on the same trajectory. The organizations beginning to close the performance gap are the ones that have started treating the preservation of decisions and shared understanding as infrastructure instead of overhead. They capture the "why" behind decisions with the same rigor as they capture decisions themselves. They design handoffs to transfer context, not just deliverables. They measure whether alignment persists after the meeting ends, not just whether it was achieved in the room.
You don’t have to replace all the tools you have. Project management systems, document repositories and communication platforms still do what they’re designed to do. What they weren’t built to do is carry organizational memory where continuity currently breaks.
That’s the gap. And it’s the gap that compounds the Alignment Tax from daily friction to multi-million dollar productivity loss.
The cost of waiting
Every quarter an organization operates without continuity infrastructure, the losses recur. The 7.47 hours per week in lost time doesn’t reappear, the $12,506 per employee doesn’t get credited back to your budget. And the forces driving coordination complexity—more stakeholders per decision, more tools, more distributed teams, faster project cycles—show no sign of reversing.
The fact that the cost is distributed across the workforce makes it easy to defer. No single project failure is large enough to force a structural response; it shows up as slightly compressed margins, slightly longer timelines, slightly higher turnover among the people who carry the most context. The signals are small enough to explain away individually. Together, they represent an organization working harder than it needs to in order to achieve the same results.
The organizations that build for continuity now will compound advantage with every project cycle. The ones that wait will continue paying the tax, increasingly at a rate set by the competitors who stopped paying it first.
Continuity is the new productivity
Discover how innovative companies are using continuity as the lever to actually drive productivity gains.
