Module 6: Turning research findings into persuasive and usable outputs
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 6th 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
- present your research findings in a way that your stakeholders can pick up and use
- choose the best method for presenting insights depending on who they’re for and how they’ll use them
- write clear user needs, hypotheses and stories, and agree ‘acceptance criteria’ for when these can be considered met
- understand the difference between user journeys and service blueprints
- create user personas and empathy maps
How to create research outputs with your audience in mind
How you present your research will depend on what your intended outcome is, who you’re presenting to, what they need from your research, and how the insights will be used.
Different people will respond differently to different outputs, so it’s really important to think about your audience. You need to consider who you’re presenting your work to, what motivates them, and what barriers they think there are to acting on your research.
Motivations
At a very high level people are often motivated by:
- fears of something bad, a known risk or something unexpected going wrong
- hopes of something good, a goal or ambition
Barriers
It’s difficult to talk about the barriers to implementing research findings at a high level because they can come in so many different forms, but there are some blockers we often see:
- financial – there’s not enough money to do something
- policy or legal – something doesn’t fit within the rules
- time – there’s not enough time to do something
- effort – there aren’t enough people to do something
- value – stakeholders don’t see the value in doing something
Your best bet at moving past these barriers is thinking about your audience when you create your outputs.
At the very least, your research should make it clear to them what the priorities are from a users’ point of view.
How to share research findings as you go
Sometimes stakeholders don’t fully understand research outputs when they get them all at once at the end of a project. We’ve found it really helps when we share what we learn as we learn it. One of the best ways to do this is through ‘show and tells’, which offer a regular opportunity to share:
- what we did
- what we learned
- what we plan to do next
The other benefit of sharing this information regularly is that it forces you to think about what’s relevant to share and the best way to share it so that it’s quick and easy to understand. In our experience sharing information this way is much more effective than in a long and complex report at the end of a project.
Tip: Show and tells are also a great opportunity to ask your stakeholders for feedback or to help unblock you on a task!
How and when to produce research outputs
Try to work on research outputs collaboratively
Like analysis, it’s easier to produce useful, objective outputs when you work on them with other people.
If you can’t do this it’s not the end of the world – creating outputs doesn’t require any skills that you don’t have as a researcher. But if you’re working alone you’ll need to think very carefully about being objective and using your time in the best way.
Co-designing your outputs with the people who are likely to use them means they’ll be more accessible and easier to maintain. You want research outputs to be something that anyone on the team can use and explain, not just something the researcher ‘owns’.
Develop your research outputs iteratively
There will be a point during analysis when you feel confident enough about what you’ve learned to draw a conclusion and make recommendations. After this point you should develop your outputs iteratively, describing what you’ve discovered and adding to or adjusting your description in stages rather than all in one go.
Updating your outputs as you learn new things throughout the project means you have living documents which are always up to date. If you keep your team involved in this process too you’ll help them understand how the research might affect the work they’re doing.
How to make research outputs usable and effective
The people using your research outputs to inform their work need to:
- know where to look for them
- be able to find their way through the information
You need to think about where you keep the outputs and how you make sure their content is understandable and usable.
It helps to know when and how your research outputs are going to be used. For example, if the information is going to be broken down and used out of context in a backlog of tasks we need to consider how the outputs will perform when they’re scrambled up in this way. If the insights are going to be used in presentations or business cases we need to consider how we make the information succinct while maintaining the integrity of the research.
How to choose a research output
There are so many tools and mediums you can use to share research findings – too many to cover in one module! At Paper we commonly use:
- personas
- empathy maps
- user journeys
- service maps
- hypotheses
- business cases
- user needs, user stories, and job stories
We’ll go through the details and some of the risks of each so you can compare.
Personas and empathy maps
Personas and empathy maps help you share findings about groups of people you have identified within your research.
There are plenty of examples on the web and we would encourage you to pick and mix the elements that you think will best represent your findings.
- Personas usually describe the group along with their:
- goals
- pains or frustrations
- Empathy maps usually describe the group along with the things they:
- say
- think
- do
- feel
Risks of using personas and empathy maps
Personas and empathy maps present an amalgamated ‘idea’ of what groups of users need. The risk with this is that people can become dependent on them and use them to make assumptions about those groups, rather than referring back to direct evidence.
Sometimes personas and empathy maps are developed without any actual research to back them up, in which case they just present a set of assumptions about a group of people. You should only ever create these outputs when you have enough research insight to do so.
User journeys and service maps
User journeys and service maps are different tools but they often get conflated.
- A user journey represents the users’ experience of completing a task from start to finish. In research we focus on the existing or ‘as-is’ user journey to represent the experiences users currently have, whereas designers may also look at the ‘to-be’ version to visualise how an experience might look in the future.
- A service map or service blueprint can represent not only the journey of your users but also the interactions, processes and infrastructure that the service is made up of, including what the service team needs to do.
These are useful tools for explaining the experiences people have because they show how things happen along a timeline which is easy for everyone to understand.
Risks of using user journeys and service maps
User journeys and service maps can be risky because:
- individual experiences can become lost when they’re grouped into a single journey
- service maps in particular can get very complex and contain so much detail that they become difficult to use
Hypotheses and business cases
As user researchers we’re sometimes asked to provide recommendations based on our research. These might be ideas for further research or opportunities to make changes to a product or service.
- Hypotheses are a way for us to describe an idea that requires further research. We have a format for these that we use but again, there’s plenty of stuff online if you do a quick internet search.
- Business cases are used in some organisations to put forward a suggested change or piece of work. It’s not always easy to incorporate research insights into a business case, so we’ve created an opportunity card as a concise way to represent our findings and what we recommend doing next. We’ll share the template with you on the Learn to do user research course, but in it we include information like:
- a description of the idea
- how it meets user and business needs
- the expected time and money needed to implement the idea
- any potential barriers to implementation
Risks of using hypotheses and business cases
The risk with both of these is that they require us to think as a researcher and a designer at the same time, and we need to remain objective about our ideas or recommendations.
User needs
User needs are one of the most important outputs from research. They can help align teams in thinking about things from a users’ point of view and encourage people to consider how their choices will affect users.
We sometimes write user needs as statements and sometimes use formats like user stories or jobs to be done to help us communicate them in a consistent and clear structure.
Risks of using user needs
These outputs can be difficult to write. You’re combining and condensing what you’ve learned, which means there’s a risk you bias or assume too much.
It’s also tricky to avoid writing needs as solutions, assuming that we as researchers know the best way to meet the need. They should be written in a way that’s open enough that the team can work collaboratively to find multiple possible solutions to try.
How to write user needs as user stories
User needs are a priority for any user researcher, so we thought we’d go into a bit more detail about how to write them.
A user story has three parts and is usually presented like this:
As a… (who the user is, including any context that’s relevant),
I need… (what they need to happen, have or do),
so that… (how the user will benefit or what they’re trying to achieve)
Here’s an example:
As a user researcher at the start of my career,
I need to learn the foundational skills involved in doing good user research,
so that I can do my job well and with confidence
User stories should:
- be based on evidence – if you’re struggling to feel confident about a user story then you may need to do more research first
- be written using the language a user would use, not the language you, your teams or stakeholders use
- not describe a solution, no matter how tempting it is – user stories are there to help you understand a user’s need and empathise with them, they are not a definitive specification of what to do to meet the need
- describe what a user genuinely needs, not what they want or have asked for
- describe a single need – if you find yourself writing multiple clauses or sentences, consider whether this could be split into multiple stories
How to measure success
To make our research engaging for stakeholders we need to make sure the findings we share are actionable for specific teams and individuals, while ensuring it doesn’t lose its integrity.
How to agree and track acceptance criteria
One way of ensuring your research keeps its integrity is to attach acceptance criteria to any user stories, jobs to be done or similar versions of user needs.
Acceptance criteria are a way to test if a piece of work has actually met an associated need.
Including acceptance criteria is a useful way to ensure that outcomes are anchored back to the needs of the user. Acceptance criteria are often written in the format of:
we will know this is done when…
It’s important to write these with other members of your team so you have agreement on what the acceptance criteria are.
How to track the success of your research
As a researcher one of the outcomes you might be interested to track personally is whether your research is being used in one of the following ways:
- To inform strategy – When the research provides the evidence to change the strategic direction of an organisation
- To create goals – When the team reference what they’ve learned from research in their next sprint goal or roadmapping work
- To set tasks – When user needs are used to describe part or all of a task that will be worked on by a delivery team
How to use KPIs
A KPI, or key performance indicator, is a metric used to measure the performance of your product or service against a specific objective. You can use a number of different metrics to measure your work and they can align with your organisation’s strategy, goals, tasks or user needs.
It’s important to monitor your KPIs and iterate them as your service or product changes. They need to stay aligned with objectives and the intended benefits of what you’re trying to achieve.
We also want to make sure that KPIs aren’t fully focused on organisational goals but that they’re also aligned to a user need. For example, if the organisation’s objective is to save money on customer support by reducing the number of support tickets, think about what that means for your users.
This extends to thinking about any negative implications your KPIs could have for users. For example, when the UK government introduced the KPI that everyone in the country should be able to see a doctor within 48 hours, surgeries changed their processes so patients could only book within 48 hours. You can watch a 2 minute video of people talking about the negative implications of this.
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