An MVP can become an expensive collection of assumptions. A broad feature set may still fail to show whether a customer wants the core workflow. Product strategy starts by naming the buyer, the problem, and the behavior that would demonstrate value before committing to a large build.
How I approach it
Describe the smallest complete journey that lets the intended user solve the problem. Identify what can be tested manually, what needs software, and what can wait. Translate that journey into acceptance criteria, a delivery sequence, and questions to revisit after real use.