Module 2: Planning and designing user research
These training resources accompany our 2-day practical training course, Learn to do user research.
The course includes conversations and activities to help you apply everything you learn and an opportunity to get feedback from our experienced user researchers. It will give you all the skills you need to start or develop your career as a user researcher.
See more details and sign up for Learn to do user research.
This module is the 2nd of 6 modules in Learn to do user research
- Framing the right research problem
- Planning and designing user research
- Recruiting research participants in a mindful and ethical way
- Facilitating and observing user research
- Analysing research findings
- Turning research findings into persuasive and usable outputs
By the end of this module you’ll be able to
- plan efficiently and effectively, to unblock the design and delivery of products and services
- identify the best people to research with
- choose the right research method to get the insights you need
- frame research questions as hypotheses that you can prove or disprove
- design a user research interview and discussion guide
- design a usability test
Planning and designing research – Why it matters
Planning and designing research is an important but often overlooked stage of the process, and a key skill to have as a user researcher.
Researchers need to take the time to think about the people involved in research and our responsibilities to them. At the same time, we need to plan quickly to provide our teams with the insights they need so they don’t become blocked – or proceed without any insights at all.
As user researchers we need to be able to analyse the problem we’re looking into and match it with an approach that’s most likely to give us the best insight. We need to be open minded about which kind of research and which research methods are most suitable for the problem we’re looking into.
We also need to be able to craft questions and set tasks that will give us insight into the users needs without biassing their responses or behaviour. All of this takes planning and design.
How to choose who to research with
When thinking about which groups to invite to research, you need to think back to your original problem and consider:
- which users might have the most or the biggest problems using a product or service
- how a user’s environment might affect their experience
- whether the frequency of use make a difference
- whether the recency of use make a difference
- whether the user’s background has an affect
In module 3 of the Learn to do user research training course we’ll look at how many participants is the right number for research. We’ll also think about how you might prioritise contacting these people depending on your answers to the questions above, and how easy or difficult different people might be to reach.
How to write hypotheses to test
Start by capturing high-level questions from your stakeholders and team mates - what are they trying to learn?
Your stakeholders might already have ideas for solutions to a problem. In this case, it can be useful to write these ideas down as hypotheses to show how research can test and validate any assumptions.
Hypotheses show who your users are, what they are trying to do, the solution you’re looking into, and the method you’re using to test it. They follow a set format:
- For… [a person or a user group]
- Who are trying to… [do a thing]
- We think… [your assumption or idea]
- We’ll know this is true when… [how you will test this assumption or idea]
How to choose a research method
There’s a lot of jargon used around research types and methods and it can sometimes be confusing.
You may have heard about types of research like qualitative and quantitative, exploratory and evaluative, formative and summative. There are also lots of different methods, like:
- Interviews
- Usability testing
- Survey
- Card sort
- Contextual enquiry
- Unmoderated testing
- Desk research
- Co-design
- Co-research
These all have different benefits depending on the problem you’re looking into. We’ll go through all these together in the training course, but here’s an example:
| Method | How does it work? | What would you expect to learn? |
| Interviews | Asking people questions about their experiences |
Thoughts, feelings, experiences In-depth information |
| Usability testing | Setting people tasks, observing what they do and listening to what they say |
How people respond to your designs How you might improve your designs |
| Survey |
Having a set of questions that you want to learn from a large group of people Can be closed or open questions |
The scale of the problem you’re looking into |
How to design a user research interview
Our goal with an interview is to ask questions that help someone to recall their experiences as accurately as possible.
To aid us as researchers we will usually create some sort of discussion guide to help us to remember what we need to cover in the interview.
How to write a discussion guide
You should start any interview by making sure your participant is comfortable, they feel safe, and they are 100% clear about what they have consented to do. You can do this by asking certain questions and providing your participant with certain information. We have some best-practice examples for how to do this in our user research pattern library, which is free to use.
In most situations, it’s best to write your interview questions in the order that makes the most sense to your participant, for example to follow a timeline they are likely to have experienced. In exploratory research where little is known you may have to make some assumptions here. At the very least you will need to pick a beginning (when the participant first encountered the problem) and an end (when the problem was solved for the user).
How to write interview questions
Ideally, in qualitative research, we’re interested in participants telling us about their experience. This means it’s important we ask ‘open’ questions rather than ‘closed’ questions.
A closed question might be: Did you find our product online?
An open version of the same question might be: How did you first find our product?
The closed question only has 2 answers: Yes or No, whereas the open question gives your participant the chance to describe their experience.
We would always recommend you write discussion guides with other people to help you check if your questions are open and unbiased.
How to design a usability test
In usability testing you give users tasks to do as well as asking them questions. Your aim is to set tasks that a user would really do, and then observe how they do them. As the participant performs the task you want them to describe what they’re doing and thinking so you can understand their experience.
You may need to steer participants to specific elements of your prototype, product or service that you’re trying to test. In that case, you’ll need to design the task and set the scenario so that, as much as possible, this feels natural to the participant.
For example, you may want to test your video conferencing application but you might first want to see how people discover it. In this case you might set the first scenario and test as:
Scenario: You need to use video conferencing for your job.
Task: Please show me how you would search for a video conferencing application.
Here we might expect to see the participant use Google, the app store, or another place to look for video conferencing apps, but they might not find the one you want them to test. So after observing this you may need to move them onto your application so you can set the next scenario and task you’re interested in observing.
Next module →
Go to Module 3: Recruiting research participants in a mindful and ethical way.
Sign up for ‘Learn to do user research’
Our 2-day practical training course, Learn to do user research, gives you a complete foundation in key user research skills.
Join experienced user researchers at Paper to learn key skills and put them into practice, with lots of opportunity for questions and feedback.
Follow Paper on LinkedIn