How to Scale Communication as Your Team Grows
The recurring experience is this: something important was decided, and three weeks later you discover that two teams did not know, one team knew a distorted version, and someone made a costly call based on the distortion. The instinctive reading is that people are not paying attention, or that the company has a discipline problem. It is neither. Communication cost grows faster than headcount, and a system that worked at twenty people mathematically cannot work at eighty. This page is about what to build instead.
What’s inside
Communication cost grows faster than headcount
The three things that have to travel
Why writing replaces meetings, not supplements them
What to build at each stage
The repetition threshold
Four failure patterns
Where Blomma fits
Communication cost grows faster than headcount
The arithmetic is the whole explanation. At ten people there are forty-five possible pairs. At fifty there are more than twelve hundred. The number of relationships through which information could travel grows roughly with the square of headcount, while the time available to maintain them grows not at all.
What that means practically is that informal transmission — which is how every early company works, and works well — stops being sufficient at a predictable point, usually somewhere between thirty and fifty people. Nothing about the people changed. The mechanism ran out of capacity.
The second effect compounds it. Each hop information travels through degrades it. A decision explained by a founder to an executive to a manager to a team arrives with the reasoning stripped and the nuance gone, because each person passes on the conclusion rather than the argument. That is why teams act on distorted versions: not carelessness, but transmission loss.
So the design goal has two parts: reduce the number of hops, and make what travels durable enough to survive the hops it does take. Both point at the same answer.
The three things that have to travel
Not all information is the same, and treating it as one problem is why communication initiatives fail. Three types, with different requirements.
Direction.Where the company is going, what matters this year, what does not. Needs to reach everyone, needs to be repeated far more than feels necessary, and needs to be identical everywhere. This is the one that degrades most through hops, so it should travel with as few as possible — which means from you, directly, in writing, repeatedly.
Decisions and their reasoning.What was decided and why. Needs to reach the affected people and to persist, because the reason people re-litigate settled questions is that the reasoning was never recorded. Thewhyis the part that gets dropped and the part that matters — a decision without its reasoning cannot be applied to a new situation, so people either escalate or guess.
Status and progress.What is happening, what is blocked. Needs to be available rather than pushed, and it should live in a system rather than in anyone’s head. This is the type most companies over-communicate, in meetings, at the expense of the other two.
Audit your current channels against these three. Most companies find that status consumes their synchronous time while direction and reasoning have no reliable channel at all.
Why writing replaces meetings, not supplements them
At small scale, meetings are the most efficient channel: everyone hears the same thing at once and can ask questions. Past a certain size that inverts, for three reasons.
Meetings do not scale to the number of people who need the information, so the content gets relayed — which reintroduces hops and transmission loss.
Meetings do not persist. Someone who joins in three months, or was on holiday, or simply forgot, has no access. Every piece of important information communicated only verbally has to be re-communicated indefinitely, which is a permanent tax.
And meetings favour whoever is most comfortable speaking, which means the information that surfaces is filtered by confidence rather than importance.
The practical move is to make writing the primary channel for direction and decisions, and use synchronous time for the things writing cannot do: genuine debate, difficult feedback, and questions.
One caution. This does not mean writing more documents nobody reads. It means the reverse: fewer, shorter, findable artefacts with a clear owner — a one-page strategy, a running decision log with reasoning, a weekly written update replacing a status meeting. Length is the enemy. A three-page memo that gets read beats a thirty-page one that does not.
What to build at each stage
Under 20.Almost nothing formal, with one exception: start writing down decisions and their reasoning now. It costs an hour a week and it is the single thing that fails worst when you scale. The context in founders’ heads is your largest future liability.
20 to 50.A written weekly update from you — what changed, what matters, what is coming. A decision log. And the beginning of the shift where status goes in writing and meetings are for decisions. This is the stage the transition should happen, and most companies leave it until fifty.
50 to 150.A one-page strategy document that everyone has seen, restated regularly. A cadence where managers are briefed before their teams, with the reasoning, so they can answer questions rather than relay. Metrics visible to anyone who wants them. And explicit ownership of internal communication — someone whose job includes it, even part-time.
150+.A real internal communication function or owner. Structured cascade with reasoning attached at each level. Regular direct channels from you that skip the hierarchy — written updates, open sessions — because by this size you cannot rely on the chain to carry direction intact.
The repetition threshold
One calibration worth internalising, because it accounts for a large share of the gap between what founders believe they have communicated and what has landed.
Your threshold for repeating something is roughly a tenth of what your organisation needs. By the time you are bored of saying it, most people have heard it once, in passing, competing with their own work.
The reason is asymmetry of attention. You have thought about the strategy for months. For everyone else it was a paragraph in an update between two urgent things. That is not inattention; it is a rational allocation of their attention to the work in front of them.
So say it again. In the all-hands, in the written update, in the one-to-one, in the decision you explain by reference to it. The test of whether direction has landed is not whether you have said it — it is whether you can ask three people at random what matters most this quarter and get the same answer. Most founders who run that test are surprised.
Four failure patterns
Status crowds out direction.Your synchronous time is consumed by updates, so the strategy never gets discussed. Fix: move status to writing, ruthlessly.
Reasoning gets stripped in the cascade.Managers relay conclusions because they were only given conclusions. Fix: brief managers with the reasoning before they brief their teams, and expect them to be able to answer why.
Volume substituting for clarity.More channels, longer documents, more meetings, and less actually landing. Fix: fewer artefacts, shorter, with owners.
The founder as sole channel.Everything important comes from you, which does not scale and makes your executives look like conduits. Fix: have leaders own the communication of their own areas, with you owning direction only.
Where Blomma fits
Most of what fails here is not the system — it is the specific communication acts inside it. Explaining a decision in a way that survives being relayed. Briefing an executive so they can answer the hard question rather than deflect it. Saying the same thing for the eighth time with enough conviction that it lands as important rather than routine.
Blomma is an always-on AI career coach with no stake in your company. Use it to work out which of the three information types has no reliable channel in your company right now — usually reasoning. Use it to draft the one-page strategy or the decision write-up so the reasoning survives the hops. Use it to prepare a difficult company-wide message before you deliver it. And use it to run the three-people test on yourself honestly, which is uncomfortable and cheap.
The second application: your managers are the channel, and most of them have never been taught to communicate a decision they did not make in a way that holds up under questioning. That is a coachable skill and it is where most cascade failure actually happens..
Communication does not break because your people stopped caring. It breaks because the number of relationships grew faster than the mechanism, and nobody redesigned the mechanism.