How to scope an MVP that people can actually use

Start with one person in a recognisable moment, rather than a broad audience. A founder might choose the point where a prospective customer is deciding whether to ask for help, or where an operator needs to act on a new request.

Describe what that person is trying to do before they encounter the product. This anchors the first version in a real situation and prevents the scope from expanding to cover every possible user at once.

A first product can be small and still complete. Draw the route from the person's starting point through the information they provide, the feedback they receive, and the useful result they leave with.

Look for missing endings as you draw. A form without a clear confirmation, a request without a next step, or a result without context can make a short path feel unfinished even when every planned screen exists.

The promise is the reason someone would try the product. Keep the essential part of that promise in the first path, even when supporting features need to wait for later.

Use the promise to decide what to defer. If a feature does not help this person complete this moment, capture the idea and leave it outside the first release instead of weakening the useful path.

Uncertainty is useful when it becomes a question the first version can help answer. Write down what you do not know about the person's needs, the information they will provide, or the part of the path that may cause confusion.

Then make space to notice what happens in use. Plain language, understandable feedback, and a way to review the journey can turn an early release into a better conversation instead of a frozen set of assumptions.

Write one sentence: “This first version helps [person] do [job] when [moment].” Use it when reviewing every proposed feature; if the feature does not protect that sentence, it can wait for evidence from real use.