Module 1: Framing the right research problem
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 1st 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
- reframe assumptions and solutions as user-centric problems to solve
- interview stakeholders to understand their research needs
- translate business strategy or policy into research objectives
- get the scope of a research project right
- explain the difference between a product and a service
- advocate for user research to create change in your organisation
Framing the right research problem – Why it matters
If there weren’t problems to solve there wouldn’t be any work for us to do. When we talk about new projects or new pieces of work to be done it’s helpful to begin with thinking about the problem that needs to be solved.
How you describe a problem will have an important impact on your user research. It can affect who you do research with, how the research is done and how valuable your outcomes are. Describing a problem in the right way means you can prioritise and plan the right research too.
The way a problem is framed will always be biassed in some way by the perspective of the person, or people, who are describing it, even if it’s you doing the describing. So we need to try to frame a problem from a user’s perspective.
In our experience as an agency that works with lots of organisations we have the advantage of being objective. But whether you’re working with or for an organisation, it’s important to be objective about the problems you need to solve so you can see it from a user’s point of view.
Common problems with problems
There are some common problems that we often see at the start of projects with how organisations are framing their problems.
If you’re new to framing problems, it’s helpful to keep an eye out for them. We often notice that:
- the problem is business centric and missing the user’s perspective
- the problem is too big or too small to understand or solve all at once
- people are too quick to jump to solutions for problems, before they fully understand them
How to understand what a team needs from research
To frame the scope of your problem and understand how to solve it for both the organisation and its users, you’ll need to understand what senior stakeholders are trying to achieve. You’ll also need to understand what the rest of your team need and expect from your research.
The things we learn about in our research are usually relevant to lots of different people with different roles in the team and wider organisation. It may seem obvious, but before you plan your research, you need to chat to the people in your team about their needs and expectations. We’ll go through how you might do this on the course.
Having these conversations also helps to get people engaged in the research early on, which can make it easier to get people to help with the later stages of your research, like analysis.
How to describe a problem using ‘How might we’ statements
Designers often use ‘How might we’ statements to frame opportunities to solve problems, but they work equally well when used to describe the questions you want to answer with your research.
Example: How might we redesign the service to focus on making sure people living in rented homes are safe, warm and dry?
The statement should be specific enough to keep you within your project’s scope, but open enough to not restrict your findings.
They normally take a bit of refining and are best written by a group of people rather than an individual researcher. You normally go through several versions before you get to a statement that feels right. Often we end up with more than one, which is helpful for seeing that there are different problems to solve and we need to help our team and stakeholders to prioritise.
On the Learn to do user research course, we’ll have a go at reframing some problems in this way together, focussing on the outcomes the team needs to achieve.
How to influence stakeholders and advocate for user research
It’s a skill to be able to spot issues with the problems you’re asked to solve, but it’s another to present this thinking back to the organisation in a way that they understand why they should reframe the work, or why user research matters.
There’s always an element of negotiation involved, which is why it’s helpful to understand the motivations of your stakeholders first.
For example, it can help to demonstrate the value of user research in:
- ensuring time and money is invested in designing the most useful features, products or services
- learning how to give customers enjoyable experiences so they continue to choose your product or service over competitors’
We all know change doesn’t happen overnight, but there are some things we can do to promote user research, like:
- work in the open
- involve your team and stakeholders in observation
- involve colleagues in analysis
- give regular playbacks
We’ll go into more detail about how all these things can help on the course.
Next module →
Go to Module 2: Planning and designing user research.
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