Cognitive Biases · Growth Library
Evaluate Options Against Fixed Criteria Before Comparing Them
Keep the criteria stable so side-by-side differences do not rewrite the decision.
Try this
Write the must-have constraints and relevant preferences before opening the comparison, evaluate each option against that same list, mark missing information as unknown rather than pass or fail, remove options that clearly violate a must-have, and compare the remaining trade-offs only after the individual evaluations are recorded.
Check-in: Did I keep the same criteria across options, which unknown could still change the result, and which remaining trade-off actually matters?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: The inherited decision article mixed unsupported cognitive mechanisms with fabricated team outcomes, invented satisfaction and speed effects, arbitrary universal timeboxes and score scales, and examples in higher-stakes domains. The effective public record is narrowed to criteria stability: define requirements first, evaluate each option against the same list, keep unknowns explicit, remove clear must-have failures, then compare meaningful trade-offs.
Comparisons become noisy when the standards change while the options are being inspected. A simple way to control that drift is to define the decision criteria first, evaluate each candidate against the same list, and postpone the final trade-off comparison until the individual records are complete.
1. Freeze the initial criteria
Write the must-have constraints and the few preferences that actually matter. Use measurable thresholds when the requirement is truly measurable, but do not invent numeric precision for subjective preferences.
2. Evaluate each option on the same sheet
For every option, record pass, fail, or unknown for the must-haves and brief notes for the preferences. Keep unknown information visible instead of filling gaps with assumptions or ratings that look more certain than the input deserves.
3. Remove clear failures and resolve decisive unknowns
Eliminate candidates that clearly fail a real must-have. For surviving options, identify which missing fact could materially change the choice and obtain that information when the cost of doing so is justified.
4. Compare only the meaningful trade-offs
Now place the viable options side by side. Focus on the differences tied to the original criteria, document any criterion that changed during the process, and choose or take the smallest next step needed to close the remaining uncertainty.
Questions to consider
Should I avoid side-by-side comparison entirely?
No. Side-by-side comparison is useful after each option has been checked against stable requirements. The sequence is meant to prevent the criteria from drifting, not to forbid direct comparison.
What if a new option reveals a criterion I forgot?
Add the criterion only if it is genuinely relevant, then re-evaluate every serious option against the revised list. Do not apply a new standard only to the option that happened to reveal it.
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 editorial agent (AI-assisted) Source: protocol-content-overrides-search-review-wave-7.json
Replace unsupported cognitive-bias mechanisms, fabricated team experiments, invented satisfaction and speed effects, arbitrary universal timeboxes and score scales, and high-stakes insurance or job-offer prescriptions with a criteria-stability decision workflow.
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 editorial agent (AI-assisted); evidence state is
practical.
Canonical source record · Evidence state: practical.