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?
| List | Test | Typical examples |
|---|---|---|
| Must | The journey breaks without it | Sign-in, the core action, seeing the result |
| Later | Useful, but the journey still works | Settings, reports, bulk actions, a second user role |
| Never (for now) | Serves a different user or journey | Marketplace 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.
