Top of page
Skip to content
orlo.
Product / 5 min read

What belongs in your first product release?

Choose a first release that solves a complete problem and gives the team useful evidence for the next decision.

Maya Ellis · Co-founder & Design Director

· 5 min read

Translucent blocks and a dark cube on a reflective surface

The first release is often asked to prove demand, support several audiences, and show everything on the roadmap. That makes it hard to tell which part of the product people actually value.

Pick one audience and one task worth completing. Build enough of the surrounding experience for people to try it in their real work.

Start with a specific person and task.

Describe who feels the problem often enough to try something new. Ask how they handle it today and what would make them switch.

Use that situation to write a short release goal. The team should be able to recognize the moment when someone gets value.

Choose one useful outcome for the first release. Then decide what people need to reach it.

Follow the task all the way through.

Map the journey from first use to a usable result. Include setup, any information the user needs to enter, and the point where they can act on the output.

Try the flow with a realistic example. If users need help from the team to complete it, decide whether that support is practical for the first release.

Decide what a usable release requires.

Include the error recovery, accessibility, and support that people need to complete the core task. Those details are part of making the release usable.

Write down the requests you are deferring and the reason for each. That record helps when someone suggests the same feature during launch week.

Separate the promise from the implementation.

Some features can be supported manually while demand is still uncertain. A team can review an unusual import before investing in a generalized migration tool.

Give each manual step an owner and a time limit. If it starts blocking customers, you have evidence for automating it.

Translucent blocks and a dark cube on a reflective surface
Map the core task before committing to the features that support it.

Choose evidence that informs the next decision.

Track whether people reach the first useful outcome and where they abandon the task. Talk to a few of them to understand what the event counts cannot explain.

Agree how you’ll act on each signal. For example, repeated confusion at setup might move onboarding ahead of a new integration.

Turn feedback into a small next release.

Set a review date and bring together user feedback, support requests, and the behavior you observed. Separate recurring problems from individual preferences.

Choose the change most likely to make the core task easier. A short next release lets you find out whether the fix helped.

Before you commit to the release scope

  • Name the first audience.
  • Define the useful outcome.
  • Walk through the full task.
  • Record what can wait.
  • Schedule a review of real usage.

A focused release gives your team a usable product and a clearer basis for the next decision.

KEEP READING

A few more ideas to take into your next project.

LET’S BUILD TOGETHER

Have something in mind? Let’s make it happen.

Tell us about your idea, your goals, and where you want to go. We’ll help you work out the next step.