Why ops breaks at 20 people
The systems that got you to 20 staff won't get you to 50. Here's what to watch for.
The pattern
Every growing business hits the same wall somewhere between 15 and 25 people. The systems that worked — spreadsheets, Slack threads, one person who knows everything — start to crack.
It's not anyone's fault. It's structural.
What breaks
Communication. When you had 8 people, everyone knew everything. At 20, information starts living in silos. Decisions get made without context. Work gets duplicated.
Processes. The informal "how we do things" becomes unreliable. New hires can't learn by osmosis anymore. Mistakes increase. Rework increases.
Tools. The spreadsheet that tracked 50 clients can't track 200. The inbox that managed 10 orders a day buckles at 40.
What to do about it
You don't need to hire an ops team (yet). You need to:
- Map what you actually do — not what you think you do
- Identify the 3-4 processes that hurt most
- Fix them in order of impact, not complexity
- Automate the repetitive parts before hiring more people to do them manually
The goal isn't perfection. It's making the next 20 hires less painful than the last 20.