
client
Methods
- User interviews
- Field studies
- Competitive analysis
- Personas
- Journey mapping
- Lo- and hi-fidelity wireframing
- Prototyping
- Moderated usability testing
- A/B testing
tools
- Figma
- Visily
- Miro
- Notably.ai
Year
Clean Plate Club
Problem
People, particularly those in the United States, have a tendency to throw away food. In fact, the average American consumer wastes about 1/3 of the groceries that they buy (between 30-40%) every year. As we all know, this is expensive; there are different estimates for the cost of food waste per person, but the approximate value of the food waste in the country as a whole is $218 billion, or 130 billion meals.
Solution
Clean Plate Club is an application that aims to reduce household food waste and save people money by letting them know what they have in their inventory and when it will expire. By having real-time data on food freshness and reminders on when to consume something, users will be more conscientious of their inventory and organized when planning their meals.
Leave no crumb behind.

i. Investigate the current state
interviews
In order to identify why people are wasting food, I had to understand how they are managing it. I intereviewed 6 people using a script with with 12 open-ended questions, focusing on values, motivations, and routines. I conducted the interviews on Notably.ai to more efficiently gather key insights and themes.
To more accurately identify which common theme (i.e., level of organization, visibility of food) affected food waste, I ideally would have set up the interview to operationalize my findings and do a regression analysis, but there was not a large enough sample size.

Affinity Mapping
I synthesized my interview results using affinity mapping, organizing interview pieces into key themes based on my own analysis and the results of Notably.ai. I used these interview findings particularly in persona building and feature prioritization.

competitive analysis
I then looked into some of the tools that interviewees mentioned they used to meal plan, grocery shop, or otherwise keep track of their food inventory. I analyzed the tools' predominant user bases, desktop and mobile experiences, interactions, navigation, visual design, and copy.
.png)
Field Studies
I needed a sharper, more sensitive understanding of user behavior, so I conducted field studies observing how people bought and used their food. I went food shopping with some friends to learn why they choose their food (i.e., intent) and observed when and how they sorted through their refrigerators and pantries to understand how they actually used that food after purchase (i.e., action). This perspective helped me bridge the real world of your refrigerator to the digital world of Clean Plate Club.

ii. Define and distill needs
prioritized user base
With a keener understanding of how people forecast, organize, and use their food, I honed in on a target audience who would most benefit from a food management solution.
.png)
I then built a persona based on this audience and used it to guide the development of the customer journey and uncover key features of the solution.
.png)
customer journey
At this point, I knew I was creating a solution that allowed people to track the food in stock, but the solution had to go beyond manual tracking and organization - people can already do this on other apps, so what is going wrong with this method? To uncover the heart of the problem, I built a journey map outlining Robin's actions and feelings throughout a week of buying, consuming, and discarding food. I was able to identify where the pain points that caused the most friction were in this process so I could design a relevant, timely solution to the user's problems.

prioritized solutions
I distilled the needs identified from the persona and journey list five core needs that address user problems while still aligning with user values. This enabled me to hone in on features that most effectively alleviated problems that lead users to wasting food.

