Cognitive Biases · Growth Library

Check a Relevant Baseline Before Interpreting One Case

Practical protocol

Put a vivid example beside the broader reference class it belongs to.

A person comparing notes and marking one useful insight
Protocol summary · practical

Try this

State the decision, define the reference class, find a baseline with a clear denominator and scope, check whether it is comparable to the current case, add the case-specific information that genuinely differs, and keep the conclusion tentative when the baseline or fit is weak.

Check-in: What reference class did I use, where did its baseline come from, how comparable is it to this case, and which case-specific fact could justify departing from it?

Evidence: Practical guidance; no evidence-like claim is detected in the current source record.

Review note: The inherited article contained unsupported accuracy claims, fabricated outcomes, arbitrary confidence thresholds and high-stakes medical, political, hiring and relationship prescriptions. The effective public record is narrowed to an ordinary data-literacy procedure for choosing a relevant reference class, checking comparability and combining a baseline with case-specific information while preserving uncertainty.

A memorable example is information about one case. A baseline describes a broader set of cases. When a decision depends on what usually happens, put those two layers beside each other: define the reference class, inspect the baseline and its scope, then ask whether the current case contains information that should move the judgment away from that starting context.

1. Define the question and reference class

State what you are trying to estimate or compare. Then define the group of cases that would make a meaningful baseline: the same type of task, customer, incident, product, project, process, or other relevant category.

2. Find a baseline with visible scope

Record where the baseline comes from, what period and population it covers, and what denominator it uses. If you cannot identify those basics, treat the number or frequency as weak context rather than a precise anchor.

3. Check whether the baseline fits this case

Compare the current case with the reference class. Note differences that could matter, such as a changed process, environment, segment, requirement or selection rule. Do not borrow precision from a baseline that describes a materially different situation.

4. Combine general context with specific facts

Use the baseline as starting context and add the information that is genuinely specific to the case. If the reference class is weak or the specific information is incomplete, keep the decision reversible where possible and state what remains unknown.

Questions to consider

What makes a baseline relevant?

It should describe a group that is meaningfully comparable to the case and use a denominator that matches the question. A broad number from a different population, period, product, process or operating environment may be less useful than a narrower local record.

Should the baseline override specific information?

No. Use the baseline as context, then account for case-specific information that is relevant and reliable. The purpose is to prevent one vivid detail from silently replacing the broader context, not to ignore real differences.

Can I use this for medical, legal or other high-stakes decisions?

This page is not a decision rule for high-stakes domains. Use domain-appropriate authoritative information and qualified professional guidance where required; a generic reference-class exercise is not a substitute for that review.

Maintenance record

Review history

Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.

  1. 2026-09-10 · reviewed · Brali claim cleanup agent Source: protocol-content-overrides-claim-cleanup-batch-6.json

    Replace unsupported accuracy claims, fabricated outcomes, arbitrary sample-size confidence rules and medical, political, hiring and relationship prescriptions with a bounded reference-class and applicability 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.

Canonical source record · Evidence state: practical.