Reconfigure bad tool defaults during high-capacity periods…
When tool defaults consistently produce undesired behaviors, reconfigure the default settings during high-capacity periods rather than overriding them repeatedly through willpower during execution.
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… reveals tool friction as an output barrier
- Complements Set calendar default duration to your actual most-common… (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.