A focused MVP answers the riskiest product questions with the smallest useful release.
Start with the user problem and the evidence that would prove your proposed solution helps. List assumptions about users, workflows, and adoption, then rank them by risk.
Choose one end-to-end workflow that tests the most important assumptions. Keep the first release narrow, but complete enough that a user can reach a meaningful outcome.
Agree on a small set of signals before implementation: task completion, time to value, repeat use, and qualitative feedback. Review them together to decide what to build next.
