Product Management · Technology Strategy
What belongs in a first release
A first version should be small enough to reach real users quickly and complete enough that their reaction means something. How to decide where that line sits.
- Author
- Jordan Dias
- Published
- Last updated
- Reading time
- 5 minutes
The question this answers
A first release keeps growing and the launch date keeps moving.
Key takeaways
- State the assumption under test; anything that does not test it is deferred.
- The assumption is usually behavioural, not technical — whether people will change how they work.
- Record exclusions in writing, or deferred scope returns as a surprise.
- Replace the highest-cost step first; a shallow version of the whole process adds work instead of removing it.
The scope question is a testing question
Arguments about first-release scope are usually arguments about what is being tested. Once the assumption under test is stated explicitly, most scope disputes resolve themselves: anything that does not test the assumption is deferred.
The assumption is rarely technical. It is normally whether a specific group of people will change how they work in order to use the thing.
Keep the exclusions written down
Deferred scope that is not recorded reappears as a surprise. A visible exclusions list is as valuable as the scope itself — it prevents relitigating settled decisions, and it gives investors and boards evidence that sequencing was deliberate rather than accidental.
Replace the highest-cost step first
For internal platforms, adoption follows relief. Identify the step that consumes the most time or produces the most rework, and replace that first even if it is not the most interesting part of the system.
The common failure is delivering a complete but shallow version of the whole process. It adds a place to update without removing work, and teams quietly return to the spreadsheet.
What a first release should always include
Regardless of scope, three things belong in the first release and are painful to add later.
- Access control and audit history, because they cannot be backfilled.
- Enough instrumentation to know whether the thing is being used and where people stop.
- An onboarding path, because a platform nobody can start using has not been released.