Heuristic

Run a test that could prove you wrong

When two explanations predict an outcome equally well, that outcome does not tell you which to choose.

A situation to tryIllustrative example

One failure. Two possible causes.

An import fails. Is the file invalid, or is the connection failing? Choose an observation to compare.

A working desk with a laptop, external drive, disconnected cable, papers and a coffee mug
Drive and cableThe reports

What would you try?

Two ways to look at it
File explanationThe suspect file is invalid.
Connection explanationThe connection is failing.

Try either move. Compare what it can tell you.

Why keep the connection fixed?

Changing both file and connection would leave the cause of a different result unclear.

A control is useful only when conditions are comparable. Both causes may coexist; stop when another check costs more than it can help.

Read the complete idea VedokrokSee a situation. Try a different move.

Before you use it

Use when
  • You have a preferred explanation and can still inspect evidence before committing.

Keep this limit in mind

  • Do not invent a weak alternative just to create symmetry. Stop when extra testing costs more than the decision warrants, and keep uncertainty visible.
  • This general reasoning aid does not replace professional advice in high-stakes decisions.

Why it matters

Put the leading explanation next to a plausible rival, then look for an observation on which they make different predictions. The aim is not to be contrarian. It is to collect information that can actually move the decision.

Steps

  1. Write the explanation you currently prefer and the decision it would support.
  2. Add one plausible alternative. For each, write what you would expect to observe if it were true.
  3. Choose the cheapest useful check where the predictions differ.
  4. Record what happened, then keep, narrow, or change the conclusion. If the result fits both explanations equally well, call it inconclusive.

An example

An import failure could come from the network or a malformed file. Repeating the same failing import proves little. Holding the connection constant while comparing a known-good file with the suspect file tells you more.

Check your result

Can you name two explanations, the observation that separates them, and how each possible result would change your conclusion?

A small scene. Your next move.

Try this idea.

Make a move, see what changes, then bring it to your own situation.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Try it in a task guide

These guides use this edition of the method alongside other ideas for the same task.

Choose a test or question that could prove the working explanation wrong.
Clarify an Unclear Work Task

Connected ideas

You are readingRun a test that could prove you wrong

Evidence and sources
Supports

Confirmation bias includes seeking or interpreting evidence in ways that favor an existing belief or hypothesis.

Supports only the scoped description; does not test the corpus procedure.

Confirmation Bias: A Ubiquitous Phenomenon in Many Guises · Publisher abstract and review description

All sources (1)
Edition and review

Version 1.0.0

No review details are supplied for this edition.

Read this idea as JSON · Release details