Three consecutive reviews flagging the same commitment without action = system failure — resolve now, not next review
When the same commitment is flagged for action (renegotiation, deferral, or release) in three consecutive reviews without any action taken, treat this as a system failure requiring immediate resolution rather than another deferral.
Why This Is a Rule
Review systems produce two types of output: actions (commitments are renewed, modified, or released) and deferrals ("I'll deal with this next review"). A commitment that gets deferred once is normal — maybe the review didn't have enough context for resolution. Deferred twice is a signal — the commitment is uncomfortable to address. Deferred three consecutive times is an avoidance pattern: the review system is generating the same recommendation (act on this commitment) and the action system is refusing to execute it.
Three-consecutive-review inaction is a system failure, not a commitment management decision. The review system works (it keeps flagging the issue). The resolution system doesn't work (action keeps being deferred). Treating the fourth review as "maybe I'll handle it next time" perpetuates the failure — the pattern will continue indefinitely because the avoidance mechanism that deferred it three times has no reason to relent.
The forced-resolution trigger changes the mode: from "review and potentially defer" to "resolve this now, during this session, before moving to other items." The resolution options are renegotiate (change the commitment's terms), defer with a hard deadline and accountability (not another open-ended deferral), or release (end the commitment). "Review again next time" is not an option.
When This Fires
- When a commitment review identifies the same item flagged for action for the third consecutive time
- When "I'll deal with that next quarter" keeps appearing for the same commitment
- During commitment portfolio reviews when checking for stale flagged items
- Complements The zero-based commitment test: 'Would I start this today?' — 'probably not, but...' means the qualifiers are rationalizations (zero-based renewal) and Review commitments quarterly (monthly for high-stakes) — don't wait for subjective dissatisfaction, gradual drift is imperceptible (scheduled reviews) with the avoidance-detection mechanism
Common Failure Mode
Infinite deferral loop: "This volunteer role isn't working, but I'll figure it out next quarter." Three quarters later, nothing has changed. The commitment consumes resources while the discomfort of addressing it produces repeated deferral. The three-review trigger breaks the loop by converting the fourth review from optional to mandatory resolution.
The Protocol
(1) During each commitment review, track which commitments are flagged for action (renegotiate, release, or fundamentally change). (2) If the same commitment has been flagged in three consecutive reviews without action → treat this review as a forced-resolution session. (3) Forced resolution options: Renegotiate: change the terms, scope, or conditions of the commitment to resolve the issue. Make the change now, not "after discussion." Defer with hard deadline: if resolution genuinely requires more information, set a specific date by which the resolution must happen. The date is a commitment with consequences (A commitment contract needs five elements: behavior, schedule, completion criteria, duration, signature — missing any = preference, not commitment). Release: end the commitment. If three reviews couldn't produce resolution, the commitment may be irresolvable in its current form. (4) "Review again next time" is NOT an option at the three-review threshold. The pattern of deferral IS the problem.