A minimum viable product is not simply the smallest possible app. It is a release that lets a defined group of users complete one important task well enough to learn what should happen next.
Start with a specific user and situation
Describe who encounters the problem, when it happens, and what they currently do instead. “Everyone who needs productivity” is too broad to guide a product decision.
- Who is the first user?
- What task are they trying to complete?
- What makes the current process difficult?
Define one complete workflow
Choose a beginning, middle, and end that delivers the core value. Supporting features should earn their place by enabling that workflow, not by looking impressive in a feature list.
Make the non-goals explicit
Write down the capabilities that will not be in the first release. This helps protect time for stability, accessibility, and the essential interaction.
Plan how the product will be evaluated
Select a small set of observable signals—such as task completion, support questions, or where people abandon a flow. Avoid relying on download counts alone to judge whether a product works.