You hired to go faster. Two new people in operations, one more in finance, a couple in the project teams. Six months later the work is not moving faster - it is moving slower, and everyone is busier than ever. The calendar is a wall of meetings. Decisions that used to take a morning now take a week. And nobody can quite say who owns the thing that slipped.
This is not a people problem, and it is not a motivation problem. It is a maths problem. Every person you add creates new links that have to be kept in sync, and the number of those links grows faster than the number of people. Past a certain point, each hire buys you a little more output and a lot more overhead. Economists and engineers have a name for the overhead. Call it the coordination tax.
This piece is for the founder, COO, or team lead who feels the drag and is about to reach for the obvious lever - hire more people - without realising that lever is part of the problem. We will show where the tax comes from, why it compounds, why the usual fixes fail, and what actually breaks the pattern: leverage, not headcount.
TL;DR
The coordination tax is the compounding cost of keeping people aligned - meetings, handoffs, approvals, and “who owns this?” - and it is not the productive work.
It grows faster than headcount because communication links scale roughly with the square of team size. A team of 5 has 10 links; a team of 50 has 1,225.
The bill is already huge: workers spend about 60 percent of the day communicating, are interrupted every two minutes, and companies lose more than 20 percent of capacity to organizational drag.
Hiring makes it worse first, because a new person draws information and time from the exact people who were already the bottleneck.
The escape is leverage: AI employees on top of a Company Brain absorb the routine coordination, so each existing person keeps doing their real work - more output without more headcount.
What the Coordination Tax Actually Is
Every company runs on two kinds of work. There is the real work - the thing the customer pays for, the part that creates value. And there is the work of keeping the people who do the real work aligned with each other. That second category is the coordination tax, and most companies never put a number on it even though it consumes a large and growing share of the day.
- Coordination is not the value - The customer does not pay for your Tuesday alignment meeting. They pay for the product that ships. Coordination is the overhead required to make the product ship when more than one person is involved.
- It hides inside useful-looking activity - Nobody books a calendar slot called “waste”. The tax lives in status updates, handoff emails, cross-team reviews, and re-explaining context. Each one feels reasonable. The sum is a full day a week.
- It is a tax, not a purchase - You do not choose to pay it item by item. It is levied automatically on every unit of real work the moment that work has to pass between people.
- It is invisible on the org chart - The org chart shows boxes and reporting lines. It does not show the hundreds of informal links along which requests, questions, and approvals actually travel.
- It compounds silently - Because no single meeting or message looks like the culprit, the tax can double while every individual decision that created it looked sensible.
Key Data Point
Microsoft’s 2025 Work Trend Index, based on 31,000 knowledge workers across 31 markets, found that people spend roughly 60 percent of their time on communication - meetings, email, and chat - leaving only about 40 percent for the creative and analytical work that actually produces output7. The coordination tax is not an edge case. For most knowledge workers, it is the majority of the day.
The German management literature has a precise term for one part of this - Abstimmungskosten, the cost of aligning and integrating the activities of multiple actors17. The broader concept, Koordinationskosten or coordination cost, is one of the oldest ideas in the economics of the firm. What is new is how large it has grown in modern knowledge work, and how badly it scales as companies add people.
“Adding manpower to a late software project makes it later.”
- Frederick P. Brooks Jr., author of The Mythical Man-Month1
Brooks was writing about software in 1975, but the mechanism is universal. He observed that a new person needs information before they can contribute, and that information comes from the people already busy. The newcomer asks a blizzard of questions, which slows the very people who were the bottleneck. The same dynamic plays out in finance, operations, service, and sales the moment a team gets big enough to need constant alignment.
Why the Tax Grows Faster Than Your Headcount
The reason adding people backfires is not psychology. It is combinatorics. When you add a person, you do not add one relationship - you add a relationship with everyone already there. The number of possible one-to-one links in a team of n people is n(n-1)/2, which grows with the square of the team, while headcount grows in a straight line3.
| Team Size | One-to-One Links | Links Added by the Last Hire | Links per Person |
|---|---|---|---|
| 5 people | 10 | 4 | 2.0 |
| 10 people | 45 | 9 | 4.5 |
| 20 people | 190 | 19 | 9.5 |
| 50 people | 1,225 | 49 | 24.5 |
| 100 people | 4,950 | 99 | 49.5 |
Read the last column carefully. Going from 5 to 100 people multiplies headcount by 20, but multiplies the coordination links per person by more than 12. You are not just bigger. Every single person now sits at the centre of far more connections that need maintaining. That is why the tax rises as a share of each hire the larger you get.
The three forces stacked on top of the maths
- Ramp time - A new hire is a net consumer of attention for weeks or months. They pull answers, context, and review time from the people already at capacity before they return any.
- Partitioning limits - Some work simply cannot be split. Nine women cannot make a baby in one month, as the old line goes. When work is sequential or deeply interdependent, extra hands mostly add communication, not throughput.
- Diffusion of ownership - The more people who could own something, the more likely nobody clearly does. Bystander effects that are harmless in a crowd become expensive in a company: the task waits while everyone assumes someone else has it.
The Bain Number
Bain & Company’s research on organizational drag - the structures and processes that consume time without producing output - estimates that the average company loses more than 20 percent of its productive capacity to it, the equivalent of more than one full day per person per week. The best-run companies cut that loss roughly in half4.
“The average company loses more than 20 percent of its productive capacity - more than a day each week - to organizational drag: all the practices, procedures, and structures that waste time and limit output.”
- Michael C. Mankins, Partner at Bain & Company and co-author of Time, Talent, Energy4
The most uncomfortable implication is about scale. As companies grow, complexity tends to grow faster than the value that complexity produces. That is the mechanism behind a pattern many operators feel but rarely name: profit per employee often falls as headcount rises, because each new person adds coordination cost faster than they add output5.
Where the Coordination Tax Actually Shows Up
The tax is abstract until you see the line items. It arrives disguised as normal work, which is exactly why leaders rarely target it. Here is where the money goes, with the evidence for each.
1. Meetings that multiply
- Ad hoc everything - Microsoft found 57 percent of meetings are now ad hoc calls with no calendar invite, and 1 in 10 scheduled meetings is booked at the last minute7. Alignment that used to happen in passing now becomes a scheduled interruption.
- Meetings breed meetings - The larger the group, the more pre-meetings, syncs, and scrum-of-scrums appear just to prepare for the real meeting. A chessboard calendar of coordination is the visible symptom of the tax3.
- Little gets resolved - A study for the Hans-Boeckler-Stiftung found many organisations treat meetings as the cure for every coordination question, yet only a fraction of participants can genuinely focus on the content15.
2. Interruptions that shred focus
- Every two minutes - Microsoft found knowledge workers are interrupted by a meeting, email, or notification roughly every two minutes during core hours - about 275 interruptions a day7.
- The recovery cost - Research popularised through the Anatomy of Work index puts the time to fully regain focus after a significant interruption at around 23 minutes10. Interruptions do not just cost their own length; they cost the runway to get back.
- The infinite workday - When focused work cannot happen during the day, it migrates to the edges. Microsoft found after-hours meetings up 16 percent year over year and a meaningful share of workers back in the inbox at 10 pm7.
3. Handoffs and tool-switching
- Constant toggling - Harvard Business Research found employees toggle between applications more than 1,200 times a day - roughly once every 24 seconds of active work9.
- App sprawl - The average worker moves between about nine applications to get their job done, and every switch carries a re-orientation cost10.
- Message volume - The average worker receives 117 emails and 153 Teams messages per weekday7. Much of it is coordination: where is this, who approved that, can you confirm.
4. The “who owns this?” tax
- Diffuse responsibility - The German operations literature describes how unclear responsibilities and missing decision rules force permanent feedback loops through meetings and status mails, turning knowledge work into coordination work16.
- Escalation as a habit - When ownership is unclear, the default is to escalate. The decision climbs the hierarchy, consuming senior time and adding days of delay for a call someone closer could have made.
- Rework from misalignment - Two people build against different assumptions because the coordination link between them was weak, and the work has to be redone. Rework is the coordination tax paid twice.
| Symptom | What It Really Is | Evidence |
|---|---|---|
| 60% of the day in comms | Coordination crowding out real work | Microsoft 20257 |
| 275 interruptions/day | Focus destroyed by alignment pings | Microsoft 20257 |
| 1,200+ app switches/day | Manual handoffs between systems | HBR9 |
| >20% capacity lost | Organizational drag | Bain4 |
| 57% of meetings ad hoc | Unplanned coordination interruptions | Microsoft 20257 |
None of these line items looks like waste on its own. That is the trap. The coordination tax is death by a thousand reasonable meetings, and you cannot cut it by asking people to have fewer good intentions.
Feeling the coordination tax in your own team?
Book a 30-minute call. We will map where your routine coordination goes and what an AI employee could absorb.
The Second Tax: Coordination Knowledge Lives in People’s Heads
There is a deeper reason coordination is so expensive: most of it exists to move knowledge from one person’s head into another’s. Who signs off on this. Which system holds the master record. What we decided last quarter and why. When that knowledge is undocumented, every alignment is a live retrieval from a human being, and the tax is paid again every single time.
- Knowledge as tacit - The map of how work really flows - the exceptions, the workarounds, the unwritten rules - usually lives in a few experienced people, not in any system.
- Coordination as retrieval - A large share of meetings and messages are just queries against those human databases: “quick question, who handles X?” Each query interrupts an expert.
- The tax spikes when people leave - When an experienced person resigns or retires, the coordination knowledge leaves with them. The remaining team pays a re-learning tax on top of the ordinary one.
- Onboarding is the tax made visible - Every new hire has to reconstruct the coordination map from scratch by asking the busy people, which is precisely the Brooks dynamic in slow motion.
- Seasonal work is the worst case - Processes that run once a year - the annual close, an audit, a renewal cycle - are the hardest to remember and the most dependent on one person’s memory.
Why This Compounds With Turnover
The coordination tax and the knowledge-in-heads problem reinforce each other. The more coordination knowledge is undocumented, the more meetings you need to move it around, and the more catastrophic it is when a key person walks out. A company that never captures how it works pays the coordination tax forever, and pays a re-learning surcharge every time it loses someone who mattered.
This is the case for building a durable, shared memory of how the company actually operates - a Company Brain. If the coordination knowledge lives somewhere that both people and software can read, the routine questions stop routing through a human, and the answers survive when the human leaves. We will come back to what that looks like in practice.

