An MVP is not a half-built feature list. It's the smallest complete experience that tells you whether your bet is worth doubling down on.

A minimum viable product is the smallest thing you can put in front of real users that tests whether your product hypothesis holds. The emphasis is on viable — not a broken prototype, but a coherent slice of value that a user would actually engage with. It’s not the smallest thing you can build; it’s the smallest thing worth testing.

The common mistake is scoping an MVP like a feature list and cutting until it’s small enough. The better approach is journey-based: use story maps to visualize the full user experience, trace user journeys through it, and select the smallest journey that delivers a complete, functional experience. An MVP built from a journey preserves the user’s perspective end-to-end rather than delivering a half-finished version of everything.

<<<<<<< Updated upstream An MVP is not the final product; it’s an experiment. The question isn’t “did we build it right?” but “does this create the conditions for our target outcomes?” Does it move the needle on the impact we’re after? If yes, expand. If no, learn why and adjust.

In the 3X Model, MVPs are the primary vehicle for moving from Explore to Expand: they’re how you find out whether a product idea has merit before investing heavily in scale and polish.

An MVP is not the final product; it’s an experiment. The question isn’t “did we build it right?” but “does this create the conditions for our target outcomes?” Does it move the needle on the impact we’re after? If yes, expand. If no, learn why and adjust. In the 3X Model, MVPs are the primary vehicle for moving from Explore to Expand: they’re how you find out whether a product idea has legs before investing heavily in scale and polish.

Stashed changes

Resources

• User Journeys — the technique for scoping journey-based MVPs
• User Story Mapping — the map from which MVP scope is derived
• Product Experiments — MVPs as a form of high-fidelity experiment