Rebeca Viana
💬 Product
UOK is a well-being product designed to help teachers proactively support their student's well-being. Every day students log in to UOK and answer a series of questions expressing how they feel. The current daily wellness check-in experience of UOK is basic with students answering a series of questions using a color-coded rating scale from 1-5.
We’d like to improve this daily wellness check-in experience by making it more appealing for students to answer questions each day and be able to visualize their wellness journey with UOK.
I worked on this case study during Memorisely UX/UI Design immersive online Bootcamp. During the Bootcamp I worked with a small team designers around the world. The goal of this case study was to find a more engaging way for teenager students to answer how they’re feeling, everyday.
User Research
Product Strategy
UX Design
UI Design
Prototyping
Usability Testing
FigJam
Figma
Maze
5 weeks
The current daily wellness check-in experience of UOK is basic with students answering a series of questions using color-coded rating scale from 1-5. We’d like to improve this daily wellness check-in experience by making it more appealing for students to answer questions each day and be able to visualize their wellness journey with UOK.
We believe that creating an engaging journal experience
For students
Will allow them to share their feeling in a daily basis
To help me better understand the product, I conducted a usability to identify pain points and wow moments in the existing experience
➡️ Friction Moments
➡️ WOW Moments
➡️ Friction Moments
➡️ WOW Moments
👀 Competitor Benchmarking
With a usability review complete, I moved on to competitor benchmarking to help me identify standards in competitor products that could be used to improve the existing experience.
➡️ At this point, as a user, I was worried of having my notes at homepage.
I then had to change this concern because the app has a “Lock” option that would work like a key to your journal.
Edit an entry
Statistics & More Menu
👀 Questions & Observations
To help me better frame any problems with the product, I began by forming some questions and observations I have about the product. To easily document these I followed the structure [situation], [response], [problem to business or experience] to ensure I'm aware of users and business needs.
When the questionnaire is not engaging, the student might not answer genuinely, which causes an inaccurate response.
When there’s no app reminder, the student might forget to do their entry, which causes inactivity.
When the questionnaire is completed, the student gets streak points, which causes confusion about the app scoring system.
When the UOK App doesn’t display the entry history, the student can’t see their journal, which causes lack of trust as a mood tracker app.
When the UOK App doesn’t allow to view or edit your entry, the student feels disconnected with their log, which causes lack of trust as a mood tracker app.
✍️ Assumptions
Users goal Business goal
We believe that making the questionnaire more engaging [creating the experience]For the students using the UOK App [persona] Will allow the student to have a safety place to share their feelings and increase the use of the UOK app as a mood tracker [Achieve this outcome for the business and user]
With a hypothesis set, my next step was to synthesise real survey data gathered from the product team to identify pain points from existing users
Primary Frustration
When the questionnaire is not engaging, the student might not engage with the app, which causes inactivity or lack of use as a mood tracker app.
Other observations/frustrations
When there’s no app reminder, the student might forget to do their entry, which causes inactivity and inaccurate statistics.
When the UOK App doesn’t allow to view or edit your entry, the student might feel disconnected with their log, which causes lack of trust as a mood tracker.
With a picture of the problem at hand starting to come into place, we jumped into the ideation phase and worked through the solution design model, identifying the user's actual behavior, and optimal behavior. This allowed me to form a how might we statement to begin forming a solution.
How might we make it easier and more engaging for students to share their feelings everyday?
How might we improve the entry fields options for students to expand on their questionnaire answer and daily entry.
To avoid following the first idea I conducted a series of ideation techniques. This allowed me to consider an array of solutions. Following ideation, I mapped what could be improved or added to the product.
What can I improve?
What can I add?
Following Ideation, I created user flows of the existing experience and improved the flow based on the idea that fit with business and user goals
User Story
As a High School Student, I want privately share how I feel, so I can navigate my feelings and get help.
I used a neutral color palette to avoid any decision bias and would use this prototype to get feedback internally.
To create the high-fidelity prototype I inspected the style of the products and followed the 8pt rule to effectively and easily create a prototype that was consistent with the product styling. Before creating the prototype I defined styles and components to easily and quickly help me design consistently.
Below is the final version of the prototype that I created. I included interactions and transitions from Figma to match the product flow.
With the hi-fi prototype created, I formed a testing script with scenarios and tasks for the user to complete to validate the prototype with real users. To test the prototype I used Maze and gathered feedback following every task.