shield_lock
JinDaGe
Contact
← Back to skills
extension
Category: Productivity & OfficeNo API key required

Absurdity Heuristic

Classify highly unusual situations as impossible - but beware of rejecting valid predictions

personAuthor: jakexiaohubgithub
open_in_newRepositorydownloadDownload package

Absurdity Heuristic

Core Concept

The absurdity heuristic classifies highly atypical situations as "absurd" or impossible based on how much they violate our intuitions about what is typical or normal. It is the mirror image of the representativeness heuristic - the less X resembles Y, or the more X violates typicality assumptions of Y, the less probable that X is the product, explanation, or outcome of Y.

While normally useful as epistemic hygiene for detecting nonsense, it becomes an "absurdity bias" when we reject valid predictions or explanations simply because they seem too unusual.

When to Use

  • Evaluating extraordinary claims or predictions
  • Detecting potential nonsense or fraud
  • Assessing whether future scenarios are plausible
  • Deciding when to override surface-level intuitions with deeper analysis
  • Forecasting technological or social change

Implementation

1. Recognize When Absurdity Heuristic Triggers

Notice when you think: "That's absurd," "That can't be right," or "That's impossible" based purely on how unusual something seems.

2. Distinguish Useful vs. Biased Application

Ask: Is this truly impossible, or just highly unusual? Does my sense of "absurdity" come from:

  • Genuine logical impossibility
  • Violation of known physical laws
  • Merely being outside my typical experience

3. Check for Three Danger Zones

The absurdity heuristic becomes a bias in three situations:

A. Deep theory should override intuition When you have information about underlying laws that should override surface reasoning. Example: Quantum mechanics predictions that seem "absurd" but are mathematically sound.

B. Abstract information conflicts with surface absurdity Attending to surface absurdity despite abstract information that should override it. Example: Rejecting studies showing marginal healthcare spending has zero net effect because "that seems absurd."

C. Unstable processes The process is not stable in its surface properties over the range of extrapolation. Example: The future is usually "absurd" compared to 50 years prior - projecting stable surface rules forward fails.

4. Apply Corrective Strategies

When the heuristic triggers, consciously evaluate:

  • What underlying mechanisms or laws apply?
  • Am I extrapolating from a stable or unstable process?
  • What does the base-rate data actually show?
  • What do domain experts with deep models predict?

5. Distinguish Epistemic vs. Instrumental Context

In epistemic context (seeking truth): Override absurdity intuitions with evidence and deep models. In instrumental context (making decisions): Weight absurdity appropriately - unusual claims may still require unusual evidence even if theoretically possible.

Real-World Examples

Technology Forecasting

  • 1950s: "Computers in every home" seemed absurd
  • 1990s: "Everyone carrying a networked computer" seemed absurd
  • 2020s: Many predictions that seem absurd today will be normal by 2070
  • Lesson: The future systematically violates our typicality assumptions

Medicine

  • Studies showing marginal medical spending has zero or negative net effect
  • Seems "absurd" that more medicine doesn't help
  • But randomized controlled trials confirm this for many interventions
  • Lesson: Abstract evidence should override surface absurdity

Physics

  • Wave-particle duality seems absurd to classical intuitions
  • Quantum entanglement seems absurd ("spooky action at a distance")
  • General relativity's predictions seemed absurd before confirmation
  • Lesson: Mathematical models override surface-level absurdity

Risk Assessment

  • Nassim Taleb's "Black Swan" events seem absurd until they happen
  • Financial models that assumed 2008 crash was "impossible"
  • Lesson: Unstable systems produce "absurd" outcomes regularly

Common Pitfalls

  • Rejecting all unusual claims: Some unusual claims are true
  • Accepting all unusual claims: Most unusual claims are still false
  • Ignoring base rates entirely: Absurdity heuristic has value - most "absurd" things are false
  • Failing to distinguish domains: In stable domains, absurdity heuristic works better; in unstable domains, it fails
  • Overriding with weak theory: Don't abandon absurdity heuristic for weak abstract claims

Relationship to Other Frameworks

  • Representativeness Heuristic: Absurdity is the inverse - low representativeness
  • Sagan Standard: "Extraordinary claims require extraordinary evidence" - when to override absurdity
  • Bayesian Updating: Absurdity heuristic is implicit low prior probability
  • Black Swan Thinking: Absurdity bias causes us to underweight tail risks
  • Epistemic Humility: Recognize that "absurd" ≠ impossible

Success Metrics

  • Catch yourself using "that's absurd" as an argument
  • Distinguish between genuine impossibility and mere unusualness
  • Correctly identify unstable processes where absurdity heuristic fails
  • Override absurdity intuitions when deep theory or evidence warrants
  • Maintain appropriate skepticism without rejecting all unusual claims

Key Insight

The absurdity heuristic is a double-edged sword: invaluable for detecting nonsense in stable domains, but systematically wrong when applied to unstable processes, deep theoretical predictions, or long-term forecasts. The skill is knowing when to trust it and when to override it.

Primary Sources: LessWrong (Eliezer Yudkowsky), Robin Hanson Related Concepts: Representativeness Heuristic, Outside View, Reference Class Forecasting Complexity: Medium Estimated Learning: 30 minutes to understand, ongoing practice to apply skillfully