Olive

Overview

Olive is an intuitive health & wellness app meant to encourage a healthier lifestyle by both integrating handling medical tasks, and pursuing personal health goals.

~ Hi-Fi prototype can be found here & at the end of this project ~

Purpose

This individual project was meant to showcase my knowledge, process, & skills as a UX/UI designer. I had the mentorship of a Senior UX designer.

Role

UX Designer, UX Researcher, UI Designer

Tools

Pen & Paper, Figma, UsabilityHub, Draw.io

Process

Design Thinking & User-centered Design

Understand

Before jumping into ideas, I went over the app requirements to really understand the scope of the project.

A competitor analysis was conducted on key competitors to understand the problem and market space.

Conducted a S.W.O.T analysis & UX analysis : Evaluated their usability, layout, navigation structure, compatibility, differentiation, and call to action. This helped identify product opportunities for an app that integrates handling multiple health aspects in a quick & trustworthy way while encouraging users to pursue healthier habits.

The Problem

Olive’s users need a quick & reliable way to manage personal, medical arrangements & follow healthier habits– such as engaging in physical activity, a healthy nutrition, & being informed on overall wellbeing.

Proposed Solution

We believe that by facilitating a way for users to manage real, medical tasks– as well as personalized, wellness features & informative facts– we will encourage users to prioritize their well-being.

User Research

To get a better understanding & observation of our potential users, I conducted a few interviews with 3 goals in mind:

Get a better understanding of how users handle medical tasks (physical & virtual) or maintain their wellbeing.

Learn more about what pain points users encounter while keeping up with their health needs.

Learn more about what incentivizes users to be consistent towards improving their health.

Prior to the interviews, I ran a short survey composed of 14 questions total, with 6 short free-response questions and the rest as MC. The goal was to obtain at least 10 responses. I obtained 14 in less than 3 days.

For the interviews, I recruited those who were genuinely interested in improving their health & had experienced tracking their health or booking appointments through websites/apps/ even phone.

High-level Insights

All participants are health-conscious individuals.

  • People get discouraged when appointments by phone are difficult or tedious to make.

  • Participants are struggling with keeping a consistent sleep schedule, which leaves them feeling lethargic.

  • People feel motivated by visual representations of progression, notification nudges, and/or motivational reminders.

  • Sometimes other things prioritize people’s health routines.

  • People need motivation and flexible options to make progression on a busy schedule.

Observe

For further analysis, I sorted through the data for behaviors, attitudes, frustrations, & needs/goals. Then, I used Affinity Mapping to cluster my data into user insights.

 

Affinity Mapping- Insights

Many users desire to establish consistency in either sleep, overall routine, eating habits, or physical activity…

  • People seem to be too busy to create a consistent workout schedule or to think about, & search for, healthy food alternatives.

  • Many lack motivation to workout.

  • Many people feel fatigued due to inconsistent sleep schedules. They wish to find ways to establish a routine or feel motivated to practice mindfulness and log their moods.

  • Participants predominantly contact providers the old-fashioned way (via phone) but some have had failed attempts at doing so online.

  • Some participants have messaged providers successfully but encountered minor setbacks. Also, busy parents wish to quickly and easily book appointments for their children.

  • People need to be presented with a variety of personalized workouts/meals/health feature options.

  • Motivational content may inspire users to make healthier choices.

POV

User Personas

Analyzing the findings gave me better insights into the target audience. I was able to discover how they interact with products and handle task management relating to discovering healthier choices or booking appointments. I was also able to dig deeper into what drives their internal and external motivations

To realistically portray our target users and establish empathy towards who we’re designing for, I created user two user personas. These were based off the data and user needs.

Persona #1

Persona #2

Once the target audience was put into a better perspective, I proceeded to map out user flows based on user behaviors and task management.

I created 3 user flows for my top 3 features…

User Flows

Entry Point:  Success Criteria:

1.Home screen Doctor visit is scheduled.

2.Dashboard/Medical

3.Visits/Appointments

4. Book new visit/appointment

5.Reasons for visit/Info

6. Choose doctor

7. Select date & time. Click save/confirm.

8. Confirmation shown/ back dashboard.

