MEDIGO APP
The Future of Optimizing
Patient Care
ROLE
CEO, Product Design/
Development Lead, UX Designer
TOOLS
Figma
Adobe Illustrator
PROJECT OVERVIEW
MediGO is a med-tech startup concept that was built over the course of a semester at USC. I led a team of 7 other students to create a fully-fledged project that included both materials and mobile app design, business development strategies, and product pitches to stakeholders.
As the CEO, I was tasked with overseeing all aspects of the project - from managing the product timeline to delegating tasks to project members. Additionally, as the Design Lead, I personally was responsible for managing the product design, development of the mobile app, and the onboarding website design. This case study will cover the design process for the mediGO app.
BACKGROUND/CONTEXT
current healthcare systems lack the infrastructure for personalized patient management
Originally inspired by the plight of elderly who live alone, we sought to come up with a solution that could bridge the gap between daily healthcare management and emergency care services.
A few questions we considered:
PROBLEM
difficulty in consistent, efficient, and critical health management
We found a gap in the modern emergency healthcare's system ability to recognize, diagnose, and treat those with unique medical conditions at maximal efficiency. This also applies to those who suffer from a multitude of conditions that might be put at risk without proper and precise care. Thus, our goal for our solution was to minimize the amount of time between onboarding and medical treatment.
SOLUTION
Supplementing the existing system with a universally accessible tool
With physical monitoring bracelets that not only 1) provide real time health insights and 2) are scannable for patient medical records, we had a vision to completely rewrite the health gadget scene.
The GOband is a health and activity tracker that provides first responders critical medical information in case of emergency. Combined with the mediGO app, track your loved ones and receive real-time notifications and alerts. Our vision for this band was for it to be a multifunctional yet lightweight wearable that could compete with products like the Fitbit and the Apple Watch by being monitorable by users other than the wearer.
I. INDUSTRY CONTEXT
Who would benefit from a monitoring band?
The usage of smart watches among other devices as health monitoring devices have surged in the past decade. Smartwatches are able to detect a variety of different health metrics, including but not limited to: heart rate, oxygen saturation, fitness levels, and sleep quality. Studies and surveys have shown that up to 90% of adults have expressed a willingness to share data from their devices directly with their physicians.
Here are a few statistics we gathered about the digital healthcare space:
What can mediGO offer that is different?
Our focus, therefore, is not to create a solution that would radicalize the healthcare space but rather to systemize it; making it more accessible, reliable, and convenient for both individuals living with chronic conditions and their caregivers. We envisioned that mediGO would be a product that fills a niche space in the healthcare tech scene by acting as a safety net provide assurance to our users.
Currently, there is no product in the smart band market that fills in the niche for medical technology like mediGO. Products in the smart band space are highly developed in health and fitness metrics, while those in the medical space are more specific to serving a "high-risk" population. mediGO aims to combine the best features between the two to serve a new market of people who simply want to be worry-free, independent, and healthy.
II. CONCEPT DEVELOPMENT
Setting the foundations
For the first few weeks of the course, we were expected to collaborate and finalize what features we would want our application to have. In order to accomplish this, we had to not only complete logistical efforts to understand our market, but also make empathetic efforts by reaching out and gaining insights.
Two core values that we decided to place at the forefront of our brand were:
Understanding what our users want
To find out which features people would like, we first began interviewing potentials users of our app: individuals with chronic health conditions, caretakers, and healthcare professionals. We asked whether they had been using a healthcare monitoring device, and what type of features were indispensable for them. True to our research, most patients were equipped with some type of band - health tracking for our younger interviewees and scannable bands for our elderly ones (information for elderly provided by caretakers). A few key points we gathered:
While we originally had plans to use the app for personal monitoring, we decided to reroute into an application that makes it easy to share information. With this information, we finalized the key points of the mediGO app and its correlating functions on the band.
III. PRODUCT IDEATION
Finalizing product features
First, we finalized the relationship between the different facts of the mediGO ecosystem, confirming the role of each and their relationship to one another. Next, we compiled a list of features commonly seen in both smartwatches, medical tracking bands, and health/wellness applications. From this list, we narrowed it down to a few we thought were the most important/most feasible to implement.
Understanding our users through storytelling
To precisely communicate my product vision with my team and our stakeholders, I drew up a few storyboards with scenarios that express how mediGO is supposed to be used.
Marissa is worried about her mother, who has dementia and prone to falling. She is able to go about her day rest assured, knowing that she can track her mother's condition and location throughout the day.
Daisy is a 6 year old with type 1 diabetes who wishes to be independent with her school life. With her band, her parents are able to have assurance that they will be notified right away in case of any incident.
Elaine is a seizure prone 22 year old living alone in New York City. With the band, she can ensure that anyone who finds her will know what to do once they scan it.
Barry is a 62 year old man with a rare chronic medical condition. With his band, he can instantly share critical medical information with first responders in case of emergency.
Creating a User Flow
After determining what functions we wanted the app to have, and how our different products would interact with each other, we began our app development process by mapping out a user flow that would help us imagine how each user (patient, caretaker, first responder) would interact with our application. During this step, we were careful to minimize the number of steps it took to complete a task.
Envisioning the interface
Using Figma, I began creating low-fidelity wireframes that captured just a portion of our original vision. During this process, I continuously conducted market research on how popular applications in the same space (health, tech) organize their information. My goal at this step was to keep the app consistent with what our users would be used to. Cohesive to the feedback we received from our interviewees, I decided to split the app into five main categories: the home page, health insights page, activity log, profile, and at the very center: location.
IV. VISUAL DESIGN PROCESS
Shaping our visual narrative
While mediGO's vision is to provide our users with their information in a logical and concise type of manner, our goal for the app was to create an intuitive, reliable, and inviting space for our users. We used both solid and gradient cool-toned colors such as blue and purple to establish a comfortable and calm environment and tone.
V. CRITIQUES, ADJUSTMENTS, AND HI-FIDELITY PROTOTYPING
Design Critiques
During the first round of reviews for our product, we were able to pitch our product and concept to the class and professor and receive our first round of critiques for our low fidelity prototype. During this time, we also sent the link for a few of our "users" from our initial round of interviews to review. A summary of the notes we received from each group are:
From the Professor:
"Simplify and Highlight"
Our professor recommended that we remove a few of our features so that the most important ones could be prioritized. He also encouraged us to look into data on which health metrics would be most beneficial for our users, and to organize it in a hierarchical manner.
From our Classmates:
"Update and Modernize Interface"
Our classmates had the most feedback on the interface (icons and buttons), saying that it could be updated to fit modern standards. A few also mentioned how the icons did not fit the tone we were trying to express - it was too "casual," whereas our product was "sophisticated"
From our Users:
"It's too complicated"
Our users found the activity log most useful. Most expressed uncertainty about using emergency related location services, as they are not likely to rely on the app in case of emergency. They also mentioned that they would like all the important features to have high visibility so they wouldn't have to look for it.
Secondary Adjustments
Using the critique we had received and additional brainstorming within the team, we adjusted our approach by reducing the number of features in app and instead highlighting features that were more likely to be used. A question we often had to revisit is "what makes our app unique," and "would this be what the users want." We had to constantly keep ourselves in check to ensure our vision was on par with reality.
Thus, the solutions we implemented following the class critique and final rounds of brainstorming include:
VI. FINAL PRODUCT
From concept to reality
FINAL REMARKS
Takeaways
One of my greatest takeaways from this project is the importance of strong team chemistry and trust. While I joined this class with the goal of implementing and practicing my knowledge in design, I was unable to focus on that aspect because I was being spread out with other responsibilities. As the CEO, I learned that each individual in a professional space is equipped with their own strengths, and it is the responsibility of those in leadership to guide them along that path in order to create the best possible product. I think the one thing I struggled with the most was pushing my team to attempt things outside their area of expertise (and not just doing it myself). However, at the end of the day, I had to delegate the things I couldn't do and trust in their abilities, while providing support when needed.
.png)
