Heuristic

Move quality checks upstream of the bottleneck

Do not spend the constraint on defects that cheaper checks can catch.

About 1 min read

Before you use it

Use when
  • When scarce capacity repeatedly rejects preventable bad inputs.

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

Why it matters

Add lightweight validation before the bottleneck for recurring failure modes, while retaining the bottleneck's judgment on risks only it can assess.

An example

Before specialist review, an automated schema check catches missing fields so expert time goes to semantic exceptions.

Check your result

The constraint receives fewer preventable defects without merely moving hidden error downstream.

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 readingMove quality checks upstream of the bottleneck

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