Why the Usual Fixes Fail
When the drag becomes undeniable, leaders reach for a familiar set of moves. Most of them treat the symptom and leave the mechanism intact - or make it worse. Here is why the four most common responses disappoint.
Fix 1: Hire more people
- The obvious move that backfires - The team is overloaded, so add capacity. But the new person draws information and review time from the people who were already the bottleneck, exactly as Brooks described1.
- New links, not just new hands - Each hire adds coordination links faster than output, so the effective tax rate on the whole team ticks up3.
- The market is against you - Hiring is slow and expensive, and skilled roles stay open for months. The capacity you need rarely arrives when you need it.
Fix 2: Reorganise
- Redrawing boxes - A reorg changes who reports to whom, but the informal links along which work actually travels often survive untouched.
- Coordination moves, it does not vanish - Splitting a team into two can cut internal links while adding a new, thick coordination seam between the two halves.
- The disruption tax - Every reorg resets relationships and context, temporarily raising the very coordination cost it was meant to lower.
Fix 3: Flatten the hierarchy
- The 2025 trend - Companies are stripping out middle management: 41 percent cut management layers in 2025, and average spans of control have widened to about 12 people per manager, up nearly 50 percent since 201313.
- Overload moves up - Wider spans push coordination onto fewer managers. Gartner found 75 percent of HR leaders believe their managers are overwhelmed, and middle managers report the highest burnout of any group13.
- The work is still there - Removing a layer without removing the underlying coordination just redistributes the load onto people who already had no slack.
Fix 4: Buy more collaboration tools
- More surface, more stalls - Each new tool is another inbox, another channel, another place a request can wait. Workers already toggle apps 1,200 times a day9.
- Notifications are interruptions - A tool that pings is a tool that fragments focus. Adding channels tends to raise the interruption count, not lower it.
- Tools coordinate people; they do not do the coordinating - Software that shows you the handoff still leaves a human to perform it. The manual work is untouched.
| Common Fix | What It Targets | Why It Falls Short |
|---|---|---|
| Hire more people | Capacity shortage | Adds links faster than output; slow and costly to hire |
| Reorganise | Reporting structure | Moves coordination seams; disrupts context |
| Flatten layers | Management cost | Overloads remaining managers; work remains |
| Buy tools | Collaboration friction | Adds surface and interruptions; humans still do the handoffs |
| Add leverage | The coordination work itself | Absorbs routine handoffs without adding a node to coordinate |
Reorganise vs Rewire the Work
Reorganise (boxes)
- ✗ Changes the chart - not the informal links where work moves
- ✗ Resets relationships - a short-term spike in coordination cost
- ✗ Recurs - the same drag returns in a new shape within a year
Rewire (the work)
- ✓ Removes handoffs - automates the connecting itself
- ✓ Captures knowledge - the coordination map stops living only in heads
- ✓ Compounds - each absorbed process lowers the tax permanently
The Real Escape: Leverage, Not Headcount
There are only two ways to get more output from an organisation. Add more people, which adds coordination cost faster than it adds capacity. Or add leverage, which adds capacity without adding a new person who must sit in every meeting. The whole argument of this piece comes down to that choice.
- Headcount is linear capacity, super-linear cost - Every hire is one more node in the coordination graph, and the graph grows with the square of the nodes3.
- Leverage is capacity without a new node - A standard playbook, an automated workflow, or an AI employee absorbs work without needing to be aligned, updated, or invited.
- The best leverage removes the coordination, not just the task - Automating a form still leaves the handoff. Absorbing the whole routine loop - read the request, check the systems, take the action, escalate only the exception - removes the coordination itself.
What an AI employee actually absorbs
An AI employee is not a chatbot in a corner. It is a worker wired into the systems your team already uses - email, Teams, SharePoint, CRM, ERP - that takes over concrete routine work end to end. Applied to coordination, that means the handoffs stop bouncing between people.
- Status chasing - Instead of a person pinging three colleagues for an update, the AI employee reads the systems of record and answers the question directly.
- Routine approvals - It checks a request against the rules, approves what clearly qualifies, and routes only the genuine exceptions to a human.
- Data entry and reconciliation - It moves data between systems so people stop toggling apps 1,200 times a day to do it by hand9.
- Answering the routine question - It reads the Company Brain and answers “who owns this, what did we decide, where is the master record” without interrupting an expert.
- Follow-through - It drafts the email, files the document, updates the ticket, and closes the loop, so a decision does not wait on someone finding time to execute it.
The Company Brain Is the Multiplier
An AI employee is only as good as what it knows about your company. That is why leverage starts with a Company Brain - a structured memory of your processes, decisions, systems, and context. Because the coordination map now lives somewhere both people and AI can read, the routine questions get answered instantly, the knowledge survives turnover, and every new process you capture lowers the tax a little more19.
Why this beats every fix in the last section
| Lever | Adds Capacity? | Adds a Node to Coordinate? | Net Effect on the Tax |
|---|---|---|---|
| New hire | Yes (after ramp) | Yes | Rises |
| Reorg | No | Moves seams | Roughly flat, spikes short-term |
| More tools | Marginal | Yes (more surface) | Often rises |
| AI employee + Company Brain | Yes | No | Falls |
Adding Headcount vs Adding Leverage
Adding Headcount
- ✗ Super-linear coordination cost - links grow with the square of the team
- ✗ Ramp drag - months of net drain before net gain
- ✗ Knowledge stays in heads - and walks out the door on resignation
- ✗ Slow and costly - roles stay open for months
Adding Leverage
- ✓ No new node - capacity without a new person to align
- ✓ Absorbs routine coordination - handoffs stop bouncing between people
- ✓ Knowledge is captured - the Company Brain survives turnover
- ✓ Fast to start - a first use case can go live in weeks
How Superkind Fits
Superkind builds custom AI employees that plug into the systems your team already uses and take over concrete routine work - the exact work that generates most of the coordination tax. The approach is process-first: we start from how your company actually operates, not from a generic template you have to bend to fit.
- Wired into your stack - AI employees connect to email, Teams, SharePoint, CRM, and ERP as one layer over everything you already run. No rip-and-replace, nothing new for the team to learn.
- Built on a Company Brain - Each AI employee reads a structured memory of your processes, decisions, and systems, so it answers routine questions and takes routine actions with real company context - not internet generalities.
- Absorbs the handoffs - It chases the status, checks the request, updates the record, and routes only the genuine exception to a person, so coordination stops bouncing between inboxes.
- Live in weeks - The first AI employee usually goes live within about two weeks. No six-month rollout before anything changes.
- Knowledge that survives turnover - Because the coordination map lives in the Company Brain, it stays when people leave and shortens onboarding for the people who arrive.
- Grows in performance, not headcount - Your team carries more real work without new hires, because the routine load is absorbed rather than passed to another person.
- Improves daily - The AI employees get better because your team works with them and corrects them, so accuracy rises with use.
- Use case by use case - We start with one high-tax process, prove the ROI, then expand, so the investment tracks measurable results rather than a big-bang promise.
| Approach | Hire More People | Generic AI Chatbot | Superkind AI Employees |
|---|---|---|---|
| Effect on coordination links | Adds a new node | Adds another tool | Absorbs handoffs, adds no node |
| Company-specific knowledge | In the person’s head | Knows the internet, not you | Reads your Company Brain |
| Time to value | Months to ramp | Fast but shallow | First use case live in weeks |
| Survives turnover | No - walks out the door | N/A | Yes - knowledge is captured |
| Integration | Desk and logins | Separate app | Layer over existing systems |
Superkind
Pros
- ✓ Process-first - built around your real workflows, not a template
- ✓ No platform lock-in - works on top of your existing tools
- ✓ Fast time-to-value - first AI employee live in about two weeks
- ✓ Clear ROI - one use case at a time, measured
- ✓ Knowledge captured - the Company Brain outlives any individual
Cons
- ✗ Not self-serve - requires working with our team to set up
- ✗ Needs process access - we have to understand how work really flows
- ✗ Overkill for tiny teams - a 5-person shop pays little coordination tax yet
- ✗ Not a magic reorg - it absorbs routine work, it does not redesign your strategy
A Practical Playbook to Cut the Coordination Tax
You do not fix the coordination tax with a slogan about fewer meetings. You fix it by finding where the tax is highest and absorbing that specific coordination work. Here is a sequence any operator can run.
- Measure the tax - Track three numbers for a fortnight: the share of the week spent in meetings and messages versus focused work, the number of handoffs in your top five processes, and the average wait time for a routine approval or answer. This is your baseline.
- Map the handoffs - Pick the process that scored worst and draw every point where work passes between people or systems. Each arrow is a link that costs coordination. Count them.
- Find the routine loops - Separate the genuine judgment calls from the routine loops - the status chases, the standard approvals, the data moves. The routine loops are the tax you can absorb.
- Capture the knowledge - Write down how the process actually works, including the exceptions and the unwritten rules. This becomes the seed of a Company Brain and stops the knowledge living only in one head.
- Absorb one loop with leverage - Put an AI employee on a single high-tax loop end to end: read the request, check the systems, take the routine action, escalate the exception. Do not boil the ocean.
- Route only exceptions to people - Redesign the process so a human is involved only when judgment is genuinely required. Every routine case that no longer needs a person is coordination tax removed.
- Measure again and expand - Re-run the three baseline numbers. When wait times and meeting load drop, move to the next-worst process. The gains compound as the Company Brain grows.
Coordination Tax Audit Checklist
- You can name your five most handoff-heavy processes
- You know the share of your team’s week spent coordinating versus creating
- You can point to at least three recurring “who owns this?” delays
- You know which routine questions repeatedly interrupt your experts
- The knowledge behind your key processes is written down, not just remembered
- You have separated genuine judgment calls from routine loops
- You have one high-tax loop ready to hand to an AI employee
- You have a baseline you can measure the change against
The One-Process Rule
The single most common reason automation efforts stall is trying to fix everything at once. Start with one process that scores high on handoffs and wait time, absorb its routine loops, prove the drop in coordination cost, and only then expand. One clear win builds more momentum than ten half-finished pilots.
Decision Framework: Are You Paying Too Much Coordination Tax?
Not every company should reach for leverage today, and not every drag is a coordination problem. Use these signals to decide where you stand and what to do next.
| Signal | What It Means | Action |
|---|---|---|
| Output flat or falling as you add people | You are past the point where headcount helps | Freeze the reflex hire; audit the coordination tax first |
| Meetings and wait times rising faster than revenue | Coordination is outgrowing value creation | Map handoffs on your worst process and absorb the routine loops |
| Routine questions keep interrupting your best people | Coordination knowledge lives in a few heads | Capture it in a Company Brain an AI employee can read |
| A key departure would cripple a process | You are exposed to a re-learning tax on turnover | Document the process now; do not wait for the resignation |
| Every decision escalates to the founder | Ownership is diffuse and the founder is the bottleneck | Define decision rules and let leverage handle the routine |
| Fewer than 15 people, simple linear work | Your coordination tax is still low | Keep it simple; revisit as you scale and processes multiply |
Absorb the Tax Now vs Keep Scaling by Headcount
Absorb Now
- ✓ Compounding relief - each absorbed loop lowers the tax permanently
- ✓ Knowledge captured early - before the next key departure
- ✓ Existing team does more - without the ramp drag of new hires
- ✓ Cleaner processes - you have to understand the work to absorb it
Keep Scaling by Headcount
- ✗ Rising tax rate - each hire adds links faster than output
- ✗ Slower decisions - more nodes, more alignment, more delay
- ✗ Fragile knowledge - still trapped in individual heads
- ✗ Falling profit per employee - complexity outpaces contribution
For a broader look at the failure modes this connects to, our pieces on the interruption tax, the founder bottleneck, and seasonal knowledge that nobody remembers how to run each pull on one thread of the same problem.
Frequently Asked Questions
The coordination tax is the compounding overhead of keeping people aligned: the meetings, status updates, handoffs, approvals, and "who owns this?" questions that grow every time you add a person. It is not the productive work itself. It is the cost of connecting the people who do the work. Because the number of communication links grows faster than headcount, the tax rises as a percentage of every hire the bigger you get.
Each new person adds communication links with everyone else, and those links grow roughly with the square of team size, not in a straight line. A team of 5 has 10 possible one-to-one links, a team of 20 has 190, and a team of 50 has 1,225. Past a point, the coordination each hire creates eats more capacity than the hire adds. This is Brooks's Law applied to operations, not just software.
The evidence is stark. Microsoft's 2025 Work Trend Index found knowledge workers spend about 60 percent of their time on communication (meetings, email, and chat) and are interrupted roughly every two minutes, or 275 times a day. Bain estimates the average company loses more than 20 percent of its productive capacity to organizational drag. Harvard Business Research found workers toggle between applications over 1,200 times a day.
Bureaucracy is one source of it, but the coordination tax is broader. It includes healthy-looking activity too: alignment meetings, Slack threads, cross-team reviews, and re-explaining context to new hires. Much of it feels like real work. That is what makes it dangerous. Nobody schedules a meeting called "waste", yet the sum of well-intentioned coordination can consume a full day of every working week.
It can, because informal alignment that used to happen at a desk now becomes a scheduled call or a written thread. Microsoft found 57 percent of meetings are now ad hoc and the average worker receives 153 Teams messages per weekday. Remote work does not create the tax, but it makes it visible and often converts quick clarifications into formal coordination events that take longer.
Because a new hire needs information before they can contribute, and that information comes from the people already at capacity. They ask questions, need onboarding, and add new links to coordinate. For the first weeks or months, a new person is a net drain on the exact people who were already the bottleneck. The team gets slower before it gets faster, and sometimes it never recovers the lost time.
Headcount adds capacity linearly and coordination cost faster than linearly. Leverage adds capacity without adding a new node to coordinate. Automation, standard playbooks, and AI employees are leverage: they absorb routine work and answer routine questions without needing a seat in every meeting. The goal is to grow output faster than you grow the number of people who must stay aligned.
A generic chatbot adds another tool and another place to check, which can raise the tax. An AI employee wired into your existing email, Teams, SharePoint, CRM, and ERP does the opposite: it absorbs the handoffs and routine questions that used to bounce between people. Instead of a person chasing an approval across three systems, the AI employee reads the context, drafts the action, and routes only the genuine exceptions to a human.
A Company Brain is a shared, structured memory of how your company actually works: its processes, decisions, systems, and context. It matters because most coordination exists to move knowledge out of one person's head and into another's. When that knowledge lives in a Company Brain that AI employees can read, the routine questions get answered without interrupting an expert, and the knowledge survives when people leave.
Start with three numbers: the share of the workweek spent in meetings and messages versus focused work, the number of handoffs in your top five processes, and how long a routine request waits for an answer or approval. Track how each changes as headcount grows. If meetings and wait times rise faster than output, you are paying an increasing coordination tax, and adding people will make it worse, not better.
No. It scales with connections, not just size. A 40-person company with tangled processes and no written playbooks can pay a higher effective tax than a disciplined 400-person company. Founder-led businesses feel it early because everything routes through one person. The tax becomes acute at the growth stages where a company adds people faster than it documents how work is done.
Flattening can help, and many companies are doing it: 41 percent cut management layers in 2025. But wider spans of control push coordination onto fewer managers, who are already overwhelmed. Removing a layer without removing the underlying coordination work just moves the load. The durable fix is to absorb the routine coordination itself with leverage, so the remaining structure has less to carry.
More collaboration tools usually add coordination surface: another inbox, another channel, another place a request can stall. The number of apps workers switch between averages nine, and each switch costs focus. Leverage works the other way. An AI employee sits on top of the tools you already run and does the connecting for people, so the answer is fewer places to check and fewer manual handoffs, not more.
The goal is to remove the routine coordination, not the people. When an AI employee handles the status chasing, the data entry, and the routine approvals, your team spends its time on judgment, relationships, and the genuinely hard decisions. In a labour market where hiring is slow and expensive, absorbing the coordination tax lets your existing people carry more real work without burning out on overhead.
Related Articles
- The Interruption Tax: What “Quick Questions” Really Cost Your Experts
- The Founder Bottleneck: When Everything Runs Through One Person
- Seasonal Knowledge: The Once-a-Year Processes Nobody Remembers How to Run
- AI Agents for the Mittelstand: Deploy AI Without Losing What Makes You Great
Sources
- Frederick P. Brooks Jr. - The Mythical Man-Month / Brooks's Law (Wikipedia)
- Quire - The Coordination Tax: Project Management Overhead
- PanDev Metrics - Brooks's Law in 2026: Communication Overhead vs Team Size
- Bain & Company - Time, Talent, Energy: Overcome Organizational Drag
- Bain & Company - Summary of Time, Talent, and Energy
- Creative Leadership Solutions - Reduce Organizational Drag (Michael Mankins interview)
- Microsoft Work Trend Index 2025 - Breaking Down the Infinite Workday
- Microsoft Work Trend Index 2025 - The Year the Frontier Firm Is Born
- Harvard Business Review - How Much Time Do We Waste Toggling Between Applications
- Asana - Anatomy of Work: Context Switching Costs and Fixes
- Gartner - Organization Design Benchmarks: Manager Spans of Control and Management Layers
- HR Bench - Span of Control: Formula, Benchmarks and Turnover Link
- SpeakWise - Middle Management Statistics 2026
- World Economic Forum - Future of Jobs Report 2025
- Hans-Boeckler-Stiftung - Meetings: Viel besprochen, wenig geloest
- OPEX / KVP Institut - Wissensarbeit besteht zunehmend aus Koordination statt Wertschoepfung
- Gabler Wirtschaftslexikon - Abstimmungskosten (Definition)
- Computerwoche - Meetings: schwarze Loecher fuer die Produktivitaet
- McKinsey - The State of AI 2025
- Moor Insights & Strategy - Microsoft Work Trend Index 2025 Shows Workplace Capacity Strain
- Deloitte - Global Human Capital Trends
- Bregman Partners - Michael Mankins: Time, Talent, Energy (podcast)
Ready to stop paying the coordination tax?
Book a 30-minute call with Henri. We will find your highest-tax process and show what an AI employee on a Company Brain could absorb - no commitment, no sales pitch.
Book a Demo →
