Environmental shifts trigger immediate priority…
When environmental conditions shift (personnel changes, market movements, health events, new opportunities), pause execution and run the zero-based question on each current priority before resuming work.
Why This Is a Rule
Scheduled reassessments (Schedule reassessment checkpoints calibrated to domain…) catch gradual drift. Event-triggered reassessments catch sudden shifts. When a key team member leaves, a competitor launches a new product, a health event changes your capacity, or an unexpected opportunity appears, the environment has changed faster than any scheduled review can catch. Continuing to execute on pre-shift priorities means allocating resources to a world that no longer exists.
The "pause execution" instruction is counterintuitive during shifts — the instinct is to work harder, not to stop and reassess. But working harder on the wrong priorities after an environmental shift compounds the misallocation. A 30-minute reassessment that redirects effort to the new reality is infinitely more valuable than 30 minutes of continued execution on displaced priorities.
The zero-based question (The zero-based commitment test) is the right tool for post-shift reassessment because environmental changes can invalidate priorities that were correct yesterday. "Knowing what I know now" — with the shift factored in — produces different answers than last week's assessment. Running the question on each priority either confirms it still holds (in the new environment) or reveals it's been invalidated.
When This Fires
- Immediately after any significant environmental change (personnel, market, health, opportunity)
- When the instinct is to "keep pushing" despite a changed landscape
- When Major transitions require full feedback loop recalibration… (major transition recalibration) applies at the priority level specifically
- Complements Schedule reassessment checkpoints calibrated to domain… (scheduled reassessment) with the event-triggered reassessment
Common Failure Mode
Continuing execution on inertia: "The CEO just resigned but let's stay focused on Q2 goals." The Q2 goals were set with the CEO's vision as a premise. The premise changed; the goals may need to change too. Continuing execution without reassessment risks investing the most intense effort in precisely the quarter where the goals are most likely to be wrong.
The Protocol
(1) When a significant environmental shift occurs, immediately pause current execution (not permanently — for reassessment). (2) List all current priorities. (3) For each, apply the zero-based question (The zero-based commitment test) with the shift factored in: "Given that [shift] has occurred, would I still choose this priority today?" (4) Priorities that pass → confirm and resume execution. (5) Priorities that fail → immediately flag for renegotiation, deferral, or replacement. Do not resume execution on invalidated priorities. (6) The reassessment should take 30-60 minutes — a small investment that prevents weeks of misallocated effort on post-shift priorities that no longer hold.