Draft, open for argument

There is always a next constraint

Relieving one constraint reveals the next. That is the work.

The rule

Fix the slowest query in an application and the code paths that waited on it rush to the next limit: a lock, memory, another query. A delivery line behaves the same way. Expect it, budget for it, and treat each new pile as the next item on the list.

Signs you are breaking it

  • Surprise that CI is slow after agents tripled the tests.
  • A transformation project with an end date.
  • Blaming the last tool when a new queue appears.

In Lights Out

The shift report at the end shows how your constraint moved from station to station.

Back to all factors