Product · 4 min read
What makes a first product release useful?
A focused first release is a way to learn from the real workflow, not a smaller version of every future feature.
Name the user and the job
Start by describing one person, one situation and the job they need to complete. A broad audience and a long list of features make it difficult to tell whether the product is helping. A specific workflow gives design and engineering a shared point of reference.
Keep the whole journey
A small release should still take the user through a complete, useful journey. Reduce the number of journeys and edge cases, but make the chosen path coherent: entry, action, feedback and a clear next step.
Leave room to learn
Build the first release so it can be observed and improved. Talk to the people using it, look for where they pause or need help, and use those observations to decide what belongs next. The goal is a dependable starting point, not a feature count.