Review all installed defaults quarterly — outdated defaults silently steer toward yesterday's goals

Why This Is a Rule

Defaults — automatic settings in your tools, workflows, and behavioral systems — are among the most powerful forces shaping daily behavior precisely because they operate without conscious engagement. Your email auto-sort rules, your meeting duration defaults (30 or 60 minutes?), your project management templates, your morning routine sequence — each one silently steers behavior toward whatever goal was current when the default was installed.

The danger is that goals shift but defaults don't. You set up an automated weekly report for a project that ended six months ago. Your email rules still prioritize a client who's no longer your top account. Your calendar still blocks 2 hours for a process you've since streamlined to 30 minutes. These stale defaults consume resources (time, attention, workflow friction) while steering toward outdated objectives.

Quarterly review is the right cadence because defaults typically remain accurate for weeks to months — they don't drift daily. But every quarter, enough context changes (new priorities, new tools, new team structures) that a meaningful fraction of defaults will have gone stale. The review catches this drift before it accumulates into significant misalignment.

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.