Reversibility

Core rule: match process depth to undo cost. Most decisions are cheaper to reverse than they look; irreversible ones deserve deliberation and staged commitment.

When to Use

• Uncertain how much analysis a decision deserves (tech, process, product, org)
• Tempted to committee a low-blast-radius choice, or to rush a high-lock-in one
• Can redesign the move (pilot, flag, abstraction, time-box) to lower undo cost
• High-stakes choice where acting vs waiting have asymmetric recovery profiles

When NOT to Use

• Already classified this session—decide at matched depth; do not re-label forever
• Trivial two-way calls (names, local refactors) where deciding is cheaper than classifying
• Externally forced move with no optionality (hard deadline, contract, regulation)
• Correctness gates (security, data integrity) that need the right answer, not speed theater

Procedure