How to cut a first release down to something you can ship

A scoping method for a first product release: choose one user and one journey, sort features into must, later and never, and fake what you can.

Almost every first product is scoped too large. The founder can see the finished thing, so every part feels essential. The cost is not only money. A release that takes three times as long delays the one event that tells you whether the idea works: a real person using it.

This is the method we use to bring a first release down to size. It takes an afternoon and a whiteboard.

Step 1: pick one user and one journey

Not “small businesses”. One specific kind of person, in one situation, trying to get one thing done. Write it as a sentence: “A clinic receptionist confirms tomorrow’s appointments without phoning each patient.”

If your product has two sides, such as buyers and sellers, choose the side that is harder to win and serve the other by hand for now.

Step 2: write the journey as steps

List what that person does, in order, from arriving to getting the result. Six to ten steps is typical. Do not describe screens yet, only actions: signs in, sees tomorrow’s list, sends reminders, sees who confirmed.

Step 3: sort every feature into three lists

Take every feature anyone has mentioned and ask one question: can the user finish the journey without it?

ListTestTypical examples
MustThe journey breaks without itSign-in, the core action, seeing the result
LaterUseful, but the journey still worksSettings, reports, bulk actions, a second user role
Never (for now)Serves a different user or journeyMarketplace features, integrations nobody asked for

Be strict. “Later” is not a rejection, it is a queue. Most items on it will be reordered by what you learn after launch, and some will quietly disappear.

Step 4: do by hand what you can

Many “must” items need to happen but do not need software yet. Onboarding can be a call. An admin panel can be you editing the database. A weekly report can be an email you write on Friday. Billing for the first ten customers can be an invoice.

  • If it happens fewer than a handful of times a week, do it by hand.
  • If the customer cannot see the difference, do it by hand.
  • If you do not yet know the right rules, do it by hand until you do.

Doing it manually is also research. You find out what the real rules are before you pay to encode them.

Step 5: decide what you will not cut

Small scope is not the same as low quality. A few things belong in a first release however small it is:

  • Sign-in and data handling done properly, since these are painful to fix later.
  • Automated deployment and basic tests, so every later change is cheap.
  • A way to see what users do, so launch teaches you something.
  • The core journey working well on the device your user really has.

Step 6: fix the date, flex the scope

Set a release date you can afford and treat it as fixed. When something takes longer than planned, and something will, move an item from “must” to “later” instead of moving the date. This is uncomfortable the first time and it is the habit that gets products shipped.

How do you know it is small enough?

Describe the release in two sentences to someone outside the company. If they can repeat back who it is for and what it lets them do, the scope is clear. If you need a third sentence that starts with “and also”, there is something left to cut.

A first release is a question put to the market. Make it the smallest thing that can get a clear answer, and spend what you saved on the second release, once you know what to build.

Common questions

What should be in an MVP?

Only what one kind of user needs to complete one journey from start to finish, plus sound foundations such as sign-in, deployment and basic analytics. Everything else goes on a later list.

How do you decide which features to cut from a first release?

Ask of each feature whether the core journey breaks without it. If the journey still works, the feature moves to later. If it serves a different user or journey, it is out for now.

Is it acceptable to do things manually behind a new product?

Yes. Handling onboarding, reports or billing by hand for early customers saves build time and shows you the real rules before you turn them into software.

Should a startup fix scope or fix the release date?

Fix the date and let scope move. When work runs over, push an item to the later list instead of delaying the release.

Talk to us

Working through this for your own product?

Send a few lines about what you are building. An engineer replies, usually within one business day with a first opinion.

See how we work with growing companies

We use these details only to reply to this request. No newsletters, no list. We aim to reply within one business day. See our Privacy Policy.

Book a callTalk to our team