User testing
We interviewed 5 participants who were current Carepass members and had done user testing
in the
past. We also looked for users who had a type of disability that they needed technical assistance.
Our goals:
- See their expectations regarding the dashboard
- Gather their thoughts on the current information about Carepass on
the page.
- If the participants could navigate to the dashboard page
With the data collected from the testing, we learned the following:
- 3 out of 5 participants suggested reorganizing the content and the information that
needed
clarification.
- 2 participants thought that the cancelation call to action should be more visible.
- 2 participants users said there was significant white space on the page.
- All participants identify seeing membership information as the top 3 important to
them.
- All participants responded that they were satisfied with the current. Dashboard
content.
Even though we conducted user testing and user interviews, we used the CVS persona Micheal to
sync up with CVS to ensure we were going with other users' goals.
Wireframes
With the information gathered and syncing with the CVS persona, other designers and I worked
together to see how to make the information flow and not repeat information. The wireframe was also
where we ensured that people who were a part of the project and other teams aligned on how to
present to the information. on how data would be presented.
High-fidelity prototypes
At this time, Carepass was also introducing a new feature for gaining rewards with the number of
steps users take. Leadership wanted to make the feature a part of the dashboard. With that
additional information, we needed the following experiences:
- New user
- Existing users, with or without the reward
- Able to add new features
- Showing available promotions that connect with the membership - for example, the monthly
free $10
Handoff
The discussion and handoff were broken down by feature container so leadership
and developers
could plan building.
For the developers, I did provide the following information in the Figma file:
- A11Y markups
- Components and elements
- Clickable prototypes
- Interaction notes
- List of Components, existing elements, and new elements
Takeaways
Imapct
With the updates on the memberships, customer service calls dropped by 33%, and users did cancel
their membership for a period and had a 25% increase in returns.
Did we answer our questions?
There were a lot of challenges with this project, like Figma being new to the team, a lot of
different departments and people's feedback that needed to stay with the project's goals, and the
tight deadline. I believe we achieved the goals of simplicity, ensuring we do the best accessible
design practices and the ability to add information in the future.
Next steps?
- Collect the data from the A/B Test
- Do another user test with the updated pages