Most managers know the feeling: the strategy is clear, the goals have been announced, and people understand what they are supposed to accomplish. Yet the work still moves at half speed.
A decision waits for three approvals. Two departments build separate versions of the same report. A project meeting ends with no named owner. Employees spend Friday afternoon preparing status updates about work they could have finished if they had not been preparing status updates.
This is the coordination tax: the time, attention, and money lost while people organize work instead of completing it. The term gained renewed attention this past week after new workplace research highlighted the gap between understanding company priorities and being able to act on them. In that study, 83 percent of workers said they understood how their roles connected to business goals, but only 51 percent believed their organizations arranged work effectively around those priorities.
That gap matters because it challenges a familiar management assumption. When execution stalls, leaders often assume employees need more direction, motivation, training, or oversight. Sometimes they do. In many cases, though, people already know what matters. They are trapped in a system of handoffs, unclear authority, repeated reporting, scattered information, and meetings that stand in for decisions.
The answer is not to stop coordinating. Shared work requires communication and judgment. The answer is to separate coordination that protects quality from coordination that exists only because no one has cleaned up how work moves.
The Work Is Clear, but the Path Is Not
A company can have a sound strategy and still make ordinary execution painful. Strategy tells people where to go. An operating system tells them how decisions, information, and responsibility move from one person to another.
Many organizations pay close attention to strategy and treat the operating system as administrative housekeeping. That is a mistake. A goal such as “reduce customer response time” means little when service staff need permission from sales, finance, and legal before solving a routine problem. A goal such as “speed up product delivery” collapses when five teams maintain separate project records and no one knows which one controls the schedule.
This is why the coordination tax rarely appears as a line item. It hides in payroll, project delays, overtime, missed opportunities, and employee frustration. The company pays for activity but receives less finished work.
Managers Become the Shock Absorbers
Middle managers often carry the tax personally. They translate broad goals into daily assignments, settle conflicts between functions, explain delays upward, and protect employees from shifting requests. When the organization lacks clear working rules, managers compensate through memory, relationships, and constant follow-up.
Gallup’s 2026 workplace findings show why this burden deserves attention. Global employee engagement fell to 20 percent in 2025, and manager engagement declined more sharply than engagement among individual contributors. Gallup estimated the broader productivity loss from low engagement at about $10 trillion worldwide. Those figures cover more than coordination problems, but they fit what many managers experience: expanding responsibility, limited control, and too little time for coaching or focused work.
A manager who spends the day chasing updates cannot develop people. A manager who must attend every cross-functional meeting cannot think ahead. A manager who acts as the only bridge between departments cannot build a team that operates without constant intervention.
This is not a personal time-management failure. It is a design failure that lands on the manager’s calendar.
Meetings Often Reveal the Problem Rather Than Cause It
It is tempting to blame meetings. Research from Atlassian found that meetings were ineffective 72 percent of the time in its study, and 76 percent of respondents said they felt drained on days filled with meetings. Other workplace surveys have found that managers carry more meeting hours than employees without supervisory duties.
Cutting meetings can help, but meetings are often symptoms. Teams hold another meeting because decision rights are unclear. They invite more people because nobody knows who must be consulted. They schedule status calls because project information cannot be trusted. They repeat discussions because decisions disappear in chat threads and email chains.
A useful meeting should do one of three things: make a decision that cannot be made alone, solve a problem requiring live exchange, or build shared understanding where disagreement matters. Routine updates, document review, and information distribution usually do not require everyone to gather at the same time.
Managers should therefore ask a harder question than “Do we need this meeting?” A better question is, “What failure in our working system created the need for this meeting?” Sometimes the meeting remains necessary. Often it exposes unclear ownership, poor records, or too many approval points.
Approval Chains Grow Long Because Trust Is Vague
Approval systems usually begin with a sensible concern: cost control, legal exposure, brand consistency, safety, or quality. Over time, organizations add reviewers but rarely remove them. The result is a chain in which several people can delay a decision, but no one clearly owns the outcome.
Long approval chains also reveal vague trust. Leaders may say they trust managers while requiring senior review of routine choices. They may ask employees to act like owners while denying them authority over schedules, customer remedies, hiring steps, or modest expenditures.
When authority is clear, speed improves without sacrificing control. When authority is unclear, cautious employees send everything upward. That behavior is rational. People protect themselves when the cost of a wrong decision is visible but the cost of delay is hidden.
Senior leaders can change this by measuring delay as well as error. If every review focuses on mistakes while no one tracks waiting time, the organization teaches people that slowness is safe.
Status Reporting Can Consume the Work It Describes
Managers need visibility. The problem begins when each layer asks for its own version of the same information. A project team updates a task system, prepares a department report, builds slides for an executive meeting, and answers follow-up questions by email. The numbers may differ because each report was created at a different time.
A useful status system should answer a few plain questions: What was promised? What is finished? What is late? What is blocked? Who owns the next action? What decision is needed, and by when?
Anything beyond that should earn its place. Reports should exist because someone uses them to make a decision, not because they appeared on last year’s calendar. Managers can test this by pausing a report for one cycle and seeing who notices. Silence is evidence.
The aim is one reliable record, not perfect software. A shared spreadsheet used consistently beats an expensive platform surrounded by private trackers. Discipline matters more than the tool.
The First Repair Is to Map the Actual Work
Leaders often discuss how work should happen. Employees know how it actually happens. Those are not always the same.
Take one recurring process that causes delay, such as approving a customer contract, hiring an employee, issuing a purchase order, or launching a product change. Follow a real example from start to finish. Record every handoff, wait, approval, revision, and duplicate entry. Note where the work sits idle and why.
Do not begin with a policy manual or an executive flowchart. Begin with the people doing the work. Ask them what they send, what they receive, what they recreate, what they wait for, and what they do when the official process fails.
Once the path is visible, managers can remove steps, combine reviews, set response times, assign ownership, and create a single record. The goal is not a prettier diagram. The goal is fewer places where work can stall unnoticed.
Set Decision Rights Before Asking for Accountability
Managers cannot hold people accountable for outcomes they lack the authority to shape. This sounds obvious, yet companies routinely assign responsibility without decision rights.
A project owner may be responsible for a deadline but unable to secure staff from another department. A service manager may own customer satisfaction but lack the authority to issue a refund. A department head may be judged on cost while senior leaders approve every hiring choice.
For each major responsibility, identify the decision rights that must accompany it. State who decides, who advises, who must be informed, and when escalation is required. Keep the group small. Consultation should improve judgment, not distribute blame.
This also requires restraint from senior leaders. Once authority is assigned, executives must resist reopening routine decisions simply because they would have chosen differently. Intervention should be reserved for decisions outside agreed limits, not matters of personal preference.
Accountability becomes fair when authority, information, and consequences line up.
Protect Time for Work That Requires Thought
Coordination expands to fill the calendar unless managers defend time for concentrated work. Messages, meetings, and small approvals create a sense of motion, but they break attention into pieces.
Research on office interruptions has linked frequent disruptions with higher perceived workload. The practical effect is straightforward: after an interruption, a person must reconstruct what they were thinking. Complex work suffers most because the mental setup takes time.
Managers can protect focus by grouping approvals, setting quiet periods, limiting recurring meetings, and establishing response expectations. Not every message deserves an immediate reply. A team can agree that urgent issues use one channel while routine questions receive answers within a stated window.
Managers must model this behavior. A leader who sends scattered requests all day teaches the team to remain on alert. A leader who gathers questions, provides context, and respects focus time teaches people to finish work.
Measure Flow, Not Busyness
The coordination tax survives because many organizations measure visible activity. Attendance, message volume, hours online, meeting participation, and frequent updates create proof that people are occupied. They do not show whether work is moving.
Managers need measures tied to flow. How long does a request wait before action? How many times is work returned for revision? How many approvals are required? How often do teams duplicate the same information? How much elapsed time passes compared with hands-on work time?
Flow measures should not become another reporting burden. Use data already generated by the work where possible, and examine a small number of indicators tied to a known problem. The purpose is to find friction, not build a surveillance system.
Managers should also watch for one warning sign: employees working late after meeting-heavy days. That often means coordination consumed the hours reserved for production. Overtime may hide the problem for a while, but it transfers the cost from the company’s process to employees’ home lives.
What Senior Leaders Need to Hear
Middle managers can remove waste within their teams, but some problems cross departmental lines or come from above. Senior leaders need an honest picture of the cost.
Do not present the issue as a complaint about bureaucracy. Show a real process, the number of handoffs, the waiting time, the labor involved, and the business result. Compare the cost of delay with the risk the controls were meant to manage.
A contract review that takes twelve days may include only three hours of actual review. A weekly report may consume eighty staff hours and lead to no recorded decision. A product launch may slip because three groups maintain different schedules. Concrete examples are harder to dismiss than general frustration.
Then ask for a specific change: one fewer approval, one named decision owner, one shared record, a response deadline, or a trial period with reduced reporting. Small operating changes can prove the case and build support for broader reform.
Senior leaders also need to hear when managers themselves are overloaded. A company cannot ask managers to coach employees, lead change, manage risk, improve performance, and coordinate across functions while filling most of their calendars with internal traffic. Something has to be removed.
Conclusion
The coordination tax is not the price of teamwork. It is the price of teamwork arranged poorly.
Some coordination protects customers, safety, legal compliance, and sound judgment. Keep it. The rest deserves inspection. Repeated updates, unclear ownership, overlapping tools, routine escalations, and meetings without decisions consume time that no strategy can recover.
Middle managers are in the best position to see the problem because they live where plans meet daily work. They can identify the handoffs, delays, and reporting loops that senior leaders rarely encounter. They can also begin repairs by mapping one process, clarifying one set of decision rights, removing one unused report, and protecting blocks of focused time.
The work will not become frictionless, nor should it. Good organizations pause when the stakes require care. But they do not confuse waiting with discipline, attendance with contribution, or reporting with progress.
When people understand the goal yet still cannot move, more motivation is not the answer. Clear the path.