Ops Capacity Toolkit
For when the team is carrying more than it can sustain.
- Time
- 60 minutes monthly plus weekly stress signal review.
- Who
- Engineering manager, support/on-call owner, product counterpart, and operations/finance partner.
- Decide now
- Cut, re-order, or re-staff work so the reliability floors hold.
- What it gets you
- A capacity plan that protects reliability and catches overload before it becomes an incident.
- What you leave with
- Capacity plan with a reliability-floor checklist and an escalation dashboard.
What to do at each pace
- • Do now in tighter conditions: Hold new hires unless the role unblocks committed delivery, and move 10-20% of sprint capacity to reliability and churn defense.
- • Do now in easier conditions: Loosen buffers only where the stress indicators have stayed green for two cycles and reliability coverage is unchanged.
- • Go ahead when: Add scope only when load stays inside the agreed band and someone is named each week to own delivery risk.
- • Pause if: Stop adding roadmap scope when overload lasts two cycles or on-call load or service levels degrade.
- • Restart when: Go back to protecting capacity when service levels or on-call load cross their limits; resume planned hiring after two improving weekly briefs.
By pace: When conditions say slow down, protect reliability capacity; when they say speed up, move spare capacity into growth work.
Prep checklist
- • Compile on-call load, incident trend, and delivery throughput for the last 4-6 weeks.
- • List planned work that assumes additional capacity not yet staffed.
- • Define the reliability floors that cannot be traded away in the next planning window.
Run sequence
Measure load
Objective: Quantify demand on people/systems versus sustainable throughput.
Prompts
- • Which teams are consistently above healthy on-call or delivery load?
- • Which commitments assume best-case capacity?
Deliverable: Capacity stress test by team with red/yellow/green status.
Protect the floors
Objective: Lock service and reliability floors before adding new scope.
Prompts
- • Which service levels cannot be traded away this quarter?
- • What planned work should pause when a floor is breached?
Deliverable: Service-level floor checklist tied to roadmap rules.
Escalate early
Objective: Create visibility loops before capacity issues become incidents.
Prompts
- • What weekly indicator predicts stress two sprints ahead?
- • Who receives escalation when overload persists for two cycles?
Deliverable: Escalation dashboard used in leadership review.
Signs it worked
- • At least one overload source is removed or re-sequenced each cycle.
- • A breached reliability floor triggers roadmap triage the same week.
- • Leadership can see forward-looking capacity risk two sprints out.
What's in this toolkit
Common mistakes to avoid
- • Assuming normal capacity under stress