Building the Product

How do I decide the single riskiest assumption my MVP should test instead of trying to prove the whole idea at once?

A starting point

List every belief your business needs to be true (people want this, they'll pay this much, you can acquire them cheaply, you can deliver it), then rank them by how fatal they are if wrong and how uncertain you are. Your MVP should attack the top one, usually a demand or willingness-to-pay risk, not a technical one. Founders default to building because it feels productive, but building the wrong thing well is the most expensive mistake there is. Use this as a starting point and re-rank as you learn.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 2 link-checked Read Use

Read

📖 Book
✓ Link checked Paid Intermediate

Why we picked it Once you know your riskiest assumption, this book tells you which experiment actually tests it. It carries 40 plus illustrated experiment types organised by cost, time, and strength of evidence, matched to whether the risk is about desirability, feasibility, or viability. It is the reference you keep on the desk so you run the cheapest test that gives real evidence, not the most impressive demo.

Testing Business Ideas: A Field Guide for Rapid Experimentation

From Strategyzer (Wiley) by David J. Bland and Alexander Osterwalder Book, around 320 pages

  • Break the idea into prioritised, testable assumptions first (via assumptions mapping), then pick an experiment for the riskiest one.
  • Match the experiment to the type of risk: a landing page or interview for desirability, a different test for feasibility or viability.
  • Start with cheap, fast, low-evidence experiments and only invest in stronger, costlier ones as an assumption survives the early tests.
Open strategyzer.com →
✍️ Essay
Free Beginner

Why we picked it This is the essay that named the problem: an MVP quietly pushes you to build a whole product when what you actually need is to test one thing. Higham makes the case for the Riskiest Assumption Test (RAT), building only enough to learn whether your single biggest unknown holds. It is the sharpest starting point for deciding what to test instead of what to build.

The MVP is dead. Long live the RAT.

From HackerNoon by Rik Higham 8 min read

  • An MVP is not really a product, it is a way to test whether you have found a problem worth solving, so treat it as a test, not a launch.
  • Find your largest unknown and build only what is needed to test it, nothing more.
  • The goal is to maximise the rate of learning by minimising the time to try things, so pick the assumption that would kill the idea if it were wrong.
Open medium.com →

Use

📋 Template
✓ Link checked Free Beginner

Why we picked it The essay tells you to find your riskiest assumption, this template shows you how to actually surface it. It is a free, copyable 2x2 grid where you plot each assumption by how important it is and how much you actually know, so the top corner (very important, barely known) is the one to test first. That top-right quadrant is your single riskiest assumption, made visible instead of guessed at.

Assumption Mapping Template (free, FigJam)

From Figma FigJam by Figma Ready-to-use board

  • Write every belief your idea depends on as a plain assumption, then place it on the grid rather than debating it in your head.
  • The two axes (importance and how much you know) turn a vague hunch into a ranked list, so the riskiest assumption becomes obvious.
  • Test only the top-right quadrant first (critical and least known), and leave the safe or trivial assumptions alone for now.
Open figma.com →

People also ask

What actually counts as an MVP, and what's the smallest one I can get away with? An MVP is the least you can build (or fake) to test your single riskiest assumption, not a shrunken version of your dream product. Ask 'what's the ... Beginner 3 resources → How do I decide which features to cut from v1? Cut everything that doesn't help you learn whether people want the core thing. Pick the one workflow your earliest, most desperate customers need a... Beginner 3 resources → How long should building an MVP take? Weeks, not months. If your MVP will take more than 4-8 weeks, your scope is wrong, not your timeline. Airbnb, Stripe, and Twitch all launched narro... Beginner 3 resources → Should I build an MVP at all, or can I validate without one? If you haven't talked to ~20-30 potential customers yet, don't build anything, you're not validating, you're procrastinating in code. A concierge M... Beginner 3 resources → How do I get my first users for the MVP? Recruit them by hand, one conversation at a time, this is the whole point of an early startup. Go to where your users already are, DM them, email t... Beginner 2 resources → What's the difference between an MVP and just a cheap, half-finished product? An MVP is a learning tool with a clear hypothesis attached; a cheap product is just a bad product. The point isn't to spend less money, it's to buy... Intermediate 2 resources →