The Ownership Engine
Ownership is manufactured by scope design first, culture second, and leader accountability third
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 92%
Most leaders try to create an ownership mentality with exhortation. Tan argues it starts structurally: if a person's scope is too thin to be meaty, no amount of culture talk will make them feel like an owner. She builds ownership in three layers — carve scope worth owning, coach an unblockable mindset, and take the blame yourself as the leader.
Origin
Melissa Tan, drawn from watching ownership dilute as Dropbox scaled from ~200 to 1,500 people, and from her decision to refuse a team-size doubling at Dropbox in order to protect scope quality.
Core principles
- 01Ownership is diluted by scale unless scope is deliberately re-carved
- 02Scope should be split by meaty problems or funnel areas, not by page or component
- 03Being blocked is a starting condition, not an excuse — 'did I exhaust all the options?'
- 04Headcount that fragments scope reduces both impact and recruiting appeal
- 05As the leader, every failure on the team is yours first
How to run it
- 1
Carve scope people are excited to own
Before adding people, define the scope each person will own and run independently. For growth teams, split by meaty problems to solve or by funnel area (activation, monetization) — never by 'you own the checkout flow.'
Pro tip Use recruiting as the test: would a strong candidate be excited to own this scope? If not, the scope is too thin.
Watch out Adding headcount that fragments scope into slivers makes both retention and hiring harder, even if the ROI math looks good.
- 2
Coach the unblockable mindset
Growth is cross-functional, so people will constantly be blocked by design, engineering, or a core PM who owns the surface. Train the reflex: instead of feeling disempowered, ask 'what is everything I can do, and did I exhaust all the options?'
- 3
Lead by example and absorb the failures
Visibly do the unblocking work yourself, and when something on the team goes wrong, be the first to say you are ultimately responsible and it was a failure or oversight on your side.
Watch out Taking on unowned work yourself is how leaders overextend — see the timeboxing discipline in the team-first pattern.
In the wild
Finance saw each growth PM was bringing in over a million in ARR per year from experiments and proposed doubling the team to double the ARR. Tan pushed back hard, because doubling would mean splitting scope into slivers — one PM owning just the checkout flow — which would neither be interesting enough for the team nor attractive to the people she wanted to recruit.
→ Scope stayed meaty; the linear headcount-to-ARR extrapolation was rejected as a false model.
Common mistakes
Extrapolating impact linearly with headcount
The finance logic 'each PM makes $1M, so double the team' ignores that the per-person impact came from owning a meaty problem. Doubling the team shrinks each scope and each person's ceiling.
Preaching ownership without fixing scope
As companies scale, ownership dilutes structurally because 'there is somebody else' now. Culture messaging cannot restore what the org chart removed.
Is it for you?
Best for
Managers scaling a team past the point where everyone wore five hats, deciding whether to add headcount
Not ideal for
Teams where the work genuinely is narrow, repetitive execution and scope cannot be meaningfully enlarged
From the transcript
“I think it first starts with defining the scope that everyone is going to own and drive, right?”
“the finance team looked at our metrics and saw that each growth PM was bringing over a million in ARR per year”
“And so, I actually pushed back significantly.”
“if things don't go right in my team, I'm the first one to say that ultimately I'm responsible and it's a failure or oversight on…”
From the episode
Building high-performing teams
Melissa Tan (Webflow, Dropbox, Canva)