SafeEats: Elimination diet made easy
A smart food and symptoms logging tool that helps you better avoid allergens and intolerances
Aug 2020 - Dec 2020
Easy access to accurate nutritional information is growing need for many Americans. According to a 2014 study, over 60% of US households contained at least one member monitoring or limiting consumption of at least one macronutrient or ingredient. Our team aimed to understand the problem space and design a product for users with dietary restrictions.
Our design process and decision makings are firmly rooted in user research. Surveys and interviews are used to direct our problem definition and generate design requirements. User feedback sessions are conducted in every iterative design cycle.
I was involved in every stage of the project. During research, I designed the survey in Qualtrics and analyzed and visualized results in Excel. I also conducted two semi-structured interviews. At the prototyping stage, I led the design of the prototype and transformed our early wireframes into a prototype in Figma. I was also involved in prototype feedback sessions and devised solutions to address problems revealed.
Note: some content and layout of this page are not finalized.
Easy and efficient access to accurate nutritional information is growing need for many Americans. According to a 2014 study (“Households with Dietary Restrictions, 2014), over 60% of US households contained at least one member monitoring or limiting consumption of at least one macronutrient or ingredient. Our team aimed to understand the problem space and design a product for users with dietary restrictions.
Our user-centered design process
/ User Research
// Research Problem Directions
After background research, our team came up with 4 general themes of questions for users with dietary restrictions:
Current process for determining food safety
Usage of existing systems
Need for educational content on dietary restriction practices
Demand and risk tolerance level for new food
// Research Methods
We conducted eight video interview sessions with target users. Our participants have ages between 22 and 50. Their dietary restriction types include allergies, intolerances, vegetarian/vegan, and religious.
See our full semi-structured question script here.
Fun time: user interviews!
Qualtrics survey blocking logic
Joining an online support group
We reached out to a wider user population through online surveys. Our primary goal was to answer two questions: "what problems/contexts do our users find challenging to meet their restrictions” and "how do those challenges differ among users with different restriction types". These questions would help us narrow down our user group and problem space, giving us a specific design direction. We designed the survey in Qualtrics and distributed the survey via social media platforms. We also reached out to online support communities for dietary restrictions for more targeted users.
See the full survey here.
We conducted with one in-person contextual inquiry. We were primarily interested in the process by which someone with complex dietary restrictions shops in a grocery store. We payed close attention to how they utilize food labels when determining what to purchase. The data collected from this inquiry would facilitate the creation of a task analysis for the process of using food labels and packaging to determine what was safe to eat.
// Result Analysis
We held interpretation sessions after each interview. Interpretation notes were pooled into a spreadsheet together with questions and design ideas. Those sessions resulted in over 200 notes. We imported them into a Miro board and created an Affinity Map. The process helped use condense the data into seven major categories of user needs.
Creating an affinity map in Miro
Various chart types used
Survey data analysis and visualization
We first cleaned the survey data by removing any abnormal responses with extra short response times. Results were recoded and conditionally formatted in Excel. Visual inspection and basic statistical measures such as mode, quartiles were adopted. We made various charts to compare inter-group (different restriction types) differences in responses.
Conditional formatting for visual inspection
Task analysis for elimination diet
We used task analyses to break down common tasks our users must go through. This method helps us discover potential subtasks that are not addressed by existing tools.
On the left is a task analysis for Elimination Diet, a diet where users test their body’s reactions to certain ingredients by adding them to their safe diet one-by-one. This is a common process many users with food allergies go through voluntarily or under doctors' suggestions.
// Research Findings
From the result analysis, we summarized the following eight user pain points:
Determining whether food fits within one’s dietary restriction is stressful. This is especially true for people with food allergies and intolerances. It can take years for them to feel comfortable selecting food.
Food Packaging and labeling can be confusing and lacks information. Jargon is a commonly mentioned source of confusion. The actual amount of ingredient is a commonly missing piece of information.
Some users learned about some of their allergens using self-devised testing strategies similar to an Elimination Diet.
Restaurants pose a difficult barrier for people to navigate their dietary restrictions.
Taste and price sometimes out-weight dietary restrictions for users without life threatening restrictions during decision making process.
Desires and anxieties about exploring new foods.
Youtube is a popular source of information for vegan users. Some allergy users would get manufacturer information via customer hotlines or websites.
/ Identifying Needs
// Problem Statement
After reviewing our team capabilities and environmental limitations, we proceeded with the specific problem space:
"Help users with allergies and intolerances improve food product selection process by helping them better understand their conditions and offering product information relevant to their restrictions."
// User Needs and Design Implications
They need a system that allows them to easily track and manage their restrictions.
They need to feel comfortable with trying new foods and recipes.
They need food labels that are easier to understand and have more information on the ingredient proportions, taste, quality, and explanation of ingredient jargons.
They need useful and accurate information about their dietary restrictions that includes byproducts and products that are safe to eat.
They need to track their food intake and test for any adverse reactions to determine any allergies or intolerances.
Design Implications (Our product should...)
Build trust with the user by providing accurate and helpful information. Informs the user on whether a new product or food may cause an adverse physiological reaction
Help the user discover new recipes and food products that won’t cause adverse reactions. Suggest safe alternatives when needed.
Include product pages that:
Extract information relevant to the user's restriction profile.
Smartly suggest ingredient proportion based on product type.
Show crowdsourced user reviews on the taste or quality of the item.
Show users additional information not found in a common food packaging, for example, changes in a manufacturer's cross-contamination practices
Provide users with specific pages dedicated to useful and accurate information about their dietary restrictions that include:
Risk level for common ingredients and potential symptoms
Compound ingredients that may contain potential allergens
List of related information sources
Allow users to track their food and symptoms to products they may have tried. This can include adding specific products they found through the app and tracking how the food made them feel.
// User Persona
// Usage Case Storyboard
/ Brainstorming and Design
We did a group brainstorming session via a "wall walk", during which each team member generated and posted idea notes onto related section of the affinity map. We then discuss ideas one by one, building connections and condensing them into "systems of features". We finally came up with four major systems for our mobile app:
A user dietary restriction profile that accommodates users who are unclear about their full restriction list. The profile should also incorporate the idea of consumption threshold
A mobile implementation of the Elimination Diet process that features food and symptoms tracking. The result will update user's dietary restriction profile accordingly
An ingredient detector that reports product risks based on user profile
A product search filter that helps users to select food suitable for their user profile
Design ideas connected to form systems of features
How four systems of features interact to enhance the service