Bias comparison · evidence reviewed
Confirmation Bias is a broad umbrella for belief-consistent search and interpretation. Congruence Bias is narrower: it concerns choosing a hypothesis test that fits the favored explanation but does not discriminate well among competing explanations.
The shortest distinction
| Question | Confirmation Bias | Congruence Bias |
|---|---|---|
| Scope | Broad patterns in information search, interpretation, weighting, memory, and hypothesis testing. | A narrower failure in selecting or valuing diagnostic tests among competing hypotheses. |
| Typical question | What evidence would make me change this belief, and am I applying the same standard to supporting and challenging evidence? | If this test is positive, would a plausible alternative hypothesis predict the same result? |
| Positive evidence | Supportive evidence can be overweighted or challenging evidence can receive less attention or stricter scrutiny. | A positive result is weak when several hypotheses predict it; the problem is low diagnosticity, not positivity itself. |
| Best countermeasure | Predefine disconfirming evidence and compare competing explanations using the same standard. | List alternatives and choose observations where the hypotheses make meaningfully different predictions. |
Decision diagnostic
Write the current belief or leading hypothesis and what evidence would weaken it.
List at least one plausible alternative explanation before gathering another round of evidence.
For each proposed test, predict the likely result under the focal and alternative hypotheses.
Prefer tests where outcomes separate the explanations rather than merely allowing the favored hypothesis to receive another positive result.
Use the broader Confirmation Bias label only when the issue extends beyond test choice into search, interpretation, weighting, or memory.
Same outcome, different bias
Confirmation BiasAn engineer gives more weight to logs that support the suspected root cause and discounts contradictory traces.
Congruence BiasAn engineer runs a test that the suspected cause should pass, but a second likely cause would pass the same test.
Confirmation BiasA team interprets ambiguous customer comments as support for the roadmap it already prefers.
Congruence BiasA team asks whether users like a new feature without designing a comparison that separates feature value from novelty or selection effects.
Confirmation BiasA user repeatedly prompts a model to strengthen one explanation and judges supportive outputs as more credible.
Congruence BiasA user asks the model for evidence expected under the favored explanation but never asks what observation would distinguish it from a rival explanation.
Retrospective review protocol
Evidence
Comparison reviewed 2026-08-18. The individual bias pages contain their full evidence status and boundary conditions.
