The coordination tax: most knowledge work exists to transfer context between humans
60 to 70 percent of knowledge work hours are coordination: meetings, translation artifacts, state synchronization, handoff management. PRDs exist because the engineer isn’t the person who talked to the customer. Sprint planning exists because eight engineers need to avoid stepping on each other’s work. Design handoffs exist because the developer needs intent transferred into implementable form. None of these artifacts is the product — they’re bridges between humans who can’t share a brain.
We don’t see this because we’ve categorized the overhead as “the role.” A PM’s job is writing PRDs and running standups. An EM’s job is sprint ceremonies and dependency management. But the value was always the working software, the shipped product, the revenue. Everything between “we understand what to build” and “the thing exists” is process — and process exists because the execution layer is made of humans.
What happens when AI compresses coordination
When agents handle execution directly, the translation layers between humans get deleted — not just the coding tasks. No PRD needed because the person with customer insight works directly with the agent. No sprint planning because there aren’t eight engineers who need to coordinate. No status meeting because the state is the commit history. 2025-12-04_01-09_ai-automation-shifts-human-work-toward-strategy-workflow-design-and-exception-handling AI automation shifts human work toward strategy, workflow design, and exception handling.
This creates a compounding loop: fewer humans → less coordination → work expressed as code → more verifiable → agents handle more → fewer humans still. Each turn accelerates the next, making standard forecasts 2-3x too conservative.
The real residual
What survives when coordination evaporates is the hardest 15-20% — zero-to-one product vision, genuine care in relationships, engineering architecture bets, and the emerging discipline of agentic systems design: building, tuning, and evolving the agent harnesses themselves. 1.1.1 My job is thinking, then AI executes in the system I build. The compound engineering loop is exactly this discipline.
The coordination tax didn’t just waste time. It suppressed the highest-value work that humans do. Removing it concentrates human effort on the work that was always the most important — the work we were always too busy coordinating to do properly.
What makes this personally relevant
The two qualities that separate people who catch this wave: agency (stubborn confidence the gap is closeable) and ramp (ability to learn quickly without permission or roadmap). Both are about posture, not credentials. 2026-01-10_10-10_composability-contracts-for-ai-workflows Composability contracts for AI workflows are one way to make agent-delegated work verifiable — expanding the frontier of what coordination overhead can be safely removed.