Writing Management Infrastructure

The cost of coordinating without structure

Every company past a certain size pays a hidden tax on every decision because information moves through people instead of through structure. The bill compounds until someone designs the coordination on purpose.

January 2026 4 min read

A company of twenty people coordinates by talking. Everyone is one message away from everyone else, information travels in one hop, and a new decision reaches the people who need to know about it inside a day. The coordination cost is invisible because there’s almost nothing to pay for.

At eighty people the same company still coordinates by talking, except now the talking is spread across a dozen projects in several time zones, with more relationships than any one person can hold in their head. The information still travels, but it travels by bouncing through people: someone in product mentions a change to someone in sales who mentions it to a customer who mentions it back to the account team three weeks later, and by the time leadership hears about it the context has been rewritten four times. Nothing has gone wrong, exactly. The tax is being paid in small denominations spread across everyone’s week.

At two hundred people, if nothing has changed, the tax has become the main cost of running the company. Decisions take longer than they should because the information needed to make them is scattered across the people who know different parts of the answer, and new hires take a quarter to become useful because what they needed to know wasn’t written down and they had to extract it from five different colleagues who each had a partial version. Initiatives that span teams stall in the gap between the two teams, because the thing that would have made them move was a piece of shared context that didn’t exist anywhere except inside a handful of senior heads.

The tax is invisible because it doesn’t show up as a line item. It shows up as a general feeling that things are slower than they used to be and that everyone is working more for less output. The leadership team diagnoses this as a culture problem or a focus problem and tries to fix it with better meetings or a new OKR framework. Neither works, because the real cause is that the company has grown past the size where informal coordination can carry the load, and nothing has been built to take its place.

What gets built, eventually, is structure. A shared place where the current state of a project is recorded so nobody has to ask. A written version of how decisions get made in each area, so the pattern doesn’t have to be rediscovered every time. A record of which person owns which question, so the question doesn’t circulate through three of them before it lands somewhere. An onboarding that points at the structure, so new people inherit it instead of having to reconstruct it.

The resistance to building the structure is predictable and worth naming. Operators who came up when the company was small associate structure with bureaucracy, because the structure they’ve seen has mostly been the bureaucratic kind: process for process’s sake, invented to justify the people who manage it. That version is real and worth avoiding. The version that’s worth building is different: structure whose only job is to carry information so that coordination doesn’t have to happen through a conversation every time. It’s lighter than the bureaucratic kind because it’s subtractive: every piece of it is there to remove a conversation that was costing more than the structure costs.

The test for whether a piece of structure is worth keeping is whether it’s cheaper than the informal coordination it replaces. A document that gets read and keeps three people from having to ask the same question is paying for itself. A process that nobody reads and nobody follows is the tax without the benefit, and it should be cut. Most companies end up with both kinds running at the same time, with the useful structure underused because nobody trusts it and the useless structure overused because someone is measuring compliance with it.

The work of building coordination structure is slow and unsatisfying, because the payoff is invisible in the month you do it. The company that invests in it compounds every month after, because every decision made inside the structure costs less than the same decision would have cost outside it. The company that doesn’t keeps paying the tax, and the tax keeps growing, and nobody ever gets a bill.

Subscribe

A roughly monthly dispatch from karlbaz.com. Links to the month's memos, plus a short note on what matters now.

Roughly monthly · No promo · I do not sell or share your address · Unsubscribe anytime