Use recent tasks, expectations, and obstacles to understand what to improve without leading participants toward a preferred answer.
This article covers the conversation during and after a test. The main guide connects it to recruitment and follow-up. Find your first users View guide
Start with what the person was trying to do and the last time the problem occurred. Ask how they handled it before your product. Concrete examples help separate a real need from polite interest.
Avoid asking people to approve a feature or imagine a future purchase. Ask about their actual process and choices, then listen without defending your design.
Ask what they expected to happen and what they looked for next. If they agree to a live session, observe the task without immediately coaching them through it. Keep recordings subject to explicit consent.
When someone says the product was useful, ask which part helped and what they accomplished. Positive evidence can show what to preserve, just as obstacles show what to investigate.
Repeated problems deserve attention, but frequency alone does not determine priority. Consider severity, affected users, and the product promise. Investigate security, data loss, and payment failures immediately.
Surveys can help answer defined questions, but early conversations leave room to discover unexpected problems. Choose based on what you need to learn and the follow-up needed.
Compare their tasks and contexts before changing the product. They may represent different needs. Record the tradeoff and test a focused change with the intended audience.
Return to the main guide to connect what you heard with a change, a response to participants, and a possible second test.