When Not to Grow

The seventh collapse pattern is the one that arrives disguised as success. Demand is up, you hire, and within a year the thing that made the organization good has quietly stopped working. Everyone can feel it. Nobody can name the decision that caused it, because the cause was not a decision. It was a series of yeses that outran the structure.

The numbers where structure breaks

These are not laws, but they are consistent enough to plan against.

Around 7 to 12 people. Everyone can no longer be in every conversation. Below this, coordination is free: you all hear everything. Above it, information starts having to be deliberately moved, and if nobody has made that someone's job, it stops moving. The first symptom is two people doing the same work, or a decision made by someone who did not know something they would have known last year.

Around 25 to 30. You can no longer hold everyone's context in your head. The founder stops knowing what everyone is working on. Informal coordination collapses. This is where groups either build real governance or become quietly hierarchical while insisting they are flat.

Around 50 to 60. You need subgroups with genuine autonomy, and links between them. One circle of 50 does not work, whatever the process.

The trap is that each threshold is crossed by hiring one more person, which never feels like a structural decision.

Growth is not the only response to demand

When demand exceeds capacity, hiring is the reflex. There are five other options, and most groups never consider them.

Raise prices. The least popular and often the most correct. If you cannot meet demand, your price is below market. Higher prices with the same team is more resilience, less coordination cost, and better clients.

Say no to a segment. Drop the work that fits worst. Capacity is freed, focus improves, and your purpose gets sharper.

Narrow what you offer. Doing three things well for more people beats doing nine things for everyone, and requires far fewer people.

Improve throughput. Sometimes the constraint is a broken handover, not headcount. Adding people to a coordination problem makes it worse.

Stay the size you are and let demand go elsewhere. A legitimate strategic choice that is almost never named as one. Some of the most durable organizations decided their size on purpose and defended it.

Growth is one option among six. Treating it as the default is how the trap closes.

Before you hire, answer these

What structure breaks at this number? If you are going from 9 to 13, you are crossing a threshold. What has to exist that does not exist now? Usually: written roles, a real governance rhythm, and someone accountable for information moving.

Who onboards them? Not "we all will". A specific person, with time actually allocated. Groups that grow badly are usually groups that hired well and onboarded badly, and the new person concluded within a month that nobody had a plan.

What is our runway after this hire? See Open Books. Hiring into a four-month runway is a bet, and everyone should know it is being placed.

Is this demand durable? One large client's expansion is not a trend. Hiring against a single client's growth is how you end up with a team and a concentration risk at the same moment.

What do we lose? There is always something. Say it out loud. At 12, you lose everyone-in-the-room. At 30 you lose the founder knowing everyone's work. Naming the loss in advance means people grieve it rather than experiencing it as decline.

Growing without breaking

Add structure one threshold ahead, not one behind. At 10, build what 15 needs. Adding structure while already overloaded is how it becomes bureaucracy: rushed, over-general, and resented.

Split before it hurts. Two circles of 12 with clear purposes and a link between them work better than one of 24. Splitting is not failure; it is the mechanism.

Hire in ones, with gaps. Three people at once cannot be absorbed by a group of ten. Culture is transmitted by proximity and there is not enough to go around.

Write down what was implicit. At 8 people, "how we do things" lives in shared memory. At 20 it has to be written or it is lost, and the newest third of the organization is operating on guesses.

Protect the practices that carry it. Check-ins, governance meetings, the rounds. They feel expensive as you grow and are usually the first to be cut. They are the mechanism, not the overhead, and cutting them is how a 30-person organization becomes a normal company.

Where it goes wrong

Growth as the measure of health. If the only number anyone celebrates is headcount or revenue, you will grow past your structure, because nothing else is being watched.

Hiring to relieve overload without asking why there is overload. Sometimes overload is a structural problem and a new person joins the same broken process, gets overloaded too, and now two people are drowning.

Believing culture will carry it. Culture at 10 is relationships. At 40 it must be practices and written agreements, or it becomes nostalgia and a growing gap between the founders' story and everyone else's experience.

What good looks like

A group turns down work, on purpose, with a clear reason, and does not treat it as a loss.

A group that decides to grow crosses a threshold deliberately: roles written first, someone accountable for onboarding, the loss named out loud.

And someone can say "we are the right size" without it being a defense.

Try this week

Count your people. Find which threshold you are nearest.

Then ask the question groups skip: if demand doubled next quarter, which of the six responses would we choose, and have we ever discussed the other five?

If hiring is the only one that has ever been on the table, the trap is already open.