Reconfigure bad tool defaults during high-capacity periods — don't override them through willpower during every execution

Why This Is a Rule

A bad default that you override every time is a repeated willpower tax: you pay the cognitive cost of noticing the default, deciding to override, and executing the override at every interaction. Over hundreds of interactions, this tax accumulates into significant cognitive overhead. The default should be changed once, during a calm high-capacity moment, so that every future interaction flows through the correct behavior without requiring override.

The "high-capacity period" timing is critical because default reconfiguration requires deliberate thought: you need to find the setting, understand the options, choose the right value, and test that the change works. During execution (when you're trying to get work done), this deliberation is a distraction that competes with the primary task. During a dedicated configuration session (weekend morning, review session, admin block), the deliberation is the task.

This is Design weekly adjustments as structural changes (move blocks, change environments, create defaults) — persistent patterns are system problems, not motivation problems's structural intervention principle applied specifically to tool configuration: when the same frustration recurs because of a default, stop overriding it with willpower and change the default itself.

When This Fires

• When you notice overriding the same tool default repeatedly
• When a tool behavior annoys you every time but you "work around it"
• During weekly reviews when Start weekly reviews with "What did my tools help me produce?" before reviewing configuration — anchor evaluation in outcomes, not activity reveals tool friction as an output barrier
• Complements Set calendar default duration to your actual most-common meeting length — convert repeated duration decisions into one-time pre-commitment (calendar default configuration) with the general principle for all tool defaults

Common Failure Mode

Permanent workaround: overriding a bad default 5 times per day for 2 years (3,650 overrides) instead of spending 5 minutes changing the setting. Each override feels trivial ("it's just one click"), but the accumulated cognitive cost is enormous — and the 5-minute fix was available the entire time.

The Protocol

(1) When you notice overriding a tool default for the second time: note it. Don't fix it now — you're in execution mode. (2) Add "reconfigure [tool] default for [behavior]" to your admin/configuration task list. (3) During your next high-capacity period (admin block, review session, or dedicated configuration time): locate the setting, change the default, test the change. (4) Verify over the next few days: does the new default eliminate the override? If yes, the fix is permanent. If no, the setting was wrong — adjust during the next admin block. (5) Track: how many default overrides did you eliminate this month? Each eliminated override is a permanent cognitive savings.