← BackSee all toolsCapacity and Utilization ModelWorking demo · sample data · shows a method I used, not a real event
Capacity · true vs logged hours

Capacity and Utilization Model

Is the team the right size for the work? A model that separates true from logged utilization and compares hold, reduce and retrain.

I used this model for team capacity decisions. The inputs are fictional and no individual is described.

The model

Is the team the right size for the work?

Utilization is real demand divided by real capacity. Set the team and the demand. Padding in logged hours makes a team look busier than it is, so the page shows both numbers.

63%Utilization as reported
50%Utilization, true
Under-usedZone
0507085100%+

What if…

OptionTrue utilizationRead
Hold the team50%Room to absorb
Reduce by one seat63%Room to absorb
Retrain one seat into adjacent work (+20 hours of demand)63%Room to absorb

The rules

Five rules I use for capacity decisions.

  1. Aim for a clean 80%. Not 100%: a team with no slack cannot absorb a bad week, train or improve.
  2. Measure true, not logged. Logged hours drift up when time is the thing being judged.
  3. Name the work before you keep the seat. Every seat needs named work, an owner, a metric and a review date.
  4. Look sideways before you cut. If behaviour and learning capacity are strong, a retrain into adjacent work is cheaper than a restart.
  5. Re-run it every quarter. Demand changes faster than org charts.

Reading the zones

What each band means.

Below 50%

Under-used

Find work, rebalance, or accept that the seat has no demand yet.

70 to 85%

Target band

Enough slack to absorb surprises, enough load to justify the seat.

Above 95%

Over-loaded

Errors, burnout and single points of failure. Add capacity or cut scope.

More in Operating Model & Governance

See all tools