Augment

How to Scope an MVP Without Building the Wrong Thing

Scope is the decision about what not to build. These steps help you cut features without cutting the value.

Hands sketching a UX flow on a whiteboard during a design workshop
Photo by Kaleidico on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • Start from the user's problem and the outcome they want, not from a feature list.
  • Draw the end-to-end journey, then pick the thinnest path that delivers the outcome.
  • Say no to features that serve edge cases, admins, or growth until the core is proven.
  • Write down the risky assumptions and design the MVP to test them.

Begin with the problem

A feature list grows easily and shrinks painfully. A problem statement does the opposite. Write one sentence: "[Type of user] struggles to [do something] because [reason], and wants [outcome]." Every feature must earn its place against that sentence.

Map the journey, then cut

1

Draw the full journey

From the moment the user has the problem to the outcome they want.

2

Mark the essential steps

Which steps must exist for the user to reach the outcome at all?

3

Find the thinnest path

The simplest route through those steps, even if some parts are manual.

4

Park everything else

List the rest as later. Do not delete the ideas, just delay them.

Doing part of the work by hand behind the scenes is a legitimate way to test an idea before you build the system.

List your risky assumptions

TypeQuestionTest
DesirabilityDo people want this?Interviews, landing page, pre-signups
UsabilityCan people use it?Usability tests with a prototype
FeasibilityCan we build it?A technical spike
ViabilityWill it make money?Pricing tests, paid pilots

Put the riskiest assumption first. If it fails, the rest does not matter.

Use a simple filter

  • Does this feature help the user reach the core outcome?
  • Will the MVP still make sense without it?
  • Can it be done manually or with an existing tool for now?
  • Does it test a risky assumption?

If the answers are no, no, yes, no, it can wait.

Hold the line

Scope creeps in small requests. Keep a visible "later" list, and review it after launch with real data. Many of those features will turn out to be unnecessary, which is the point of waiting.

Frequently Asked Questions

Pick the thinnest path through the user's journey that still delivers the core outcome, and test your riskiest assumptions first.

Sources and further reading

  1. The Lean StartupEric Ries · Undated page · Accessed
  2. Silicon Valley Product GroupSVPG · Undated page · Accessed
  3. Jobs to Be DoneChristensen Institute · Undated page · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by Kaleidico on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

How to Scope an MVP Without Building the Wrong Thing | Augment. Lab