Designing an MVP around what users need
When time is limited, clear priorities matter more than more features.
Start with one specific problem
Define the obstacle and the situation in which it occurs. Turn assumptions into testable questions, using interviews and existing behaviour to check them before writing a feature list.
Map the shortest path to value
Map the steps between first use and a meaningful result. Question every additional step. A prototype should reveal problems rather than hide undefined business rules.
Let feedback guide the next step
Define success for the main task and observe whether users can complete it independently. Record obstacles, causes, and changes so the next iteration is grounded in evidence.
