The Five Stages of Scale
Diagnose your company by headcount stage — family, tribe, village, city, nation — and change the rules
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 88%
Hoffman's scaling model breaks company growth into five stages by employee count: family, tribe, village, city, and nation. The mechanic is that headcount proxies for scale across every vector — sales, product lines, customer service, account management, finance — so employee count is a usable diagnostic for organizational complexity. At each stage, what got you here won't get you there. Communication changes as you go from everyone in a room, to workers plus managers, to pure managers, to managers of managers. Decision-making, pivoting, and acceptable risk all rebase. Crucially, the underlying principle may survive while the tactic inverts: Facebook's 'move fast and break things' became 'move fast with stable infrastructure' — both are speed principles, but broken infrastructure at 500 people makes you slower, not faster. The output is a stage-appropriate operating system rather than nostalgic habits.
Origin
Extracted from Young and Profiting
Core principles
- 01Headcount proxies for organizational complexity across every vector
- 02What got you here won't get you there
- 03Communication, decision-making and risk tolerance all rebase at each stage
- 04The principle can stay constant while the tactic must change
- 05The mistake is running nation-stage at village-stage rules, or vice versa
How to run it
- 1
Locate your stage honestly
Place the company on the family / tribe / village / city / nation ladder using headcount as the proxy for complexity across all functions.
Pro tip You can sit between stages — that's usually where the growing pains are loudest.
Watch out Revenue and headcount can diverge; the stage that governs your management problems is the headcount one.
- 2
Audit inherited practices
List the practices you're still running purely because they worked at the previous stage: how you communicate, how you hire, how you decide, what you let break.
Pro tip The clearest tell is a habit that feels harmless but keeps generating friction.
Watch out Founders defend early-stage practices as culture when they're really just artifacts of being small.
- 3
Rebase communication and decision rights
Redesign how information moves and who decides, given the new layer count. Family stage needed neither; nation stage needs both explicitly.
Pro tip Note the shift: everyone works, then some manage, then some only manage, then some manage managers.
Watch out Adding management layers without redesigning decision rights just adds latency.
- 4
Reset which risks you'll take
Re-ask which risks the current stage can absorb. Speed still matters, but the things you're willing to break change completely.
Pro tip Facebook kept the speed principle and swapped the tactic: move fast with stable infrastructure.
Watch out Assuming you 'got wise and abandoned speed' misreads the change — the goal is still speed, via a different route.
- 5
Preserve the principle, replace the tactic
For each practice, separate the durable belief from the stage-bound implementation, and rebuild the implementation for your size.
Pro tip Keep vibrant culture, high performance and high-quality talent constant; let the mechanics vary.
Watch out Wholesale reinvention destroys what was working; surgical replacement is the point.
In the wild
Facebook's 'move fast and break things' was optimal at roughly 40 people, when breakage was cheap and speed came from not caring. At 500 people, broken infrastructure was too hard to fix and the company was suddenly moving slower. The slogan became 'move fast with stable infrastructure'. Hoffman's point is that people misread this as Facebook getting wise and abandoning speed. It didn't. Both versions are speed principles; only the tactic changed, because at the new stage the old tactic produced the opposite of its intent.
→ Facebook preserved velocity through a stage transition by swapping the tactic while keeping the principle.
The host describes her own company sitting between tribe and village stage: growing well, but scaling feels genuinely hard for the first time. Her hiring illustrates the transition — she used to find someone on LinkedIn, DM them, interview, and hire, and now runs a months-long process that sometimes visibly slows the business down. The stage model reframes this from 'we got worse' to 'the game changed, and each practice needs a deliberate pros-and-cons call at this size'.
→ Growing pains get diagnosed as a stage transition rather than a personal failure.
Common mistakes
Running village rules at nation scale
Hoffman names this as the mistake directly: trying to run the same way you did at a smaller stage once the size has changed the nature of the game.
Reading a tactic change as a values change
When a company swaps 'break things' for 'stable infrastructure', observers assume it abandoned speed. It usually just found the faster route at the new size.
Scaling headcount without scaling the operating system
Employee base grows with sales, products, support, and finance whether you plan for it or not; the communication and decision structures don't upgrade themselves.
Is it for you?
Best for
Founders and operators crossing a growth threshold who can feel that their existing habits are starting to cost them.
Not ideal for
Deliberately small or lifestyle businesses that never intend to scale headcount past a single team.
From the transcript
“when you're getting to each of these things um what got you here won't get you there”
“move fast and break things work totally fine when you're 40 people. When you're 500 people and the infrastructure breaking and everything breaks”
“your mistake is trying to run the same way as you might be even in a village when you're in a nation”
From the episode
Reid Hoffman: LinkedIn Co-Founder on Building and Scaling Massively Valuable Companies Fast
Reid Hoffman