Small enough to ship. Useful enough to matter.
Choose the user.
A product for everyone is difficult to scope. Choose the person who most clearly needs the first version, and understand the task they are trying to complete.
Specificity gives the design and engineering work a direction. It also makes feedback more useful once the product exists.
Draw the whole workflow.
Identify the start, the main task, and the outcome. Include the ordinary states around that journey: missing information, an empty account, an error, or a step the user needs to repeat.
A focused first release can still offer a complete path through one important workflow.
Decide what can wait.
Separate the work needed for the first useful version from the work that would make the product broader. Write down what is outside the scope as clearly as what belongs in it.
Every additional feature adds product decisions, engineering work, and more things to learn. The first release deserves a clear priority.
Define the learning.
Decide what the release should help you understand. A useful question might concern the task itself, the clarity of the workflow, or whether people return to use the product.
The answer should inform a real next decision. Avoid collecting feedback without knowing what it will help you change.
Keep the next release earned.
Show the product to the people it is for. Listen to the specific points of friction and the parts that already help. Use that evidence to choose the next piece of work.
Our view: a strong MVP is a focused product and a practical learning tool. It should create something real to react to.