Capacity & Utilization
How much a resource could produce versus how much it actually does - and why chasing 100% utilization can quietly backfire.
What it is
Capacity is the most a resource - a machine, a store, a team, a plane - could produce or serve in a given period if fully used. Utilization is how much of that capacity you are actually using, expressed as a share. The pair matters because a lot of operational and profitability questions turn on the gap between the two: unused capacity is cost you are already paying for with no output to show for it, while capacity you have run out of is demand you are turning away. Understanding this lets you see whether a business's problem is too little demand for its capacity, too little capacity for its demand, or a mismatch in timing between the two.
When to use it
Use it in operations, cost, and profitability cases involving fixed assets or staffed resources - factories, hotels, airlines, clinics, restaurants, professional-services teams. It is the right lens for 'should we expand?', 'why are unit costs so high?', and 'can we handle more demand?'. It connects directly to fixed-cost absorption: low utilization spreads fixed costs over few units, so unit cost balloons. It is less relevant where there is no meaningful fixed capacity. Do not treat higher utilization as automatically better - past a point it removes the slack needed to absorb variability and can worsen service and reliability.
How to apply it
Define the capacity carefully - in what units, over what period, and is it theoretical maximum or a realistic sustainable level after downtime and breaks? Compute utilization as actual output divided by that capacity. Then read the number in context: low utilization signals a demand or scheduling problem and heavy fixed-cost drag per unit; very high utilization signals you may be leaving demand unserved and running with no buffer. Watch the timing dimension too - average utilization can look fine while peaks are turning customers away and troughs sit idle. The goal is to match capacity to demand sensibly, not to maximize a utilization percentage for its own sake.
Common mistakes
The most seductive error is treating 100% utilization as the goal; near-full utilization destroys the slack that absorbs demand spikes and equipment downtime, so queues, delays, and breakdowns multiply. Another is comparing utilization to a theoretical maximum that ignores maintenance, breaks, and setup, which flatters the number. People also average away the peaks - a 70% average can hide an overwhelmed Friday and a dead Tuesday. And they forget the fixed-cost link: they diagnose 'high unit cost' as a cost problem when it is really a low-utilization problem that expansion would worsen, not fix.
Example
A boutique hotel with 100 rooms reports it is 'busy' at 85% average occupancy but still loses money. Looking at capacity and utilization more closely: weekends run at 100% and turn guests away, while midweek sits near 55%. The average hides a mismatch - lost revenue at the peak, idle rooms carrying full fixed cost midweek. Building more rooms would raise peak capacity but deepen the midweek drag, so it is likely the wrong move. The real levers are shifting demand into the trough (midweek pricing, corporate packages) and capturing more of the peak, not adding capacity. The capacity-utilization lens reframes an 'expand?' question into a 'smooth the demand?' one.
Practice it
Practice on operations and profitability cases by separating theoretical from realistic capacity, computing honest utilization, and always checking the peak-versus-trough pattern behind an average. The skill to build is linking utilization to fixed-cost absorption and resisting the reflex that treats a higher utilization number as automatically better.