A practical starting point
A minimum viable product is a way to test whether a proposed solution helps a real user. It is not simply the smallest version of every feature on your wish list.
Choose one user, one job and one end-to-end experience. Identify the assumption that could make the idea fail. A manual service, clickable prototype or small working feature may be enough to test it.
Define what you need to observe before building more. Look at whether users complete the task and return, not just whether they like the presentation. Keep a record of the trade-offs made.
The practical guide below works through a hypothetical example, the decisions to check and a way to review the result. Use it to prepare questions for your own situation; adapt the exercise to the information and tools you are authorised to use.
MVP Planning should produce a decision about the next test, not an automatic permission to build the entire wish list. Use Customer Discovery to check whether the task matters and Writing a Startup Product Brief to explain the implementation work. Keep excluded features visible so they do not quietly return as assumptions during design. Add scope when the evidence justifies it.
Read the practical guide
MVP Planning: a practical planning guide →Related topics
Start with a better brief.
Use the free planning tool, then tell us what you want to achieve.