Know the user and problem
Developers can estimate a defined solution. They should not be expected to discover the business problem for you while also building it.
Map the core journey
Write down the shortest route from a user arriving to receiving value. That journey becomes the backbone of the MVP.
Write what is out of scope
Exclusions are as important as features. They prevent assumptions from silently expanding the build.
Decide how product decisions will be made
Someone needs authority over priorities, trade-offs and acceptance. Without clear product ownership, delivery slows and rework grows.
Keep the goal simple: spend enough to learn what matters, then use that evidence to decide what deserves the next investment.