Capacity-Red Headcount Justification
Add headcount only when a days-committed-vs-days-in-quarter calculator stays red after cutting low-value work
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 85%
A method to avoid org bloat by making headcount data-driven. Each period, tally the days each person needs for committed work (including meetings, PTO, offsites/bursts) against the actual days in the quarter. If they're 'red' (more work than days), first cut low-value meetings and launches they only need to be consulted on; only if they stay red across multiple quarters do you build the business case for a new hire. It operationalizes 'wait for people to cry uncle' before hiring.
Origin
Reintroduced by Davis's Shopify manager Dean; Davis had used similar approaches at prior companies.
Core principles
- 01Bloated orgs come from hiring ahead of demonstrated, sustained overload
- 02A single red quarter is often explained by an isolated event (summit, burst, partner travel) — not a reason to hire
- 03People often won't 'scream uncle' when overloaded because they read it as weakness, so make overload visible in data
- 04First response to red is cutting low-value time, not adding headcount
How to run it
- 1
Tally committed days vs quarter days
For each person, add up days spent in meetings, PTO, offsites/bursts, optimizations and reporting, and compare the total to the number of days in the quarter.
- 2
Interpret red as overload, but check for one-offs
If someone is 'red' (more committed days than exist), ask whether it's isolated to this quarter due to a summit, burst or heavy partner travel before reacting.
Watch out Don't build a hiring case off a single red quarter caused by a one-time event.
- 3
Cut low-value time first
If red persists, first remove low-value commitments — step out of meetings you only need to be consulted on, or launches you don't need to attend every meeting for.
- 4
Build the hire case only if still red
If they remain red after cutting, and the surplus work equates to a full role, make the business case for a new hire and define what that person will own.
Pro tip Also watch for people who should be 'screaming uncle' but won't — offer coaching or resources before they burn out.
Watch out Sometimes the answer is still 'no hire' — the data may show you just need to protect people's time better.
In the wild
Davis describes managing an agency portfolio where five clients each started at $100k and grew to $2M+; rather than overload the manager, the move was to give them three clients and hire someone to take the other two.
→ Workload rebalanced by adding capacity only where scale demonstrably outgrew the person.
Common mistakes
Hiring off a single red quarter
An isolated overload from a summit or travel-heavy quarter isn't sustained demand; hiring on it creates bloat once the one-off passes.
Is it for you?
Best for
Managers deciding whether rising workload justifies new headcount versus reallocating time
Not ideal for
Teams facing sudden step-changes in demand where waiting multiple quarters would bottleneck growth
From the transcript
“my current manager Dean created this uh calculator that we look at that says how much time are you spend spending in meetings”
“and red means uh they have more work yeah more days than there are in the in the quarter”
“sometimes people want scream Uncle when they should be screaming Uncle because they think it's a sign of weakness”
From the episode
The ultimate guide to performance marketing
Timothy Davis (Shopify)