Trellis Health
Consumer Product
Strategized and built the symptoms feature for pregnant women which resulted in 85% of user satisfaction rate
DURATION
10 weeks
ROLE
Product Designer
TOOLS
Figma, FigJam, Notion
Impact
85%
Satisfaction Rate
(Ease of use)
90%
of the users found logging symptoms less time consuming
Background
Women go through a lot of changes during pregnancy. From normal headaches to fluctuation in moods to severe health conditions. Women have been predominantly using a symptoms tracker for their menstruation cycles and pregnancies. But when it comes to tracking symptoms for pregnancy, there is a need to create a reliable way of not only logging them but also reviewing the data collected for tracking one’s health. This might avoid any unforeseen issues during and after the pregnancy.
Design Process
We followed the following design process and it was iterative in nature:
User Research
DOMAIN OF INQUIRY
For pregnant women, symptoms range at different levels. There are common symptoms and then some that occur at certain times. Some symptoms might be associated with each other while some others might occur together due to some reasons. We targeted symptoms that are common, associated and that need monitoring (might be severe) and might lead to serious health conditions leading to complications in pregnancy.
COMPETITOR ANALYSIS
Competitor analysis was performed to learn about the symptoms feature available in the market for menstruation cycle tracking as well as pregnancy tracking Apps.
We targeted popular Apps and studied the symptoms for each one of them and made a note of the factors that helped them stand out or factors that worked well for the people to use the App for longer duration.
COMMON OBSERVATIONS ABOUT SYMPTOMS
-
Most Apps have quick log and save actions for symptoms.
-
Analysis of the symptoms was rarely found.
-
Reminders are common when logging symptoms.
USER JOURNEY MAP
Key Findings
-
People are less or not motivated to track symptoms.
-
Some symptoms may lead to others.
-
Tracking symptoms on a daily basis would help understand health more clearly.
-
Many apps use simple icons or one touch interactions to save the symptoms.
Conceptual Design
REQUIREMENT GATHERING
User stories were created to define the scope of the functionality of the feature.
Following requirements were finalized after multiple discussions and brainstorming sessions:
-
User should be able to quickly log symptoms
-
Users should be able to log a symptom and add details.
-
Users should be able to look at the logged symptoms for this week.
USER SCENARIO
Interaction Design
MOOD BOARD
Inspired with the ideas I started creating sketches, finalized the lo-fi sketches with the team and then started working on hi-fi design screens in figma.
A/B TESTING
Chips view vs list view for logging symptoms: After iterating on the above design, I tried creating simple views that would accommodate overlapping of symptoms and ruled out the cons of the above design.
A chips view looks trendy and desirable to click on and changes its color to ensure it was selected by the user.
A simple list view like the Apple Contacts helps the user find the symptoms easily as the list is the simplest to read and browse
PROTOYPING
Logging symptoms with list view design
Add Details for logged symptoms and explore all logged symptoms
Evaluation
With the given two designs created, I planned a usability test. The purpose of the usability test was to find out how women would use the symptoms feature and to test between the chips view vs list view.
I recruited participants who were pregnant or planning to get pregnant. We interviewed all 4 participants in 2 days. It was a 30 minute test session with 3 tasks online over Zoom meetings.
MAJOR FINDINGS
3/4
participants found the quick save approach easy to use and helpful
List View
was the winning design in A/B testing
Key Learnings
-
In the overall project work, I learnt how an App is sent to the App store and tested. The entire process and patience required while things are fixed and tested again.
-
I explored the scope and need for responsive design in iOS devices (iPad designs were also created for the app - not shown in this case study).