Single-Owner Review Limits
Cap reviews, approvals, and meeting size so one accountable owner drives the pace
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 86%
A concrete operating rule to kill approval bottlenecks: no more than three reviewers on a piece of work with only one of them blocking, and any meeting over ten people forces the host to remove attendees and write better decision notes. Replacing daisy-chains of approvals with a single accountable owner sharply increases team agency, pace, and quality.
Origin
An operational change Costello introduced at Asana after getting 'really aggressive about being real' regarding how many reviews and approvals a piece of work truly needs.
Core principles
- 01A daisy-chain of approvals destroys agency and pace.
- 02One person should hold the book and be responsible for how the work moves forward.
- 03Distinguish who is blocking from who is merely informed, a stakeholder, or a decision-maker.
How to run it
- 1
Assign one accountable owner
Give a single person the book — responsibility for how the work moves forward and for connecting the dots — rather than spreading accountability across a chain.
- 2
Limit to three reviewers, one blocker
Allow no more than three people assigned to review a given body of work, and let only one of them block whether it advances to the next stage.
Pro tip Be explicit about roles: blocking approver vs. informed people, stakeholders, and decision-makers.
- 3
Cap meetings at ten people
If a meeting has more than ten attendees, require the host to kick people out and write better decision notes instead.
In the wild
Asana decided they didn't want a daisy-chain of approvals — they wanted one person the book could stop with, responsible for how the work moved forward, plus hard limits on reviewers per work item and people per meeting.
→ It created a lot more agency and pace within working teams and changed both the speed and quality of the work.
Common mistakes
Requiring a daisy-chain of approvals
Multiple sequential approvers strip agency and slow work; a single accountable owner restores pace without losing quality.
Letting meetings balloon past ten people
Oversized meetings dilute decision-making; forcing removal and better written notes keeps decisions crisp and fast.
Is it for you?
Best for
Scaling product/engineering orgs where approval bottlenecks and bloated meetings are slowing delivery
Not ideal for
High-risk decisions (legal, safety, compliance) that genuinely require multiple blocking sign-offs
From the transcript
“no more than three reviews on a given piece of work where people are blocking one approver and if a meeting has more than 10…”
“we don't want a daisy-chain of approvals we just want one person with him the book can stop with them and they can be responsible…”
From the episode
How to ask the right questions, project confidence, and win over skeptics
Paige Costello (Asana, Intercom, Intuit)