Entry Point:  Success Criteria:

1. Home screen  Appropriate workout is found and performed.

2. Workouts. 

3.Search for preferred workout

4. Select a workout

5. Save Workout & perform workout

6. Workouts.

Entry point: Success Criteria:

  1. Home. Reminders and desired sleep routine are set.

  2. Profile

  3. Sleep Tracking Settings

  4. Add sleep reminders

  5. Set a bedtime goal

  6. Set reminder frequency

  7. Profile

I mapped out user flows for the 3 main functionalities of the app. This way, I would know what steps the user would take to get to their desired destination before laying out the information architecture (IA). 

Based on my analysis and findings, I proposed the following sitemap…

Sitemaps

Proposed Sitemap

I created this sitemap with co-existing hierarchies so that users would have a general location in which to input their information as well as a page to find overall health-related information.  I also isolated the medical and mindfulness tabs. The goal was for all sections to be easily accessible.

However, after conducting open card sorting I validated some of my beliefs but invalidated others. I had to make refinements to the sitemap so as to accommodate user’s  mental models better.

Proposed Sitemap

Ideate

To establish how the app’s pages would be laid out before creating mockups & validating the content structure, I conducted open card sorting with real potential users.

I recruited 5 participants interested in completing a digital, open card sort. They created a total of 24 categories with a median of 4 categories each. I used OptimalSort and used all of the 20 cards allowed with the free plan to include the basics of the content that would be included on the sitemap. Based on the results, I iterated on the sitemap to produce the following:

Refined Sitemap

Analysis

After going through the data, I realized that my categories could use different naming conventions. Many participants separated physical aspects of health from mental aspects – which I was content about– but used slightly different terminology that was more upfront in its own way. Rather than ‘health and fitness’  and ‘mindfulness,’ these became ‘body’ and ‘mind,’ highlighting the area of focus in the user’s health as they navigate through. 

Also, although there were a total of 24 categories created, many of the categories were similar in their groupings – such as ‘profile’, ‘general’, and ‘tools’. Most of the users categorized medical information and tools together. However, the majority included ‘records’ under the category of profile or general tools and account features. Therefore, I decided to include records and inbox under the user’s profile. This was also the case for “inbox” or notifications.

Also, I realized that I could label “tracker” /“planner” as “Plan”  and integrate as a co-existing hierarchy for easy access. 

Low-Fidelity Wireframes

 

Before going digital, I quickly generated ideas for my main features on paper.

 

This feature was meant for users to quickly & easily navigate through the app’s workout page. It mostly shows high-level functionality and interaction.

Avoiding detail was a challenge, but these paper sketches helped me to focus on the high-level functionalities of the app.

 

This feature would allow users to easily book a doctor appointment with their providers or with someone new. Additionally, it shows the option of a virtual versus an in-person appointment.

 

This was meant to show how tracking sleep was integrated in the same location as non-medical reminders and to-do list.

Prototype

Mid-Fidelity Prototype

Using Figma to create my mid-fidelity prototype, I added more details to better communicate specific interactions. I focused on establishing a better sense of what would happen next when items were clicked on. I used grayscale to focus on the interactions before spending too much time on visuals.

Finding a Workout

This flow shows how users would be able to quickly search for workouts as well as where they would find their favorites. The green dots represent where users would click.

Booking a Doctor Appointment

This flow shows how users will be able to book a doctor appointment

Tracking Sleep

This flow shows basic functionality of tracking one’s sleep, including usability pointers.

High-Fidelity Prototype (not final)

For my high-fidelity prototype I focused more on the placement, fonts, and button sizes. I wanted to generate the look and feel of the app, adding minimal color & omitting specifics.

Finding a workout

Booking a Doctor’s Appointment

Tracking Sleep

 

Exploring Desktop Design

Although I was focused on a mobile-first approach and on mobile device testing, I created a few desktop designs for each of the flows in order to depict how the design could transfer from one screen size to the next. This image shows the first step when booking a doctor appointment.

Test

Usability Test

After conducting a series of moderated and unmoderated usability tests with 6 participants, I sorted out the data into an affinity map and used a rainbow spreadsheet to showcase which data point– or error found– belonged to its corresponding participant. Then, I created the following affinity map to identify insights.

