Why Your MVP Should Start With a Key Question, Not a Feature List

A widely shared piece on DEV Community argues that most teams build weak MVPs by starting with a feature list and trimming it down, rather than identifying the single most critical assumption to test. The author contends that a true MVP is not simply a smaller product but a focused tool for validating whether a core idea is worth pursuing further. The recommended starting point is asking 'What do we need to learn first?' rather than 'What can we fit into version one?' Using a client-feedback tool for agencies as an example, the piece illustrates how builders should isolate their riskiest assumption — such as whether users will abandon email and Slack for a new workflow — and test that before adding billing, roles, or integrations. The article also warns against 'just in case' feature additions, which inflate scope, multiply edge cases, and obscure whether the core value proposition actually works.