Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

Product Strategy

Most MVPs fail because founders treat them as small products instead of focused experiments. Here's how to scope one that actually teaches you something.

Hecham Gazhi2 min read

The word 'minimum' in MVP gets most of the attention. Founders argue about which features are small enough. But the more important word is 'viable' — and viable for what? An MVP is viable when it can answer the question you most need answered.

Start with the riskiest assumption

Every new product rests on a stack of assumptions: that the problem exists, that people care enough to change behavior, that they'll pay, that you can reach them affordably. One of those is the most likely to be wrong. Your MVP should be designed to test that one first.

  • If the risk is demand, a landing page and a pre-sale may be enough.
  • If the risk is usability, a clickable prototype tested with five users is faster than code.
  • If the risk is whether the workflow works end-to-end, then — and only then — build software.

Write the question down

Before scoping features, write a single sentence: 'We believe [customer] will [behavior] because [reason]. We'll know we're right when [signal].' If a feature doesn't help produce that signal, it isn't part of the MVP.

If a feature doesn't help answer the question, it belongs in v2 — no matter how obvious it feels.

Make the learning visible

Instrument the product before launch. Decide what you'll measure, what result would change your plan, and when you'll review it. An MVP without a learning plan is just an early release.

Enjoyed this? Get the next one by email.

Occasional notes on building products and businesses.

Working on something related?

Let's talk