An MVP is a way to learn. Start with a specific audience and a problem important enough for that audience to change its behavior.
Define the decision
Ask what you need to know after the first release. Whether people complete a workflow is more useful than whether they say the idea sounds good.
Choose one complete journey
Cut secondary features, but keep the core experience coherent. A user should be able to start, finish, and understand the result of the primary task.
Agree on success before launch
Select a small set of signals: completed tasks, repeat usage, or qualitative feedback. Use the findings to decide what to improve, stop, or build next.