Headcount & Capacity Planning

Headcount conversations fail when they start with “we need more people” and end with a number. Strong leads start with the work: streams of change, service ownership, interrupt load, and the outcomes that matter this half. Capacity planning turns desire into a plan stakeholders can fund or cut with eyes open.

You will not always get the hires you want. Your job is to make trade-offs explicit: what ships if we stay flat, what slips if we add scope, and what burns people if we pretend math is optional.

Capacity is not headcount

Headcount is seats. Capacity is the fraction of time that can do planned product and tech work after meetings, on-call, hiring, and drag. A team of eight with heavy interrupts can have less shipping capacity than a team of five with clean ownership.

• Planned capacity: roadmap and committed projects.
• Interrupt capacity: incidents, support, drive-by asks.
• Investment capacity: debt, platform, hiring, learning.
• Unavailable capacity: PTO, leave, ramp-up, part-time.

A simple capacity model

1. List the work streams for the next quarter (product, reliability, platform, keep-the-lights-on).
2. Estimate size in engineer-weeks, not story points theater. Ranges are fine.
3. Compute available engineer-weeks: people × weeks × focus factor (often 0.6-0.75).
4. Subtract known ramps, PTO, and on-call weeks.
5. Compare demand vs supply. Cut or sequence until the plan is honest.
6. Name the explicit “won’t do” list so scope does not sneak back in chat.

When to ask for headcount

Hire when the constraint is sustained demand against a clear stream, not when one bad quarter of meetings made everyone tired. Bring evidence: lead time, WIP, on-call load, roadmap commitments, and risks of staying flat.

• Role brief: problem to solve, not a stack shopping list only.
• Why now: what fails if we wait a quarter.
• Alternatives considered: scope cut, vendor, platform leverage, rebalance.
• Ramp plan: who onboards, when the seat becomes net positive.
• Success signal: what changes in 6 months if the hire works.

Allocation patterns that protect delivery

• Keep a stability reserve: do not plan 100% of capacity to roadmap.
• Limit concurrent major bets per team (often one primary, one secondary).
• Separate stream ownership from temporary swarm work with an end date.
• Fund platform or debt with a fixed percentage when pain is chronic.
• Rebalance when topology is wrong before you add more people to a broken interface.

Adding people to a confused ownership map multiplies confusion. Fix the map, then staff the streams.

Conversations with your manager and finance partners

1. Lead with outcomes and risks, then the capacity math.
2. Offer scenarios: stay flat / +1 / +2 with different delivery shapes.
3. Be ready to recommend the cut if headcount is denied.
4. Never accept infinite scope with finite capacity in silence.
5. Review the plan monthly; capacity plans rot faster than roadmaps.