Everything Breaks at 3 and 10

There's a restaurant I work with that grew from three people to five and fell apart.

Nothing dramatic happened. Nobody quit, nobody stole, the food didn't change. The owner just noticed, over about two months, that everyone was exhausted, quality was slipping, and the team that used to feel like a kitchen felt like a queue. Everything routed through him. It always had. That was the point: at three people, the owner is the operating system, and it works beautifully.

At five, it doesn't. And the cruel part is that nobody changed anything, which is exactly the problem. The system that made the place good stopped fitting the place it had become.

Hiroshi Mikitani, who built Rakuten, put a number on this: everything in a company breaks every time headcount roughly triples. At 3, at 10, at 30, at 100. Not the people. The invisible stuff: who decides what, how information moves, what gets rewarded, what a meeting is for. The coordination you got for free at one size becomes the thing quietly taxing everyone at the next.

The tell is always the same sentence: "it used to just work."

It did. Osmosis worked. Everyone heard everything because everyone was in the room. Approval was a look across the pass. Priorities didn't need writing down because there was only one, and everyone was staring at it.

Then you tripled, and osmosis died, and nobody held a funeral. So people fill the gap the only ways they can: they wait, or they silently absorb. When work is quietly absorbed it sneaks up on you. It's always just a little outside of your scope at a time until your scope becomes something unrecognizable. You're a few "can you justs" away from a total mental and physical collapse.

When teams wait for the founder, the founder absorbs every decision to keep things moving, and "nothing is stalled" becomes technically true while everything gets slower. The founder reads their own exhaustion as personal inadequacy. It almost never is. It's an operating model built for three, running at ten.

Two things worth doing the week you notice this.

Name the threshold out loud. "We tripled, so our old ways expired" is a diagnosis nobody has to be ashamed of, and shame is the main reason founders fix the wrong thing. Name the problem and you can predict it.

Then rebuild the two or three mechanisms the old size gave you free. Who can say yes to what, written on one page. Where information lives when it's not in your head (which pays exponential dividends). What the team would say the priorities are, without checking.

The restaurant did this. The owner kept her morning market run and insisted on a "family shift meal", wrote the routine decisions onto one page and handed them to her second, and got back the hours that made him good in the first place.

If some version of "it used to just work" has been rattling around your head: it's not you. It's probably the system needing an update.

---

Not sure whether you're at a threshold? The fit-check takes two minutes, no email required. — linked as above.