One-in-one-out for option sets — adding a new option…

Implement one-in-one-out constraints where adding a new option requires removing an existing one, preventing option accumulation from eroding reduction benefits over time.

When This Fires

When you've curated an option set (Limit recurring low-stakes decisions to 3-7 options…) and want to prevent it from expanding back
When you notice a previously reduced domain has silently grown beyond its target range
When someone recommends a new option and you feel the pull to "just add it"
When periodic reviews reveal option-set sizes exceeding their design targets

Common Failure Mode

Exception creep: "I'll add this one without removing anything, just temporarily." Every exception is temporary in intention and permanent in practice. Within six months, the "temporary" additions have doubled the set size. The constraint must be absolute for routine domains — the moment you allow exceptions, the maintenance protocol is effectively disabled.

The Protocol

(1) For each curated option set (Limit recurring low-stakes decisions to 3-7 options…), establish a cap: "My lunch rotation is 5 restaurants." (2) When a new option appears, apply the swap test: "Which of my current 5 would I drop for this?" (3) If you can identify a clear swap → make it. Remove the old, add the new. The set stays at 5. (4) If you can't identify a swap → the new option isn't better than your worst current option. Decline it. (5) Conduct quarterly audits: count each curated set. If any exceeds its cap, immediately reduce back to target by dropping the weakest options.