Product discovery
Test the assumption before you build around it.
Sondering helps product teams run exploratory customer conversations without turning discovery into a week of scheduling. Ask about real behavior, concrete moments, and the trade-offs people already make.
Make an interview- Explore a problem before presenting your preferred solution
- Probe the language and examples behind broad statements
- Compare patterns while retaining contradictory responses
§ 01
Start with the decision, not the feature
The strongest discovery brief names the uncertainty that could change a decision. Who experiences the problem? When does it happen? What do they do today, and what does that workaround cost them?
Describe that uncertainty to Sondering and review the proposed interview plan. Remove leading questions, add prompts for recent examples, and keep the conversation focused enough that respondents can finish it.
- Problem exploration
- Concept and message testing
- Onboarding friction
- Workflow and workaround research
§ 02
Ask for moments, not opinions in the abstract
People are often generous with hypothetical enthusiasm. Useful discovery gets closer to what happened: the last time they faced the situation, what triggered it, what they tried, and why they accepted the result.
Adaptive follow-up questions can invite that detail when an answer stays broad. The goal is not to pressure a respondent into agreement, but to understand the context behind their words.
§ 03
Bring the evidence into the product conversation
Review themes across interviews, then open the transcripts behind them. Look for repeated constraints, distinct segments, unexpected workarounds, and evidence that challenges the original framing.
A discovery study should reduce uncertainty, not manufacture certainty. Pair interview evidence with behavior, support signals, and product data before deciding what deserves investment.
Turn the question into a conversation.
Brief Sondering, refine the interview plan, and get a link to share in about two minutes.