Open-ended questions don’t have a predetermined set of answers and they’ll differ from user to user.
They allow room for discussion and follow-up questions, encouraging your users to answer at length.
The questions “did you enjoy using our product?” and “what did you enjoy about using our product?” are similar but the answers you get are wildly different.
With the former, the answers are either binary or multiple choice and it’s a good question to ask in a survey to get quantitative data.
The latter encourages your users to expand on their positive experiences with your product.
Open-ended questions encourage in-depth answers and help you understand your users’ perspective.
This is invaluable for gaining insights about their pain points, needs and motivations.
Avoid leading questions
The point of user interviews is to get answers that accurately reflect your users’ experiences with your product.
That’s why you should avoid asking leading questions.
So, if you ask your users “did you enjoy using our fantastic product?” you’re implying that the answer should be “yes” with the way you’ve framed your question.
Leading questions are most commonly found in surveys but they can crop up in user interviews, too.
To avoid them, make sure you keep your questions neutral and avoid platitudes about your product.
Leading questions prevent your users from giving you honest feedback.
It’s awkward to answer a question honestly if someone’s experience is opposite to the framing of the question.
Someone who had a negative experience with your product is less likely to answer truthfully if you ask them “what did you enjoy about using our fantastic product?”.
Leading questions compromise the integrity of your data and render it useless.
This makes it impossible to get actionable insights and improve your product to better meet your users’ needs.
Understand your users’ context
To ask your users the right questions, you need to understand their context.
This means understanding the context in which they’re using your product.
Understanding your users’ context is key to getting the most value out of your user interviews.
It also gets you closer to the main goal of product discovery, which is creating a product that meets your users’ needs.
Understanding the contexts of use is also a cornerstone of user-centered design.
The context in which your users use your product is influenced by everything from their culture to the capabilities of the device they’re using.
But, what does that have to do with your user interview questions?
Let’s go back to our collaborative design tool example from earlier.
If it’s meant to be used in a professional capacity by product designers, its context of use will be different than if it was geared towards beginners.
If you understand how your product is used, you’ll be able to craft better interview questions.
In our example, you can ask “how does our product fit into your workflow?”
This will gain you insights into potential improvements you can make on that front.
Understanding your users’ context also helps you narrow down the pool of potential participants, e.g. excluding iOS users if you’re making an Android app.
Use active listening techniques
A user interview is a conversation, not an interrogation.
Building rapport with your interviewees is crucial for a successful user interview in product discovery.
Active listening plays a huge role in making that happen.
It helps you connect with your interviewee and facilitates open, honest dialogue.
If you actively listen, your users will be more comfortable opening up and you’ll get better results from your user interviews.
It’s important to always inform your interviewees that you’re recording and you should gain their consent first.
Recording and transcribing user interviews will allow you to revisit and reference them later.
It also makes it much easier to share the results of your user interviews with the rest of your discovery team.
Another benefit is that you’ll be able to gather insights faster if you have a transcript of the interview as opposed to relying on notes or your memory.
Recording and transcribing user interviews also promotes transparency and makes it easier to analyze your data.
Follow up with your users after implementing their feedback
Acting on feedback is more important than the feedback itself.
Once you’ve analyzed it, it’s time to implement it and improve your product.
Don’t stop there, though.
Make sure you follow up with your users after you’ve acted on the feedback.
Ivan is truly passionate about what he does. In his role as Lead Product Manager, his strength is shaping products that not only meet market needs but also wow their users. And with over a decade of experience at software companies and startups, he knows all the ins and outs of building successful products.
In his spare time, he enjoys staying active, whether it's hitting the gym, playing sports, or hiking. His dream office? A terrace in Komiža on the island of Vis, taking in the warm Adriatic sun.