Core Idea
Definition
The hypothetico-deductive method evaluates hypotheses by deducing observable predictions from them and then testing whether those predictions hold.
In Plain English
If this explanation were true, what should we expect to see? Then go look.
Framework Structure
Components
Flow
Propose explanation -> Derive predictions -> Test in the world -> Keep, revise, or reject based on the result
How to Apply
- 1.State the hypothesis clearly enough that it implies specific predictions
- 2.Derive observable consequences that should follow if the hypothesis is true
- 3.Design a test that can distinguish those predictions from alternatives
- 4.Collect evidence and compare it against the predicted pattern
- 5.Revise or reject the hypothesis if the predictions fail
When to Use
- •Testing explanatory hypotheses
- •Product, scientific, and operational experiments
- •Situations where theory should lead to observable expectations
- •Any context where you want to connect explanation to evidence
- •Challenging narratives that sound plausible but predict little
When NOT to Use
- •When the hypothesis is too vague to generate clear predictions
- •When measurement is too weak to distinguish outcomes meaningfully
- •When the domain is too complex for clean one-shot tests and richer triangulation is required
- •When the exercise is used only to confirm rather than to challenge
Example
Problem
A team believes that faster first-response time in support will reduce churn.
Application
- 1.Turn the belief into a hypothesis about customer behavior
- 2.Deduce predictions such as lower churn among customers receiving faster early support
- 3.Run a test or natural comparison that isolates response speed as much as possible
- 4.Compare actual churn outcomes against the predicted pattern
Conclusion
The team evaluates the theory by what it predicts, not just by how convincing it sounds.
Takeaway
A hypothesis earns trust when it survives predictive testing.
Common Mistakes
- •Generating predictions after seeing the evidence
- •Using predictions so broad that nearly any outcome can be counted as support
- •Ignoring rival hypotheses that make similar predictions
- •Treating one failed prediction as total disproof when auxiliary assumptions may be involved
- •Confusing successful prediction with complete explanation
How to Practice
if then prediction
For each explanation you propose, write at least two concrete observable consequences.
rival prediction check
Ask whether a competing explanation would predict the same evidence.
pre registered expectation
Write the expected pattern before examining the results so you cannot quietly rewrite the theory.
Related Cognitive Biases
confirmation bias
People often seek affirming examples rather than risky predictions.
post hoc rationalization
After results are known, people can retrofit predictions to protect the theory.
overconfidence
A neat theory can feel stronger than its predictive record actually justifies.
Related Frameworks
Related Skills
Variants & Extensions
Typical Failure Modes
- •Vague predictions
- •Post hoc adjustment
- •No discrimination from rivals
Further Reading
- The Logic of Scientific Discovery by Karl Popper
- Theory and Reality by Peter Godfrey-Smith
- The Art of Statistics by David Spiegelhalter