Testing a tool that helps people find the right help
The goal of this work was to help Deaf people, people with hearing loss or tinnitus, and their family and friends, find the information they need. On this project, I was a User Researcher at the Royal National Institute for Deaf People (RNID).
Context
When I joined RNID, a charity that supports deaf people and people with hearing loss and tinnitus, the team was starting to build an online tool that lets people find the right information or support for their situation.
I was asked to test the tool’s usability and content with users. There were a few different journeys in the tool, so, to begin I mapped each journey and identified an approach to the product research.
Plan
I met with designers to learn about the different journeys, potential risks and their questions. Then, I planned rounds for different journeys, sequenced based on what was ready, who to recruit, or other dependencies.
I wrote objectives specific to each round, and overall for the study:
- review if people know why they are answering questions
- review whether people can go through a journey without support
- review content to see if it’s clear, useful and offers a next step
Collect
I planned rounds of moderated interviews with people who are deaf, have hearing loss and tinnitus, and the people who support them.
I chose to do moderated testing because some of the prototypes still had limited capabilities or journeys that didn’t end.
Because user research was new to RNID, moderated testing also gave designers and other collaborators the chance to interact with participants and learn from them in real-time.
Make sense
My research highlighted a number of moments where people were missing a Call to Action or didn’t understand which option to choose.
In other cases, I noticed that people felt unsupported by the tone of voice or untrustworthy of the organisation, particularly when we asked them to sign up for emails at the end of their journey.
I also uncovered a larger design question when I learned that people may expect to choose multiple options, something we still needed to consider.
Share
Because I was new to the organisation, this was the first time many content designers and subject experts at RNID had tested their content with our users. So, I brought people along the research process showing them how we can do research across our products and services.
This engagement also helped when it was time to share findings, which I did by mapping insights across the journeys and then suggesting changes, because people understood the process we went through to learn them.
Impact
Testing early helped us uncover pain points that would have stopped people from getting through their journeys, and abandoning the tool altogether. If we hadn’t found the problems early on, we wouldn’t have been able to learn as much when the tool was live.
We continued to monitor live feedback and make iterations to address important pain points over time. From Google Analytics, we saw that the majority of people could get through to their results and 56% of people found out they have or may have hearing loss.