Same constraint for three weeks straight = structural…
When the same operational constraint appears in three consecutive weekly reviews, treat it as a structural issue requiring architectural change rather than tactical adjustment, escalating it from the weekly action item to a dedicated project.
When This Fires
- The same constraint appears in your bottleneck journal for three consecutive weeks
- A weekly review surfaces the same "action item" for the third time
- Tactical fixes keep addressing symptoms while the root cause persists
- Your team's retrospective keeps identifying the same blocker
Common Failure Mode
Continuing to apply tactical patches week after week: "We'll try a different workaround this time." Each tactical patch provides temporary relief, creating the illusion of progress. But the constraint returns the following week because the architecture that produces it hasn't changed. The infinite tactical patching loop is the most common way structural problems avoid resolution.
The Protocol
During weekly review: (1) Compare this week's constraints to the previous two weeks. (2) If the same constraint appears in all three: escalate. (3) Create a dedicated project with a clear scope: "Redesign [process/tool/structure] to eliminate [constraint]." (4) Allocate focused time — this is a project, not an action item. (5) The project's success metric: the constraint no longer appears in weekly reviews.