Asking useful questions that generate valuable answers is a skill that takes time, practice and experience.
It can also mean the difference between a valid test and a complete waste of time and money. If you’re a UX research newbie though, there are helpful rules to get started in writing useful questions that deliver genuine, valuable insight.
At a basic level, asking ‘the right’ questions means encouraging users to share their point of view, without your influence or bias.
Your job as a UX researcher is to uncover truth and honesty. Your job is to gather user feedback that isn’t colored by your own hopes or expectations. Your job is to listen, and to be deliberate with your words and actions.
To ask good questions in an in-depth interview – the ones that get to the heart of the user experience – you should consider the aim and scope of your UX research.
With these in mind, you can plan questions that will help you discover what your user’s goal is when using a product and how they go about achieving it.
With this information in place, you can begin to explore what works well, what works not so well and what doesn’t work at all for users.
Remember to explore all three of these areas as fully as possible. The point is to discover problems that currently exist, but it’s also good to highlight what is working well. Don’t dwell on them too long, but it’s good to report positives back to stakeholders, as these can help ‘cushion the blow’.
Your time with the user will be limited, so you’ll want to stick to the task at hand, but always keep an ear out for behavior or comments you weren’t expecting – as ultimately these can all help improve the overall experience of your product.
At any point while using a product, there is a natural next step that your users will want to take (i.e. when you add a product to a basket, you might expect to be offered the choice to view the basket or continue shopping). A key part of your questioning will be to ask users what they expect those next steps to be.
Knowing what your user’s expectations are will help you build workflows and customer journey maps to match them. And the only way to find out what those expectations are, is to ask users directly.
Other questions may deal with their initial impressions of a product, their feedback about common examples of use of the product, and their comments on any changes you may have in mind for an existing product or service.
Before you ask users your questions, try them out on a test audience. This audience can be people you know, who you can rely on to give sincere and constructive opinions on whether your questions make sense or not. You may want to prepare a cup-of-tea/stiff-drink and the quiet room.
After you’ve finished the test, the answers will be collated and analyzed. It helps to consider this stage when coming up with your questions beforehand. Your users’ responses should be actionable, either directly or after analysis (i.e. offers practical guidance on how you can improve the product).
If you cannot see how you will practically use the responses to improve user experience, then think of a different question. Analysis of quantitative data may be easy (count the number of yes and no replies), but this is more complicated to action. Information from qualitative questions may be harder to analyze but can give you a clearer picture of how to improve your product.
For an in-depth and entertaining guide to getting started with user research, read our free-to-download, comprehensive ebook ‘User Experience Research 101’
The questions themselves can be organized into three stages.
You start with a broad introduction, then a focus on the specifics, before ending with a more general perspective.
These three different phases can look like the following:
#1 Opening section
These are broad questions, where you find out about your users’ work, use of the product and any overall feedback they may have. “Tell me about a typical day for you at work?” and “What are your biggest daily challenges at work?” are typical icebreakers.
#2 Middle section
This is more focused. Ask for opinions on specific features of interest that are tied to your research goals, why they hold these opinions and what they expect to see or achieve.
#3 Closing section
When announcing the end of the session, you can open opportunities to gain extra information and insights. Users often feel more able to express themselves freely at the end of a session as though the pressure is off, so don’t ignore the value of the closing section. Instead, use it to ask pivotal questions like “If you could change one thing, what would it be?” or to rate their experience, or ask how useful they think a specific function or feature will be for them.
Often without meaning to, we can influence people’s answers by the way we phrase a question.
Here’s an example of two very similar questions that could lead to wildly different answers:
In the first question, we’re restricting the answer to only the good things they’ve discovered about your product.
In the second question, the field is open: the user can reply with good things, bad things, or both, depending on the feature.
We might not like the answer to question 2 as much as question 1, but it’s the answer to question 2 that’s the one we need to hear and will make a difference.
Also keep in mind that what users say and what users do may be two completely different things. Remote observation of how someone uses a product or service may uncover important truths that simply talking about it may not have revealed.
Think of the following list as the basics you always need to cover, no matter what specific area or product you’re working on.