Cognitive Biases · Growth Library
Check Whether Familiarity Is Driving a Low-Stakes Choice
Compare the default with one viable alternative before keeping it automatically.
Try this
Name the default, write the criterion that matters, identify one viable alternative, compare the two on that criterion and any important constraint, then keep the default or try the alternative for a stated reason. Use this only for ordinary low-stakes choices.
Check-in: What was the default, what criterion mattered, what alternative did I compare, and why did I keep or change the choice?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: The inherited article contained fabricated prototype results, invented satisfaction changes, unsupported mechanism claims, arbitrary trial counts and universal statements about cues and habit formation. The effective public record is a low-stakes decision check: identify the familiar default, name the criterion that matters, compare one viable alternative and update the default only when the comparison produces a concrete reason.
Defaults are useful because they reduce repeated decision work, but a default can outlive the reason it was chosen. This protocol is a small check for ordinary reversible choices: make the familiar option explicit, compare it with one realistic alternative, and keep or change the default because of a concrete criterion.
1. Name the default
State what you are about to choose simply because it is the usual option. Do not assume that familiarity is a problem by itself. The first step is only to make the current default visible.
2. State the criterion that matters
Choose the reason that should drive this decision: cost, compatibility, reliability, time, quality, effort, preference, reversibility, or another real constraint. Avoid changing the criterion after seeing which option wins.
3. Compare one viable alternative
Pick an alternative that could realistically replace the default. Compare both options on the stated criterion and note any constraint that would make the alternative impractical. Unknown information stays unknown rather than being filled with a guess.
4. Keep or update the default deliberately
If the familiar option still fits, keep it and record why. If the alternative is preferable and the change is reversible, try it and note what you learned. For higher-stakes decisions, move to a more complete review rather than relying on this quick check.
Questions to consider
Do I need to choose the unfamiliar option?
No. The familiar option may still be the better choice. The purpose is to make the reason visible, not to reward novelty.
What kinds of decisions fit this protocol?
Use it for ordinary reversible choices such as tools, routes, formats, routines, vendors with low switching cost, or ways of organizing work. Do not use casual experimentation as a substitute for proper review in medical, legal, safety-critical or major financial decisions.
How many alternatives should I compare?
Start with one viable alternative when the problem is automatic defaulting. If the decision is important enough to require broader option generation, use a fuller decision process instead of turning this check into a large comparison exercise.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-09-10 · reviewed · Brali claim cleanup agent Source: protocol-content-overrides-claim-cleanup-batch-5.json
Replace fabricated prototype outcomes, invented satisfaction changes, mechanism claims, arbitrary experiment counts and universal statements about cues or habit formation with a bounded low-stakes choice check.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-09-10: reviewed by Brali claim cleanup agent; evidence state is
practical.
Canonical source record · Evidence state: practical.