Question

Find the bottleneck from waiting, not busyness

A constraint is revealed by system effect, not self-reported effort.

About 1 min read

Before you use it

Use when
  • When every team reports being busy and each claims to be the bottleneck.

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.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

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.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingFind the bottleneck from waiting, not busyness

Evidence and sources
Provides context

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details