Schedule reassessment checkpoints calibrated to domain volatility — spontaneous awareness can't detect gradual priority drift

Why This Is a Rule

Priorities drift as environments change — but the drift is gradual enough to escape spontaneous awareness (Review commitments quarterly (monthly for high-stakes) — don't wait for subjective dissatisfaction, gradual drift is imperceptible). A priority that was perfectly aligned in January may be misaligned by April because the competitive landscape shifted, a team member left, or a new opportunity emerged. Without scheduled reassessment, the misaligned priority continues receiving resources because nobody triggered a re-evaluation.

The volatility calibration is the key design principle: reassessment frequency should match how fast the domain changes. High-volatility domains (startup execution, crisis management, rapidly changing markets) need weekly reassessment because priorities can shift dramatically within days. Low-volatility domains (long-term skill development, stable organizational roles) need quarterly reassessment because priorities change slowly. Matching frequency to volatility prevents both under-assessment (priorities drift undetected) and over-assessment (stable priorities get needlessly re-litigated).

This is Schedule reviews at intervals shorter than natural feedback latency — forcing functions tighten loops that can't be structurally accelerated (forcing functions at intervals shorter than feedback latency) applied specifically to priority management: the reassessment checkpoint is a forcing function that fires before priority drift compounds into significant misallocation.

When This Fires

• When establishing a priority management system for any domain
• When priorities haven't been explicitly reviewed in longer than the domain's volatility warrants
• When work feels misaligned but you can't pinpoint when the misalignment started — it drifted between reviews
• Complements Review commitments quarterly (monthly for high-stakes) — don't wait for subjective dissatisfaction, gradual drift is imperceptible (commitment renewal cadence) with the priority-specific reassessment schedule

Common Failure Mode

Uniform quarterly cadence for all domains: "I'll review everything each quarter." If your startup's market shifts weekly, quarterly review means 12 weeks of potential misalignment between reviews. If your personal health goals are stable, weekly review wastes time re-evaluating things that haven't changed.

The Protocol

(1) For each domain you manage priorities in, assess volatility: how fast does this domain change? High volatility (startup, crisis, active project with many unknowns) → weekly reassessment. Medium volatility (established business, evolving team, dynamic market) → monthly reassessment. Low volatility (personal development, stable role, long-term health) → quarterly reassessment. (2) Schedule each reassessment as a recurring calendar event with the appropriate cadence. (3) At each checkpoint: are the current priorities still correct given what's happened since the last review? Apply The zero-based commitment test: 'Would I start this today?' — 'probably not, but...' means the qualifiers are rationalizations (zero-based question) and Tasks inherit their parent objective's priority — trace each task to 'which ranked objective does this advance?' before scheduling (priority inheritance check). (4) If volatility changes (stable domain becomes turbulent) → increase reassessment frequency immediately.