The Cost of Coordination

How much of the workweek disappears before any real work begins?

There is a cost that does not show up on any budget line. It does not appear in a project report or a quarterly review. But it is real, it is significant, and in most organizations it grows quietly year over year.

It is the cost of coordination.

Not the work itself. The work around the work. The handoffs between teams. The approval chains that add days to decisions that should take hours. The status update meetings that exist because no one is quite sure what the other team is doing. The dependencies that turn a straightforward initiative into a months-long negotiation.

Most leaders know this problem exists. Fewer have looked at what it actually costs.

Where the Time Goes

Ask any senior leader how much of their team's week is spent on actual productive work versus coordinating, waiting, updating, and aligning. The honest answers are rarely comfortable.

Research on knowledge work consistently finds that a significant portion of the workweek, often 20 to 40 percent, disappears into coordination activity. Meetings to plan other meetings. Documents reviewed by people whose approval may or may not be required. Work sitting in a queue because a dependency on another team has not resolved.

For most teams, this is background noise. Frustrating, but accepted as the cost of working in a large organization.

It does not have to be.

When Outside Functions Enter the Picture

The coordination problem gets measurably harder when work requires input from functions outside the delivery team. Governance. Risk. Compliance. Security. Legal.

These functions exist for good reasons. No serious organization operates without them. The problem is not that they are involved. The problem is how they are typically brought in.

In most organizations, outside functions are engaged late. Work reaches a review gate after significant effort has already been invested. The governance team flags a concern. The security team identifies a gap. Compliance raises a question that should have been answered three months earlier. The work stops. The team waits. The timeline slips.

What looks like a governance problem or a security problem is often a coordination problem in disguise. The right people were not in the conversation early enough, and the organization pays for it at the end.

The teams that have solved this are not the ones that eliminated oversight. They are the ones that moved oversight earlier. Risk and compliance are part of the conversation from the start, not a gate at the finish line. Security is embedded in the team, not consulted after the fact. Governance is a guardrail that runs alongside the work, not a toll booth that stops it.

The result is not less rigor. It is less rework.

The Real Cost

Coordination overhead is not just a productivity problem. It is a strategic one.

When delivery teams spend a disproportionate share of their time navigating internal processes rather than building, shipping, and solving, the organization moves slower than it should. Good people spend their energy on coordination rather than the work they were hired to do. And because the cost is diffuse, spread across dozens of teams, hundreds of meetings, and thousands of small delays, it rarely gets treated as the serious problem it is.

Consider what happens when a cross-functional initiative requires sign-off from five different functions, each with their own review cycle, their own timelines, and their own definitions of done. A project that should take six weeks takes six months. Not because the work is hard. Because the coordination is.

Now multiply that across every initiative in your portfolio.

AI Will Make This Worse Before It Makes It Better

There is a version of artificial intelligence (AI) adoption that reduces coordination overhead. Faster information retrieval. Automated status updates. Smarter dependency tracking. That version is real and it is coming.

But most organizations will experience a different version first.

AI accelerates output. Teams can produce more, propose more, and move faster on the work itself. What AI does not automatically do is fix the coordination structures those teams operate inside. And when faster-moving teams run into the same slow approval chains, the same late-stage compliance reviews, and the same cross-functional dependencies, the friction does not disappear. It compounds.

More work moving faster into the same bottlenecks means more congestion, not less. An organization that was already struggling with coordination overhead and adds AI without addressing the underlying structure is not solving the problem. It is pressurizing it.

The organizations that will benefit most from AI are not the ones that deploy it fastest. They are the ones that fix their coordination structures first, so AI has somewhere productive to go.

Where It Can Be Reclaimed

The organizations that consistently outperform their peers on speed and delivery are not necessarily better resourced. They are better coordinated. A few patterns show up consistently.

Ownership is clear. Someone is accountable for moving the work forward, which means someone is also accountable for resolving the coordination failures that slow it down.

Outside functions are integrated, not consulted. Governance, risk, compliance, and security are part of the team structure for significant initiatives, not external reviewers called in at the end.

Approvals are designed to be fast. Not because rigor is sacrificed, but because the process is built around decisions rather than documentation. The question is not whether something has been reviewed but whether the right person is empowered to say yes.

Dependencies are visible and managed. Teams know what they are waiting for, who owns it, and when it will be resolved. Blockers are surfaced early, not discovered late.

None of this is complicated in concept. It is hard in practice because it requires changing how functions relate to each other, and that is a leadership problem, not a process problem.

The Question Worth Asking

Before your next major initiative kicks off, it is worth asking: how much of this project's timeline will be work, and how much will be coordination?

If you cannot answer that question confidently, that is the first thing worth fixing.

The cost of coordination is real. It is recoverable. And reclaiming it starts with making it visible.