Review all installed defaults quarterly — outdated…
Schedule quarterly reviews of every default you have installed in your systems and processes, because contexts change and outdated defaults silently steer toward yesterday's goals without conscious detection.
When This Fires
- Every quarter as a scheduled maintenance event
- When you notice a system producing outputs that no longer match current needs — a stale default may be the cause
- After any major priority shift, role change, or tool migration
- When "cleanup" tasks accumulate — many are symptoms of outdated defaults
Common Failure Mode
Never reviewing defaults because they're invisible: "I set that up ages ago and it still works." It works in the sense that it executes. But does it still serve your current goals? A default that reliably does the wrong thing is worse than no default — it actively misallocates resources while giving you the feeling of automation.
The Protocol
(1) Every quarter, list all installed defaults across your systems: email rules, calendar defaults, automation scripts, app configurations, behavioral routines, workflow templates. (2) For each default, ask: "Is the goal this serves still my current priority?" If no → update or remove. (3) Ask: "Is the implementation still optimal, or have tools/processes changed?" If changed → redesign. (4) Ask: "Is this default producing the intended behavior, or has context drift made it produce something different?" If different → recalibrate. (5) Document changes made during the review. The documentation helps you notice patterns (which types of defaults decay fastest?) and prioritize future reviews.