Scoping an MVP: what to build first, and what to leave out

A focused first release is a learning tool. Here is how we prioritise the problems worth solving first.

The most common risk in a first release is building too much. An MVP exists to test the riskiest assumptions with real users, not to ship every idea on the roadmap.

We start by listing assumptions, ranking them by uncertainty and impact, and designing the smallest product that can test the top three.

Everything else becomes a backlog item with a clear trigger for when it earns a place in the build.