MVP user research helps identify which problem deserves a first build. Ask people about recent tasks and existing workarounds, then use the evidence to prioritize a prototype and its validation questions.
Choose people who do the work
Speak with users who have recently completed the task you want to improve. A small initial group can surface useful patterns, but the number needed depends on the audience and the questions. Treat early findings as evidence to investigate rather than proof that every user has the same needs.
Ask about a recent example
Have the person walk through what happened, which tools they used, and where they got stuck. Ask what information they needed and who else became involved. Concrete examples help distinguish a repeated problem from a feature someone thinks might be useful.
Explore exceptions and review needs
Find out what happens when information is missing or a decision is uncertain. For an AI feature, ask which outputs users would want to check and which actions should require approval. These answers help define a useful scope and clearer boundaries.
Turn findings into a first journey
Summarize the main task, the friction points, and the decisions the product should support. Use them to prioritize a prototype or MVP, then validate the result with users. Rantum Solutions connects this discovery work to the design, development, and automation plan.
A short interview outline
Ask the participant to recall the last time they completed the task. What started it? Which tools did they open? What information was missing? Who needed to approve the result? Where did they copy information by hand? Avoid showing the proposed solution until you understand the current behavior; otherwise the conversation can drift toward opinions about your design.
Planning checklist
- Recruit participants who actually perform or depend on the task.
- Record the context of each example rather than counting feature requests alone.
- Separate observed behavior, participant opinion, and your interpretation.
- Use the findings to write a task that a prototype should help someone complete.
When is the research enough for a first step?
Enough depends on the risk of the decision and the variety of users. Early conversations can guide a prototype without proving that the whole market wants the product. Name the uncertainty that remains and choose a test that addresses it. This keeps research connected to a decision rather than a large report.
Next steps
Before you start, turn the findings into a focused MVP scope. Explore our AI, automation, and development services or send a project brief to discuss the requirements.
For a broader planning guide, read SaaS MVP Development Checklist for Startup Founders.