Name the core outcome
Before ranking features, describe the result a user must be able to reach. A useful MVP protects this outcome and removes work around it. A thin MVP removes steps from the outcome itself.
Design one complete journey
Choose one audience, one urgent problem, and one end-to-end workflow. Completing a narrow journey creates better evidence than partially supporting several unrelated jobs.
Separate learning from infrastructure
Some work is necessary to test the idea; other work prepares for a scale that may never arrive. Prefer architecture that can evolve, but do not make future complexity a launch requirement.
Keep a decision ledger
Record what was removed, why, and what evidence would justify bringing it back. This keeps scope decisions strategic instead of emotional and gives the post-launch roadmap a reliable starting point.