Think Better

How to Think in Hypotheses

Starting with a best guess feels risky. In practice it's the fastest way to the right answer, as long as you're willing to be wrong.

6 min readFull guide coming soon

The short version

The slow way to solve a problem is to gather all the data and hope an answer appears. The faster way is to start with a best guess and test it.

A good hypothesis is specific enough to be proved wrong. 'Something is wrong with sales' is not a hypothesis. 'We're losing customers in their first 90 days because onboarding is confusing' is.

Then ask: what would have to be true for this to be right? Go and check those things first. If you're wrong, you'll find out quickly and pick a better guess.

Try it now. Put this into practice with the Hypothesis Builder (coming soon).

What the full guide will cover

  1. Why answer-first is faster
  2. What makes a good hypothesis
  3. Listing what would have to be true
  4. Avoiding confirmation bias
  5. When to switch hypotheses
Newsletter

Get the full guide when it's ready

Join the Futureback Brief. One useful idea for thinking and working better. No corporate fluff.