MVP or Full Build? How to Decide What to Ship First
Shipping too much too early is how good ideas run out of runway. Shipping too little is how they fail to convince anyone. Here's a practical way to decide what your first version actually needs to include.
What an MVP is — and isn't
A minimum viable product is the smallest thing you can ship that delivers real value and teaches you something true about your market. It is not a buggy half-product. It's a deliberately narrow one, finished to a high standard in a small surface area.
Start with the one job
Every product has a single core loop — the action a user takes that delivers the value you promised. For a fitness app it's logging a workout; for a marketplace it's completing a transaction. Build that loop beautifully and cut almost everything else from v1.
Three questions to scope a v1
What's the one job?If a feature doesn't serve the core loop, it's a candidate for later. What proves demand? Build the thing that produces a real signal — sign-ups, payments, retention. What's reversible? Decisions that are cheap to change can wait; decisions that are expensive to change deserve attention now.
When to skip the MVP and build fully
Not everything should start small. If you're entering a category where users already expect a mature experience, or you're selling into enterprise where trust is the product, a too-thin v1 can do more harm than good. Regulated industries (health, finance) also raise the floor on what "viable" means.
The middle path: a phased build
Most of the best launches we ship aren't MVP-or-nothing. They're a v1 that's genuinely polished in a narrow scope, with a roadmap that adds surface area as real usage justifies it. You get to market fast without shipping something that embarrasses the brand.
How design fits in
Even an MVP needs design discipline. A confident, consistent interface makes a small product feel trustworthy; a sloppy one makes a feature-rich product feel risky. Invest in the few screens users actually live in, and keep the rest simple.
A quick gut check
Before you add a feature to v1, ask: would the launch fail without it? If the honest answer is no, it belongs on the roadmap — not in the first release.
Want a similar perspective on your project?