Scoping the MVP · 5 minute read

User stories, journeys and screens

Features say what a product can do. Journeys say what a person actually does with it, from arriving for the first time to getting the result they came for. Screens are the pages that journey passes through.

Together they turn an idea into something a designer and developer can estimate. They also catch gaps early, such as the password reset nobody mentioned or the email that confirms a booking.

Write user stories

A user story describes a user, what they need to do and why. The GOV.UK Service Manual suggests the format “As a… I need or want to… so that…”, and says the goal, the “so that” part, is the most important.

Write stories for each type of user. Most MVPs have at least two: the main user and an admin, who is often you. A marketplace has at least three: buyers, sellers and you.

Give each story a few acceptance criteria that start “it’s done when…”, so everyone agrees what finished looks like.

Map the main journey

Pick the journey that delivers the core value, the one your MVP exists to test. Write it as numbered steps, from the first visit to the moment the user gets what they came for. Keep each step to one action.

Then walk through the other journeys a real product needs:

  • Signing up, logging in and resetting a password.
  • The first time someone uses the product, when there is no data yet.
  • What happens when something goes wrong: a failed payment, a cancelled booking, an expired link.
  • The emails or texts the product sends, and when.
  • What you, as the admin, need to do: approve users, issue refunds, correct mistakes.

List every screen

From the journeys, list each screen or page with one line on what it is for. Include the small ones: confirmation pages, empty states, error messages and the emails the product sends. They are easy to forget, and every one takes time to design and build.

Sketch them if you can. GOV.UK’s guidance on prototypes notes that they range from a quick pen and paper sketch to a fully interactive version, and that sketches are useful for exploring and discussing ideas. Rough boxes and labels are enough to show a developer what goes where.

Describe the data and integrations

For each journey, note what information the product stores and which other services it relies on. Typical integrations include card payments, email, text messages, maps, calendars and AI models. Each one adds work, so name them all.

If you store personal information, collect only what each journey needs. The ICO’s guidance on data protection by default says you must limit your use of personal information to what is necessary for each purpose. Asking for a date of birth “just in case” is the kind of thing to cut.

Design for everyone from the start

WCAG 2.2 is the latest version of the international standard for accessible web content. Its success criteria are set at three levels: A, AA and AAA. Ask your designer and developer to work to level AA from the start, and say so in your brief, so it is priced in rather than added later.

The journeys step of the MVP builder has a box for the main journey, the screens, the data and the admin side, so nothing gets missed.

Before you finish

  • Each type of user has user stories with a clear goal.
  • Stories have acceptance criteria.
  • The main journey is written as numbered steps.
  • Sign-up, first use, error and admin journeys are covered.
  • Every screen, email and text is listed with its purpose.
  • Every integration is named.
  • Only the personal data each journey needs is collected.
  • Accessibility to WCAG 2.2 level AA is in the brief.

Common questions

What is the difference between a user story and a user journey?

A user story describes one need: who, what and why. A journey strings several stories together into the steps a person takes from start to finish.

Do I need a designer before I talk to developers?

Not necessarily. A clear journey and screen list is enough for a first estimate, and some developers and studios include design in their quote. If you already have designs, the estimate will usually be tighter.

How detailed should the screen list be?

One line per screen is enough for pricing. Say what the user sees and what they can do there, such as “list of upcoming appointments, each with a status; tap one to see the details”.

Scope your MVP with the builder

Guided sections, features ranked, your budget and runway worked out, and a brief a developer can price. Free, no sign-up.

Start your brief

Sources

Checked on 15 November 2026. Prices, rates and rules change: follow the links for the latest figures. This page is general information, not professional, financial, legal or tax advice.