Skip to content
D-bug Station

MVP Scope: What to Cut From Version One

3 min read
  • Planning
  • Product
  • Mobile

An MVP is not a small version of the whole product. It is the whole of one job, done well enough to learn from.

Most first versions are too big. Each extra feature delays launch, adds code that has to be maintained, and makes it harder to tell why users stay or leave. A minimum viable product is not a small version of the whole product; it is the whole of one job, done well enough that real users can judge it.

Find the one job

Write one sentence: the user comes to the app to do this. Everything in version one should serve that sentence. A booking app's job is booking; reviews, loyalty points and a chat inbox can wait until people are actually booking.

Usually safe to cut

  • Social features: profiles, follows, comments, sharing beyond a simple link.
  • Settings and customisation: pick sensible defaults and change them when users ask.
  • A second platform, if your users are clearly on one. A cross-platform framework keeps the door open.
  • Complex admin tools: early on, a simple admin panel or even direct database access by one trusted person is enough.
  • Gamification: streaks, badges and levels make sense once there is a habit worth rewarding.

Not safe to cut

  • The quality of the main flow. A slow or confusing core experience teaches you nothing except that people leave.
  • Crash reporting and basic analytics. Without them you cannot learn from the launch, which is the point of an MVP.
  • Account deletion and a privacy policy, which the app stores require.
  • Payments, if the business depends on them. Whether people will pay is often the question the MVP exists to answer.

Cheaper to add later than to remove

Features are hard to take away once users rely on them, and every one of them carries a maintenance cost after launch. When in doubt, leave it out and see whether anyone asks for it. The requests you get after launch are a better roadmap than the list you wrote before it.

Decide what "working" means before you build

Pick two or three numbers that will tell you whether version one worked, such as completed bookings per week or how many users come back in the second week. If you cannot name them, the scope is not settled yet.

We help clients cut scope as often as we help them build it. If you have a feature list and want a second opinion on version one, send it over, or see how we approach mobile products.

Building something along these lines?