Operations & Delivery

Lesson 3 · Planning

Capacity & utilization

A team that is 100% busy is slow at everything. Slack buys responsiveness.

It seems efficient to keep everyone fully busy. It is not. Where work arrives unpredictably and varies in size, waiting time grows sharply as utilization approaches 100%. In the simplest queueing model the wait is proportional to ρ ÷ (1 − ρ), where ρ is utilization: a factor of 1 at 50%, 4 at 80%, 9 at 90% and 19 at 95%.

That is why a team running at 95% is slow to respond to anything: urgent requests queue behind planned work. Slack is not waste; it is what buys responsiveness. Teams that must react — platform, reliability, support — need more headroom than teams with a steady, plannable backlog.

Capacity planning starts from realistic availability. An engineer is not available for project work 40 hours a week: meetings, on-call, interviews, support and leave take a large share. Plan with a focus factor — project hours over total hours — measured from your own history. And plan headcount with lead time in mind: hiring plus ramp-up means new capacity arrives months after approval.

Picture it

A platform team of five is scheduled at 100% on roadmap work. Every request from another team waits weeks, so those teams build workarounds. The manager reserves 20% of capacity for requests. Roadmap output drops slightly; request turnaround falls from three weeks to three days, and two duplicate internal tools are deleted.

Key formulas & frameworks

Queue wait factor
ρ ÷ (1 − ρ), where ρ is utilization
Focus factor
Project hours ÷ Total hours
Available capacity
People × Hours × Focus factor
Lead time to capacity
Hiring time + Ramp-up time

Try it — Utilization & queues

Queue wait factor

4.0×

Slack

20%

The wait factor is ρ ÷ (1 − ρ): how long work waits relative to how long it takes to do. From 80% to 90% utilization it more than doubles.

1.0×
50%
1.5×
60%
2×
70%
4×
80%
6×
85%
9×
90%
19×
95%

Wait factor at each utilization level. The curve is why a team planned at 100% is slow to respond to anything unplanned.

Practice

Score: 0 / 5

Question 1

Q1.A team runs at 80% utilization. What is the queue wait factor, ρ ÷ (1 − ρ)?

Question 2

Q2.Six engineers work 40 hours a week with a focus factor of 0.6. How many project hours are available per week?

Question 3

Q3.Utilization rises from 90% to 95%. What happens to the queue wait factor?

Question 4

Q4.Keeping every engineer 100% utilized minimizes delivery time.

Question 5

Q5.Which team needs the most slack in its plan?

Up nextBuild vs buy & vendors

Next lesson