The Scaling Laws of Multiple Agents
I built a team of agents to move faster. Most days, I’m the reason they don’t.
They handle content drafts, the social calendar, the metrics pipeline, my daily digest, even my expense reports. It all runs at once, and the whole thing routes through me. This one finished the thing that one’s been waiting on. That landed over here — make sure it shows up over there. That one’s about to redo work another one already did. None of them can see each other, so the only place the full picture lives is in my head. I’m the human router — and the slowest part of a system I built to be fast.
Here’s what I didn’t expect: this isn’t new. It has a name, and it’s fifty years old.
In 1975, Fred Brooks wrote down the law that still governs every team. Add people to a project and the number of communication paths grows faster than the number of people: two share one line, ten share forty-five. (It’s n(n−1)/2, from The Mythical Man-Month.) The work inside any one head grows with the heads; the wiring between heads grows like the square, and somebody has to keep it straight.
There’s a flip side. Metcalfe’s law points out those same connections are also what make a network valuable — worth having, but expensive to maintain.
And none of it changes when the nodes are agents instead of people.
You’d think handing the work to agents would kill the coordination — no meetings, no calendars, no egos. It doesn’t. It just moves onto the one part that can’t scale: the person in the middle. And speed makes it worse. The teams Brooks wrote about shipped in months. Agents land work in minutes. By the time you’ve told one what another finished, it’s three steps further along. That’s a ceiling, and you don’t get over it by trying harder.
The coordination cost never disappears. The only choice is where it lands — on you, or on a map the work carries with it.
The way past the ceiling is to stop being the router entirely and give the work itself somewhere to coordinate. Every change that lands should carry its own short answer to the only question that matters downstream — who else needs to know? What it touched, who owns the next step, what should happen because of it. Write that to a shared map every agent can read and every change updates, and nobody has to be the wire between everybody else.
That’s what we’re building WarmHub to be. The team has made this case before — the most valuable thing you can give an agent is the right context at the moment it acts, which is why we say context is the new content. A coordination map is exactly that kind of context: what a change just set in motion, the thing that otherwise lives in nobody’s head until it breaks something downstream.
One catch, and it decides everything: a map only works if the agents maintain it. A shared graph the agents don’t write to is just another dashboard a human keeps current by hand. You’re the router again, with extra steps. So the real question is small and sharp: what’s the least you have to teach an agent for it to become a good contributor to the shared picture? Get that increment right, and the map stays current as a side effect of the work.
We’re running this today. The proof is our documentation team: a writer, a fact-checker, and an editor — all agents — coordinating through a shared picture in WarmHub of what changed and what still needs a look, with a human making every final call. Amber Bowden wrote it up in Running Our Docs Like a Newsroom; if you read one thing after this, read that. The frontier is Amber’s change-readiness work: an evaluated alpha where an agent can recover a real change, the people and areas connected to it, which steps are automatic versus judgment calls, and what evidence is still missing, without anyone narrating the path. The general version, where every change in the org carries its own map, is what she’s proving out now, not something we’re calling finished.
The thing that won’t change: add agents and the coordination cost grows faster than the agents do, same as it always did with people. The only choice you get is where that cost lands: on a map the work carries with it, or on you, at midnight, telling agent seven what agent three did.