Affinity Map

The map helped me further understand user attitudes, needs, and expectations. The rainbow spreadsheet also helped me rate the errors based on frequency and usability issue. After this, I proceeded to make fixes based off my prioritized errors.

Takeaways:

  • It’s important to make the users feel at ease and make sure that tasks are easily understandable.

  • The “Sleep Tracker” feature could probably be placed under the “mind” or mindfulness page as five of six users navigated to that page when listening to the task.

  • The flow for booking a doctor’s appointment could use clarification and updates on the UI for trustworthiness.

  • Sometimes it is necessary to improvise when asking users to navigate through your prototypes so as to dig deeper and gain a better understanding of their feelings and perceptions.

 

Updates based on testing

I made the following updates based on testing. Additionally, some of these updates were verified with A/B testing through UsabilityHub, including a response of 13 participants.

Users should be able to click on an appointment in order to edit it. The edit current appointment button was deemed unnecessary, and I agreed.

 

This change made the items look more clickable, but most importantly it clarified that this step was simply a verification step (all insurance or payment info has been logged). After more ideation, this was removed from the flow, and users would simply do this on their settings.

 

This page was added to the flow so that users can have the option of booking an appointment for their family/ children.

Rather than having the user guess their sleep quality, the app would eventually let them know based off of their input.

 
 

Users preferred to see their average sleep first over their weekly progress. This was also verified with a preference test.

 

This page was added so that the app had a better way of calculating the user's sleep quality. The bedtime widget was also not needed during the sleep tracking flow. It could be found within the sleep-related settings. 

Design Language

After spending more time on implementing visual design principles, and incorporating grid fundamentals, I finalized the design language so as to refine the user interface of the app and establish a better consistency, including button styles and icons. Below is my color palette:

Colors were based on what was needed to invoke within our users. The goal was to promote an enthusiastic, light-hearted, and productive way of handling health-related tasks. For instance, since blue increases productivity and is related to the medical field, I used a light-hearted blue to highlight these tasks. And since lavender promotes relaxation, I decided to use it for the mindfulness/sleep page.

Figma:

Tell Story

Designing for Accessibility

After creating a style guide and receiving feedback from a few designers, I made sure my design was more accessible/inclusive. The following changes were implemented in order to improve the accessibility and usefulness of the app.

Here, I made sure the input fields had a greater contrast with the background color to improve visibility. I also added placeholders to clarify what type of information is being filled.

Initially, users would be able to view all their upcoming appointments once they began to scroll. However, this left doubt as to whether or not the functionality existed. For clarity, I decided to add a ‘view all’ button underneath (eventually made the button a small text ‘View All >’)

Additionally, I accentuated the top bar navigation by adding a line across the labels so that they are easily grouped and spotted by users.

 
 

The visibility of the estimated time to complete a workout or recipe was too dependent on its contrast against the images.

For consistency and greater visibility, I decided to add a dark blue bar with white text on each content card. This way, users can easily spot the approximate time an activity will take.


Updated/Final High-Fidelity Prototype

After an iterative process, I went through a lot of changes and discoveries that helped me create a well-suited platform. I focused on maintaining a user-centered approach by iterating to their needs and making sure the app was intuitive and accessible. I applied design thinking, which is definitely an iterative process that helped me diverge and converge on solutions that fit my target audience. Then, I used rapid prototyping to iterate on my prototype.

Although I faced some challenges along the road– such as iterating on the IA, receiving conflicting feedback, and realizing I had made a few design mistakes– I learned a lot by applying what I learned from interviews and critiques. Below is the updated prototype. I’ll leave the Figma link here!

Conclusions

Going through this process really shed a light on maintaining a user-centered approach when designing usable, intuitive platforms.

Using the design thinking process, I was able to continuously grow and iterate as a designer. This helped me catch discrepancies in my designs and allowed me to use raw user data to create a product that would better benefit the intended users.

I plan on iterating on my designs to refine accessibility and hope to conduct more user testing to better accommodate their needs! I know my designs are not perfect and hope to introduce a smooth onboarding flow for setting up a doctor appointment as a newcomer!

~ Thank you ~