PolyCares+

UX/UI Case Study

 

Care For All Students

If there was one thing that Cal Poly students had to say was the most frustrating about the campus, it would hands down be the Health Center. There was never any clear communication between students and the Health Center. Most complaints from students would be constant confusion, increased wait times, and scheduling inconvenience. There is no mobile app that has attempted to relieve any of these problems so the Health Center reached out to us Graphic Communication students to figure out a solution.

March 2018 – June 2018

Design Tools

Adobe XD - Wireframing & Prototyping
Adobe Illustrator - Visual Design
Marvel - Prototyping

Team

Reginald Lata - UX Designer
Rose Chang
- UX Designer

IMG_5420.jpg

The Design Process

This project was my first introduction to the UX Design Process as well as my first experience working with a client. It was interesting as I had no experience in usability testing or prototyping, but it was an enjoyable process overall. Below outlines all the steps we took to reach our solution.

Affinity Mapping

As a team we listed all the possible problems, opportunities, and important aspects of the typical health clinic experience. We then organized these ideas into groups that all have a common theme. This is how we figured out the features that we wanted to focus on to reach our solution. These features included: scheduling appointments, on-call/chat with doctor, and accessing the pharmacy.

Competitive Analysis

Key Findings

SCHEDULING APPS:

  1. Users can schedule in-person appointments and view available times that are updated in real-time.

  2. Can be used for non-medical scheduling.

  3. Cannot virtually chat with medical professionals.

MEDICAL APPS:

  1. Users can virtually chat with medical professionals and are provided educational resources within the app.

  2. Free to download but not free to virtually chat.

  3. Cannot schedule in-person appointments.

 

User Quotes

In order to learn more about the problems with the Health Center we went across campus and interviewed students between the ages of 18-22 and spanning across different majors. All students have different reasons for having to go visit the Health Center so we wanted to find as many different scenarios as possible.

Key Findings

  • Most people would prefer to meet with a doctor in person rather than virtual chat.

  • Students would like to have a 24/7 on-call type of service from the Health Center.

  • Students would like to be provided some sort of medical history or access to their medical records.

  • Because of the current hours, some students had to skip class to make it to their appointment/walk-in.

  • Users would like to see specific doctors, making a relationship with one doctor would be better than seeing multiple different doctors.

  • Not many students utilize/know of all of the resources the health center provides.

 
 
 

User Personas

From the interviews, we created Cal Poly personas who could benefit from our app. We used the goals and frustrations of our personas to create user-focused decisions that helped us move forward in developing our product, PolyCares+.

 

Feature Prioritization

Next we focused on a feature prioritization exercise where we determined the most important features of PolyCares+. We’ve decided that we want users to expect a scheduling system, documentation of check-ups, and the ability to purchase medication through the application.

IMG_4081.jpg

User Flow

Brendon’s User Flow

After pulling multiple all-nighters, Brendon becomes very ill. After class he runs to the Health Center to find that it’s closed. Feeling ill, he walks back to his dorm and just wants to speak to a doctor at the Health Center.

Katie’s User Flow

Katie begins to feel her injuries begin to worsen after a few more weeks of soccer practice. Her ankle injury seems to not get any better so she books an appointment at the Health Center through the PolyCares app.

Sketches

 
 
 
 
 

 Low-Fidelity Prototype

From sketching to low-fidelity wire-framing, our goal in this phase was to focus on improving usability rather than the visual design. In order to have our user tests not get lost in the design, we decided to keep everything in a grayscale.

 

Guerrilla Testing

Task 1:

You want to schedule an appointment but your only availability is Thursday, May 17th at 10:30am. Find a way to schedule an appointment at this time.

Task 2:

You’ve just had your appointment with the Health Center. Check your most recent summary for this appointment.

Task 3:

You check the app and see that the Health Center is closed for the day but you need to talk to a doctor because you haven’t been feeling well. Chat with a doctor and have an on-call conversation.

Task 4:

You want to know how to better take care of yourself. Your doctor recommended eating more fruits. Search through the app to see where you can learn the benefits of fruits.

 
Guerrilla+Testing.png

Key Findings

  • Thought that hamburger menu was in a weird place but liked the simple and minimalistic design.

  • Thought app was straightforward and would like to see the contact information of the doctor.

  • Participant hates going to the Health Center and making appointments there.

  • Initially confused with the bottom nav and thought that there should be more information about the doctors.

 

Visual Design

Ideation was constant throughout this whole process. From the beginning we both came up with our own designs, moods, typography, etc, and even after combining both designs we had many other iterations after user testing. We took feedback from our users and made the improvements. One significant improvement was the change to our navigation bar. Littles things like indicating what the icons were helped our users navigate through our application.

 

High-Fidelity Prototype

For our high-fidelity prototype, we took all of the data and feedback we received from our user testing and finalized a design and added a color scheme that our users found enjoyable.

 

Usability Testing

We tested out high-fidelity prototype by administering the proper documents stating our testing and our process. We both took turns administering the test while the other recorded any errors, issues, or speculations. Afterwards, we collected qualitative data from the post-test interview and calculated quantitative data from our system usability survey (SUS).

IMG_5431.jpg
 

Task 1

You want to schedule an appointment with the Health Center but your only availability is Thursday, May 17th at 10:30am. Find a way to schedule an appointment at this time for a check up regarding Allergies and fill out the check-in form.

Task 2

You’ve just gotten out of your appointment and want to know how to take better care of yourself. The doctor recommended eating more fruits but you want to know what fruits to eat. Search through the app to see where you can learn about the benefits of fruits.

Task 3

You have a consistent cough and want to order medicine from the pharmacy through the app. Go to the pharmacy menu and shop by Allergy/Cold and pay for the cheapest Allegra medicine with a new card.

Task 4

You just finished your appointment but you forgot what your prescription is. Go chat with a doctor on-call and ask them to look up your prescription for you. Then, go to the pharmacy and purchase your prescription with your Debit card.

 

Key Findings:

  • Users thought hamburger menu was for settings.

  • Thought the app was pretty straightforward and people were more interested in exploring the application.

  • Lack of scrolling made it hard for users to navigate, they really wanted to scroll for some screens.

  • Users like the idea of scheduling this way, rather than calling or walking-in to the health center.

  • Although it wasn’t intended for our original purpose, users loved the pharmacy screens and the ability to order items through the app with a card.

Moving Forward

Something valuable that I learned from this process was that Ideation and testing is super important. Learning to move away from a design and relying on user-testing is valuable to the success in developing a product. If we were to move forward with developing PolyCares+, I’d want to incorporate up-to-date wait times and improve on the navigation. Overall, this was a career changing experience, never would I have thought that I’d be shifting gears towards a User Experience design route. I enjoy creating better experiences for people and I love the collaboration that comes from working in a field like this. I have much more to learn about User Experience and hope to work on more projects in the future.

Previous
Previous

shopDisney

Next
Next

Roopairs