Private preview. Groundwork is invite-only while we finish building — join the waitlist for an invite.
Product DesignFoundational

MVP Scope

Define what your minimum viable product actually is — the smallest thing you can ship to test your core hypothesis with real customers.

Created by the Groundwork teamGCreated by the Groundwork team

What you walk away with

A real document, built from everything you worked through — then critiqued the way a tough reviewer would and polished round by round. Plus a project summary that shows your work.

19 steps in the full journey.

Who this is for

Founders about to start building, or ones already building who have watched the scope grow every week for a month.

What you'll actually decide

The smallest thing you can ship that tests the core hypothesis — and, just as importantly, the explicit list of what's out and why.

What first-time founders get wrong here

Confusing minimum with unfinished. An MVP is small in scope and complete in what it does; shipping a broad, half-working product tests nothing, because the thing users reject is the roughness rather than the idea. The other one is that everything feels essential when you haven't written down what the hypothesis is.

The first 10 questions

This is where the conversation starts. Each answer shapes what gets asked next.

  1. 01What is the product you're trying to build, and what stage are you at — idea, prototype, or early build?
  2. 02What is the core hypothesis you need to test — the one assumption the whole product rests on?
  3. 03Who is the target user for the MVP, and how will they get access to it?
  4. 04What have you already learned — any user research, prototype tests, or early customer conversations?
  5. 05What is the minimum outcome a user needs to experience for the MVP to count as a success?
  6. 06What features feel essential but are actually about you wanting to ship something polished — what can wait?
  7. 07What could go wrong that would cause you to ship too late, build too much, or test the wrong thing?
  8. 08How will you know if the MVP worked — what's the metric, feedback signal, or behavior you're looking for?
  9. 09What's the riskiest thing about this MVP, and what are you doing to reduce that risk?
  10. 10What features must be in the MVP — the non-negotiables for the test to work?

+ 7 more questions across discovery, validation, and the creative brief — each one adapting to what you've already said.

Related product design project types

Ready to work through it?

The first five questions of any project are free — no card required.

Join the waitlist →