Question
Find the bottleneck from waiting, not busyness
A constraint is revealed by system effect, not self-reported effort.
When it fits
- When every team reports being busy and each claims to be the bottleneck.
When to avoid it
- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.
A question to ask
Where does work wait persistently? · Which stage limits completed output? · What downstream stage is starved? · Would extra capacity here change system throughput?
Why it matters
Trace where work accumulates, where downstream stages starve, and which capacity change would increase end-to-end throughput. Distinguish chronic constraint from temporary incident.
An example
All teams are busy, but items consistently wait four days for one specialist review; adding coding capacity does not change completions.
Check your result
The bottleneck claim is tied to end-to-end flow evidence.
Keep this limit in mind
- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.
Connected ideas
Useful withProtect bottleneck capacity from avoidable work
Evidence and sources
Kingman's heavy-traffic result underlies a queueing approximation in which waiting increases sharply with utilization and with variability in arrivals and service.
It is a single-server heavy-traffic approximation and should be used as directional intuition, not as an exact prediction for arbitrary multi-stage work.
The Single Server Queue in Heavy Traffic · Research note metadata and established heavy-traffic formulation