Frame the bet.
Name the change, the audience, the outcome, and why you expect it to work. Decide what would prove you wrong.
A field guide to building what mattersFor the wonderfully uncertain.
Build lesson instinct.Bet on evidence.
The future belongs to better decision-makers.
Hypothesis-driven development is how you become one.
The journey from guesswork to growth
You don’t needto know the way.You need a wayto find out.
01 / The noise
Everything looks like an opportunity.
More features. More speed. More possibilities. But which one actually helps your users?
01The idea, in plain English
Every product is
a collection of
unproven beliefs.
People will want this. They’ll know how to use it. They’ll come back. They’ll pay for it.
Hypothesis-driven development turns those beliefs into small, measurable bets. You make a prediction, build enough to test it, and let real behavior inform what happens next.
It’s a way of managing a product that makes learning part of the work — from your first user to your next stage of growth.
Get to know HDD ↗
The rules have changed
AI made building faster.
It didn’t make
guessing smarter.
When everyone has the power to ship, the advantage moves to judgment. What to build. Who it helps. Whether it worked. What to do next.
Read the manifesto ↗02A small loop. A different way forward.
Strong opinions.
Testable assumptions.
Four moves that turn uncertainty into direction. Repeat for as long as your product exists.
Build to learn.
Ship the smallest useful change that tests the idea. Put it in real hands, with measurement in place.
Read the evidence.
Watch what people actually do. Compare the outcome to your prediction, including what surprised you.
Make the call.
Scale it, change it, or stop it. Record the learning and let it shape your next bet. Then go again.
03Anatomy of a better bet
“Let’s add a feature”
isn’t a hypothesis.
A good bet tells you what you’ll change, who it’s for, and how you’ll know whether it worked.
Try it with your product ↗Field note / a working hypothesis№ 001
Illustrative examples, not reported client results.
04A change in mindset
Less theater.
More truth.
01Outcomes over output.
A busy backlog isn’t a growing business. Connect the work to a change that matters to your users and your bottom line.
02Curiosity over certainty.
Being wrong early is useful. Protect the freedom to question the plan, especially when it was your idea.
03Direction over dogma.
Hold on to the vision. Stay flexible about the route. The roadmap should change when the evidence does.