When the Constraint Shifts
When you resolve the current constraint, a new one emerges. That is the system working, not failing.
The factory version: you fix the slowest machine, and now a different machine is the bottleneck. Which means the first one is no longer holding you back. That is what progress looks like from the inside.
Signs it has moved
Section titled “Signs it has moved”- The weekly review keeps showing the constraint as “addressed” but you are not seeing the throughput improvement you expected
- A new bottleneck is visible that was not there before
- The business feels different — the old problem is resolved and something else has taken its place
What to do
Section titled “What to do”Tell the system: “I think the constraint has shifted. Let’s re-assess.”
It checks your current constraints.md against your recent weekly reviews and helps you work out whether the constraint genuinely moved or whether you are seeing a different symptom of the same one. That distinction matters — chasing a symptom as though it were a new constraint is how people end up busy and stuck.
If it has genuinely shifted, the system runs the change sequence again: new Evaporating Cloud, new Future Reality Tree, new Negative Branch Reservations, new Strategy & Tactics Tree.
What this looks like over time
Section titled “What this looks like over time”You might start with a constraint around lead generation. You build and execute. Leads arrive.
Now the constraint moves to conversion — inquiries are coming in but not becoming clients. You build a listing conversation process. Conversion improves.
Now it moves to capacity — you are closing but drowning in operational work. You document and delegate.
Each cycle makes the business more structured, more predictable, more profitable. The constraint never disappears. It moves to the next weakest link, and every time it moves the business is stronger than it was.