Millions of people suffer from chronic pain every day. Remedy aims to help people that are affected by chronic pain to find relief through mindfulness-based stress reduction protocols. Studies have shown that these methods can be an effective treatment for various chronic pain conditions.
The founder approached the team when his application was experiencing a 0% retention rate, and about a 20% conversion rate. He wanted us to design an on-boarding experience that convinced his users to trust the suggested methods of treatment.
We aimed to create an educational and engaging onboarding experience that builds trust and communicates the efficacy of these treatments.
In order to do so, we had the following goals:
First, we interviewed people who suffer from chronic pain to gain an insight on their history of pain and the steps they’ve taken towards finding relief. We then gave them the task to use the current app and complete the fist lesson to uncover the major pain points within the initial on-boarding experience.
"I felt like I was forced to listen to the first lesson. I wasn't expecting a two minute audio intro"
In order to discover what makes for a good on-boarding experience, we looked at competitive and comparative apps such as Curable, Mend, Headspace, and Duolingo to understand how their onboarding process works and how to keep users engaged with potentially sensitive topics. Common elements included explaining core features, the ability to customize the program, and providing a clear value proposition from the very beginning.
To understand what type of copy helps establish trust in the case of such a sensitive topic, we took copy from various articles, scientific papers, and apps talking about chronic pain and asked people who suffer from chronic pain to highlight words that they found trustworthy or not. We compared all the test results to give us an insight to the type of language to use that would help establish trust among users.
Through the feedback received from the various research methods, we decided to guide our design exploration around two key principles:
The dashboard wasn’t part of the original scope, but it turned out to be a large element within the project. It didn’t go through a comprehensive design process and the feedback from the validation testing was a result of that. Throughout the design process, there was an emphasis on constantly developing creative solutions for users, but they may not necessarily be the ones users asked for.
While this may be the one of the most common and easy mistakes to make, making assumptions about the user is never helpful. Assumptions can work out in some circumstances, but it’ll mostly lead to confusion and more issues - as reflected with the feedback via the prototype.
Throughout this project, I learned how to capitalize on the value of our research and refine the design process to effectively curate a streamlined experience.