Autonomy at the VP Level
Place decision autonomy at the VP layer — not the leaves, not the top — to maximize thinking without producing chaos.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
If you hire smart people you must give them autonomy or you waste the investment. But pushing autonomy all the way to the leaves of a large, junior org produces 'heat' — hundreds of teams running in hundreds of directions. Concentrating it at the top bottlenecks everything on one person. The optimum sits at the VP level: enough senior thinkers for diverse bets, few enough to stay coherent.
Origin
Söderström's account of why Spotify moved on from its famous fully-autonomous 'squads' model as it scaled.
Core principles
- 01Hiring smart people is 'renting brainpower'; denying them autonomy wastes the spend
- 02Autonomy at the leaves plus a junior org produces heat, not progress
- 03Autonomy at the very top bottlenecks all decisions on one person
- 04VPs are numerous enough for diverse bets yet senior enough for pattern recognition
How to run it
- 1
Accept that smart hires require autonomy
If you pay for the smartest people and then give them no room to think, you should have hired cheaper people. Autonomy is how you realize the value of expensive talent.
Pro tip Frame headcount as 'renting brainpower' — the mental model makes withholding autonomy obviously wasteful.
- 2
Reject the two extremes
Don't push autonomy to the leaves (100 teams, 100 strategies, 100 directions), and don't hoard it at the top (a single decision bottleneck). Both fail at scale, in opposite ways.
Watch out A very junior org at the leaves amplifies the 'heat' problem because teams lack the pattern recognition to self-correct.
- 3
Locate autonomy at the VP layer
Give VPs high autonomy to set strategy for their area (e.g. define how podcasting will differentiate) while keeping levels above and below lower. This yields tens-to-hundreds of senior thinkers pulling in varied but bounded directions.
Pro tip Ask each VP to author the strategy for their domain rather than authoring it for them; their seniority supplies the pattern recognition.
- 4
Right-size teams to reduce overhead
Move away from fixed small (~7-person) full-stack pods toward larger teams (2-3x) with fewer overhead roles, so scaling doesn't multiply coordination cost.
Watch out Scaling headcount in increments of seven autonomous engineers creates a ton of coordination overhead.
In the wild
Spotify popularized small (~7), autonomous, full-stack squads. As the company scaled with a very junior workforce, full-leaf autonomy produced 100 squads with 100 strategies. They shifted to larger, more traditional teams and concentrated real autonomy at the VP level — e.g. the VP of podcasting owning that product's differentiation strategy.
→ More coherent direction and less overhead while preserving diverse, senior-led thinking; leadership no longer bottlenecked and no longer fragmented.
Common mistakes
Combining leaf-level autonomy with a junior organization
Junior teams with full autonomy lack pattern recognition and produce heat — many strategies pointing in conflicting directions with little net progress.
Centralizing all decisions on the founder/CEO
One person, however capable, becomes the throughput bottleneck; every decision must pass through them, capping the whole org's speed.
Is it for you?
Best for
Leaders of fast-scaling companies deciding where in the org chart real strategic authority should live.
Not ideal for
Very small or very early teams where a single founder making most calls is still the fastest path.
From the transcript
“if you're renting all of this expensive brain power and then you give them no room to think for themselves, that doesn't sound smart.”
“you're going to have 100 squads with 100 strategies running in 100 directions.”
“the autonomy level in Spotify now tends to be quite high at the VP level”
“scaling in increments of of seven engineers just creates a ton of overhead”
From the episode
Lessons from scaling Spotify: The science of product, taking risky bets, and how AI is already impacting the future of music
Gustav Söderström (Co-President, CPO, and CTO at Spotify)