Scale tool evaluation effort to switching cost, not feature count — maximum deliberation for high lock-in, minimal for easily replaced tools

Why This Is a Rule

People spend equal deliberation time on all tool choices, regardless of how consequential the choice actually is. Choosing a note-taking app (high switching cost: years of notes, muscle memory, workflow integration) gets the same 2-hour evaluation as choosing a PDF reader (low switching cost: swap in 5 minutes). Meanwhile, the note-taking app choice consumes the same 2 hours as the color of your calendar (zero switching cost: change in 30 seconds). The deliberation is allocated to whatever feels complex or produces anxiety, not to what's actually irreversible.

Switching cost is the correct calibration variable because it determines the real-world consequence of a wrong choice. A high-switching-cost tool chosen poorly produces years of friction (data migration, muscle-memory retraining, workflow restructuring). A low-switching-cost tool chosen poorly produces minutes of inconvenience (install a different one). The deliberation investment should match the consequence: extensive evaluation for high switching costs, minimal evaluation for low switching costs.

This is Jeff Bezos's "one-way door vs. two-way door" distinction applied to tool selection: one-way doors (high switching cost) deserve careful deliberation. Two-way doors (low switching cost) deserve quick choices with the option to reverse. Most tool choices are two-way doors that get treated as one-way doors because of anxiety about "choosing wrong."

When This Fires

• When deciding how much time to spend evaluating a new tool
• When tool evaluation is consuming time disproportionate to the tool's importance
• When Pick a tool with 5 minimum requirements, select the first that meets them, commit for 90 days — satisfice, don't maximize's satisficing approach needs calibration for when to apply it more or less strictly
• Complements Pick a tool with 5 minimum requirements, select the first that meets them, commit for 90 days — satisfice, don't maximize (5-requirement satisficing) with the meta-rule about how much evaluation effort any tool deserves

Common Failure Mode

Anxiety-driven evaluation: spending 20 hours researching task management apps (low switching cost: you can migrate your task list in an afternoon) while spending 30 minutes choosing a cloud storage provider (high switching cost: 10 years of files, automated backups, sharing links). The anxiety about "choosing the wrong task app" drives excessive evaluation; the boring cloud storage choice gets insufficient deliberation.

The Protocol

(1) Before evaluating any tool, estimate its switching cost: "If I choose wrong, how hard is it to switch?" Low (minutes to hours: PDF readers, browser extensions, simple utilities) → spend 15 minutes, pick the first adequate option (Pick a tool with 5 minimum requirements, select the first that meets them, commit for 90 days — satisfice, don't maximize). Medium (days: email clients, calendar apps, task managers) → spend 1-2 hours, compare 3 options against requirements. High (weeks to months: note-taking systems, CRM, development frameworks) → spend 4-8 hours, compare thoroughly, test with real data, commit for 90 days (Pick a tool with 5 minimum requirements, select the first that meets them, commit for 90 days — satisfice, don't maximize). (2) The switching cost estimate should consider: data portability, muscle memory investment, workflow dependencies, and integration complexity. (3) For high-switching-cost tools: check data export capabilities before committing. A tool with excellent features but no export is a trap. (4) For low-switching-cost tools: just pick one and start using it. If it doesn't work, switch tomorrow. The deliberation time you save goes to actual productive work.