U — Unspoken default

Doing nothing, waiting, or quitting is secretly steering your decision because nobody has named it as an option.

Your team has debated a new project management tool for two months. Every meeting compares Asana against Linear, feature by feature. Meanwhile the actual outcome keeps happening: you continue limping along with the spreadsheet nobody defends, because no decision has been made. The spreadsheet is winning every vote without ever appearing on the ballot.

Unspoken default is the diagnosis for exactly this: continue, do nothing, wait, stop, or exit is shaping the decision but has never been named as an option. The cue is a decision that keeps getting deferred while life quietly proceeds down one path. The fix takes two minutes: write the default explicitly onto the list ("Option C: keep the spreadsheet for another quarter"), then evaluate it with the same rigor as the shiny candidates. What are its costs, its owner, its exit condition? What visibly changes is that the deferral loses its innocence. Either the default survives scrutiny, in which case you have decided on purpose, or its hidden costs become undeniable and the stalled comparison suddenly resolves. Skip this move only when the default is already on the table and being argued for openly; then your problem is comparison, not visibility.