Pedro Arantes
HomeBlogMe

Block All Demand when WIP Reaches Its Upper Limit

You can block queues in two ways: 1. Eject the arriving job from the system. 2. Hold back the job in an upstream queue.
#product-development
Zettelkasten, November 14, 2022.

Hypotheses

  1. It takes a long time to correct a high-queue state.
  2. Queue can do enormous damage during this high-queue period.
  3. The most straightforward way to use the WIP constraint is to block all demand when it reaches its upper limit.

Arguments

It's preferable to block demands than to allow queues to reach a high-queue state because the damage a high-queue condition can cause is greater than the gains of the demands.

You can block queues in two ways:

  1. Eject the arriving job from the system.
  2. Hold back the job in an upstream queue. This approach doesn't reduce demand; it just shifts the location of the queue. In addition, it can generate economic benefits because different queues have different holding costs.

References

RecommendationsDo you want to see all posts instead?
Most of the Damage Done by a Queue Is Caused by High-Queues States
Newsletter
On Tuesday (not weekly), I publish my most recent readings and thoughts. Subscribe to my newsletter if you want to follow posts about #startups, #product-development, #mental-models, and more.

By subscribing, you agree with Revue’s Terms and Privacy Policy.