Works
About
S . B0%
← Writing

How to design an MVP: what to build first, and what to leave out

Nov 6, 2026 · Thought · 2 min read

Most founders know an MVP should be small. The hard part is deciding how small, and what exactly to cut. Cut too little and you spend months building a product nobody has asked for. Cut too much and you launch something so rough that people can’t tell whether the idea is good or the product is just broken.

Here is how I would approach designing an MVP.

Start with one job

Write down the single thing a user should be able to do with your product that they could not do easily before. Not five things. One. Every screen, every button and every setting should either help with that job or wait until later.

If you can’t describe it in one plain sentence, the MVP isn’t ready to be designed yet.

Map the shortest path

Sketch the path from the moment someone opens your product to the moment they get value from it. Count the steps. Then remove steps until the path feels almost too short. Sign-up forms, tours, settings and extra choices are usually the first things to go.

Decide what to leave out

  • Features only a few users will ever need.
  • Settings and customisation. Choose sensible defaults instead.
  • Complex roles and permissions, unless they are the product.
  • A full dashboard, when one simple view would do.
  • Anything you are building because a competitor has it.

Keep a list of what you cut. It becomes your roadmap, and it is easier to cut when you know it is postponed, not lost.

Small does not mean rough

This is where many MVPs fail. People forgive a short feature list. They don’t forgive a confusing screen, a broken layout or an unclear message. Early users are deciding whether to trust you, and the quality of the basics is how they decide.

Spend your design effort on the few things that remain: clear writing, simple layout, fast loading, and every state handled, including empty screens and errors.

Design and build together

For an MVP, the handoff between a designer and a developer is one of the biggest sources of delay. When the same person, or a small team sitting together, designs and builds, decisions are made in minutes instead of days, and you find out what is expensive to build before you have designed it.

Launch, watch, change

An MVP exists to teach you something. Put it in front of real people early, watch what they do, and ask where they got stuck. Resist the urge to polish in private. A small product in real hands teaches more than a bigger one in your head.

If you are not slightly embarrassed by how small the first version is, you built too much.

Rule of thumb

Designing your MVP?

At Elysium Designs, we help founders decide what to build first, then design and build it, from the first sketch to a live product. If you have an idea and want to turn it into something real without overbuilding, let’s talk.

Have a product to design and build?

Book an intro call