Pre-list conditions that would invalidate each priority…
Define event-based reassessment triggers in advance by listing specific conditions that would invalidate each priority, then treat trigger activation as mandatory pause points rather than optional considerations.
Why This Is a Rule
Environmental shifts trigger immediate priority… describes what to do when environmental shifts occur (pause and reassess). This rule goes upstream: define in advance which specific conditions would invalidate each priority. This converts the reactive process (something shifts → decide whether to reassess) into a proactive system (pre-defined condition triggers → mandatory reassessment fires automatically).
The pre-definition is a pre-mortem (Ask 'Given that I compromised this value, what…) applied to priorities: "Given that priority X became invalid, what caused it?" The answer identifies the invalidation conditions. For a "launch product by Q3" priority, invalidation conditions might include: key engineer leaves, market entrant captures the niche, regulatory change blocks the approach, or customer validation data comes back negative. Each is a specific, observable condition that, if triggered, mandates reassessment.
Treating triggers as mandatory (not optional) prevents the common failure of recognizing invalidating conditions but continuing execution anyway due to sunk cost, social pressure, or momentum. "We know the market shifted, but we're already halfway through..." The mandatory pause overrides this inertia: the trigger fired, reassessment happens before execution continues.
When This Fires
- When establishing any new priority — define its invalidation conditions at the same time
- When Exit criteria must be state+date pairs… (exit criteria as state+date pairs) needs the complementary invalidation trigger
- During priority-setting sessions when you want to build resilience into the priority system
- Complements Environmental shifts trigger immediate priority… (environmental shift reassessment) with the proactive trigger definition
Common Failure Mode
No pre-defined triggers: invalidating conditions occur but aren't recognized because nobody specified what would count as invalidating. The market shifts, the team changes, the data contradicts — and execution continues because the shift wasn't explicitly connected to the priority's validity.
The Protocol
(1) For each active priority, ask: "What specific conditions would make this priority invalid or significantly less valuable?" (2) List 3-5 invalidation conditions per priority. Make them observable (Apply the camera test to triggers — if a camera can't…): not "if things change" but "if competitor X launches before us" or "if customer validation scores drop below 4/5." (3) Commit: when any listed condition occurs → mandatory pause. Not "consider pausing" but "pause execution and reassess before continuing." (4) Monitor the conditions at each regular reassessment checkpoint (Schedule reassessment checkpoints calibrated to domain…). Have any triggered? (5) If a condition triggers → apply Environmental shifts trigger immediate priority…'s zero-based reassessment immediately.