Rooted

Fostering community connection to waste less food together.

3 mockup screens of 'Rooted', the food sharing product
In America, food waste occurs at every stage of the production process, with 43% taking place in the home.  I have found myself tossing out food I had every intention of enjoying more times than I care to admit. My frustration of contributing to the massive issue of food waste sparked a desire to address the issue head-on and explore whether others shared similar experiences. Seeking a solution within the realm of circular economy and community sharing, my goal was to find a way to mitigate the problem of food waste in the home.
Project Overview

PROBLEM

While people intend to eat the food that they make at home, the reality is that busy lifestyles and the monotony of repetitive leftovers often lead to tossing it out and getting food elsewhere despite their good intentions. The idea of sharing food with neighbors is dismissed due to lack of personal connection needed to initiate such a familiar interaction.

SOLUTION

A food-sharing app that fosters a sense of comfort and trust, empowering individuals to initiate sharing food within their communities with ease and confidence.

Research Methodologies
Survey, Diary Study, User Interviews, Competitive Analysis, Usability Testing
Project Goal
Understand pain points related to food waste in the home and design a solution to help minimize food waste.
My role
Self-directed UX/UI Designer (Researcher, UX Design, Visual Design)
Biggest Lesson
Be sure design decisions are aligned with core needs under the stress of tight timelines.
Tools
Figma/Figjam, Adobe Fresco                   
Constraints
80-hour project timeline
Delivered
High-fidelity mobile prototype
Despite efforts, food waste is still happening
SURVEY
I surveyed 20 people to find individuals who struggle with food waste and who viewed it as a problem. A few key findings were worth noting.
insight 1
Despite people having solutions in place to waste less food, they still find themselves tossing food.  
insight 2
Participants claim to be interested in the idea of food sharing as a solution.
insight 3
Most people buy food at the grocery store 1-2 times a week.
While it was easy to get excited at the fact that people claimed to be interested in the idea of food waste, I know all too well as a researcher that there is a possibility that people don't mean what they say!  I was curious to learn more about this as well as how grocery shopping habits correlate to food waste.

If people are open to the idea of food sharing as a solution, is there a barrier preventing people from acting on it?

Understanding behaviors over time
DIARY STUDY

To further understand the relationship between grocery shopping habits, and food waste in the home, I conducted a diary study to gather data on behaviors over time.

observation 1
Members of households made decisions influenced meal decisions, leading to food waste

Participants were influenced by other members of the household's desires to order takeout, diverting from the initial plan to eat at home, leading to tossing out food.

observation 2
People were tired of what they had, so they made impulse decisions that led to food waste

2 out of 4 participants tossed food because they were tired of eating it after multiple days.

observation 3
Food sharing led to wasted food (!)

1 participant accepted food shared with them by a family member, which they did not eat and ultimately tossed. This was a red flag to pay attention to...

Frustrations of food waste and barriers to sharing
USER INTERVIEWS

Using the data uncovered in the diary study to direct my interview guide, I interviewed 5 of the diary study participants.

insight 1
The struggle of meal monotony

Despite intending to save money by eating at home, when faced with leftovers from they night before, they don't want it.

insight 2
Busy schedules divert plans

Busy schedules often thwart intentions as groceries bought with the plan to prepare meals at home go unused when individuals are away.

insight 3
Lack of familiarity prevents sharing

People like sharing food with people they know and trust, but hesitate to initiate this kind of interaction with people they don't know.

“I feel like I've never had an opportunity to connect with my neighbors in a way to feel familiar enough to share food..."
-Interviewee

“If I have a busy week at work and can't find the time to cook, then I can’t keep on top of my refrigerator and that’s when I end up throwing out food.
- Interviewee

Addressing the reasons we toss and the barrier to sharing

USER GOALS | "HOW MIGHT WE...?"

In the moments when people are experiencing the pain points of busy lifestyles or meal monotony, the idea of sharing food with neighbors has crossed the minds of the participants, but they don't act on it. People don't feel that they know others well enough in their community to initiate an offer to share food with them.

How might we facilitate trusting connections within communities so that people can help each other waste less food?

→ How might we support people who intend to have meals at home but have busy schedules that keep them away, leading to throwing out food?

How might we help people who want to eat at home avoid meal monotony so that they can have more meal variety?

Meet Annie & Zack

PERSONAS

Narrowing down the goals, needs, pain points, behaviors, & motivations from the data led me to identifying two personas outlining 2 underlying frustrations with the overarching hurdle of hesitancy to share food with others.

Goal

To save money while by eating at home, while still having access to meal variety.  

Overarching problem

In her attempts to eat at home to save money, she inevitably gets tired of eating the same thing for multiple days and throws it out.

Goal

To avoid eating out and eating relatively healthy even when his schedule becomes unexpectedly busy.

Overarching problem

Busy schedules prevent him from making food at home that he intended to eat, leading to anxiety knowing the food is going bad, and then tossing it out.

Brainstorming for the most impactful solution

IDEATION

Coming out of research, it was apparent that a potential solution might revolve around food sharing. Despite people expressing interest in the possibility, participating in sharing was shut down by a lack of familiarity with their community members and no system in place to pave the interaction.

I found myself wishing I had probed more into why people didn't use OLIO, as this is a system in place to pave this interaction that people were not using. I suspected it could be due to unawareness of the product's existence or perhaps a lack of OLIO users near the user.

Time constraints compelled me to move forward with the project, brainstorming broadly for solutions within and beyond the realm of food sharing. My goal was to identify impactful solutions that addressed our users' pain points.


idea 1 (chosen one)
Community centered food sharing

Food sharing, like OLIO product concept, with a greater emphasis on familiarizing and building trust with members of one's community.

Pros
  • Addresses the overarching HMW as well as the sub HMW statements.
  • Ability to incorporate social feature and design patterns that are familiar to people  
  • Room for product scalability and feature add-ons that could potentially solve some of the cons listed
Cons
  • Not 100% guaranteed that this would create enough familiarity for people to risk engaging with others through the app
idea 2
Community composter

A product that allows users to connect through composting, bringing by composting materials to community members' compost spots.

Pros
  • Addresses the overarching HMW statement, providing an avenue for people to connect and take part in a process that some people might not have the time or infrastructure for
  • Room for product scalability and feature add-ons that could potentially solve some of the cons listed
Cons
  • This addresses the overarching HMW statement. but does not address the sub HMW statements.

I kept an open mind to exploring other ideas beyond food sharing, but the process felt a bit forced as my research hypothesis was related to food sharing, and the idea of food sharing did in fact meet the user needs. The solution of a community centered food sharing addressed the overarching HMW as well as the 2 underlying HMW statements.

Now, I wanted to take a closer look at companies that are in the sharing/selling space to see what I could learn before entering the design phase.


Features

FEATURE ROADMAP

Listing out the features to be included in the MVP, I tied each feature back to the HMW statements, ensuring all design decisions aligned with user needs.

(View full feature roadmap here)

Mapping out the app

INFORMATION ARCHITECTURE

What started off as a navigation map turned into more of a combination between a nav map and app structure map. This hybrid deliverable helped me not only lay out what screens should belong where, but also helped me to think about how to navigate between the screens and content.

App structure map of Rooted

App structure map (click to enlarge image)

Laying out the key flows

TASK FLOWS

Next, I needed to map out key flows that the user would need to go through to achieve their goals. Going through these flows helped me be sure I was not missing any key screens that I needed to include in the wireframes.

Sketching out initial ideas

LOW-FIDELITY WIREFRAMES

Now was time to begin sketching out key screens for the design. Laying out the sketches to create a wireflow was helpful in bringing myself through the flow from the user's perspective.

Screenshot of mid-fidelity screens of the Rooted app (1)

Low-fidelity wireframes (click to enlarge image)

Testing early & prioritizing revisions

MID-FIDELITY TESTING | PRIORITY REVISIONS

Screenshot of mid-fidelity screens of the Rooted app (1)

Mid-fidelity wireframes (click to enlarge image)

Screenshot of mid-fidelity screens of the Rooted app (2)

Mid-fidelity wireframes (click to enlarge image)

Due to time constraints, I wanted to test early on to receive feedback and discover any issues related to accessibility, app structure & UI, as well as determine whether there are any gaps in the flows or the features selected to include in the MVP.

I tested out the following flows with 3 participants:

Usability testing brought to light some areas for improvement. There was confusion about where to find 'upcoming pickups,' with different ideas ranging across various sections of the app. This confusion was caused partly by a confusing activity tab icon and the use of tabs on both the activity & messaging pages. Some participants felt uneasy about sharing exact addresses, preferring meet-up locations and desiring notifications when their address is shared. Another key takeaway is the emphasis on messaging, where participants highlighted the importance of a human connection, suggesting that making messaging a required step could enhance the community-focused experience.


*NOTE: While implementing the high-priority revisions, I let the tight timeline get the best of me, and removed the social stories from the home page, listening to the feedback I received from a participant that it made the home screen feel too busy. In the moment, I wanted to test out the flow without the stories housed on the home page to see if I received better feedback, but it ended up not being a great decision in the end because it took out a core feature from the testing that is critical in differentiating this product from competitors. This was a huge learning moment for me!

I sorted the testing findings into an Impact vs. Effort matrix to prioritize whether the iteration was necessary for the MVP. Based on these results, I revised these high-priority issues:

What went well
What needs work

Branding

BRANDING

It was now time to give an identity to Rooted.  Based on my research, the brand values include grassroots, trustworthy, sustainable, and community-focused. For the logo, I played around with some welcoming illustration ideas to give it a grass roots and friendly vibe. I chose a serif font for the logo that feels welcoming that is also used for large headings throughout the app. I paired this with a clean, sans serif for body text so that it is very easily readable.

Screenshot of high-fidelity screens of new DIYD website design.s, colors, typeface, buttons, and additional components used throughout the product

Testing & iterating once again

HIGH-FIDELITY TESTING | PRIORITY REVISIONS

I facilitated 3 moderated usability tests to test out the revisions made based on the mid-fi usability testing, as well as receive feedback on the visual design and determine if there were any remaining issues related to accessibility.

I tested out the following flows with 3 participants:

What went well

The participants commented on the branding feeling welcoming and friendly, particularly the illustrations. They felt the flows were intuitive and how it felt like other apps they are used to using on a regular basis. This time around, participants arrived on the 'Shares' tab (formerly named 'Activity') and found the content housed in this area of the app in line with their expectations.

What needs work

The phrase "Being picked up" caused confusion, as some participants associated it with ride-share language. In the "List an item" flow, participants found the instructions for 'serving' (unit, servings per unit, total servings) required extra processing, indicating a need for clearer copy on this page. A concern for privacy arose, with a participant questioning how accurate the circle radius would be displaying the Sharer's location on the food listing page.

Despite the fact that the stories feature was not included in mid-fidelity testing, I decided to add the feature back into the design as it is critical to distinguishing this products from the competition. A flow of users interacting withthis feature as well as the other revised aspects would need to be tested.

Based on these results, I identified 1 high-priority revision that needed addressing for the success of the MVP and 4   iterations to consider for the future:

  • High priority: Add stories feature for future testing
  • High priority: Explore alternative copy to replace "Being picked up"
  • For future discussion: Consider privacy  
  • For future discussion: Build out 'favorites' for pick-up location so users can easily pick pre-saved locations for pick-up
  • For future discussion: Explore ways of incorporating the problem of food storage. Could this be a feature integrated into the product or even a business partnership?

Incorporating revisions & visual design

HIGH-FIDELITY SCREENS

Adding in the branding and visual elements, I implemented the revisions prioritized from mid-fi testing and designed the high-fidelity screens.

The MVP

FINAL DESIGN
                                                                                                                                                                                                                                                         

With the usability test complete, I implemented the high-priority changes into the prototype.

Laptop mockup displaying the landing page of the new DIYD site
Click to open the interactive prototype

What I learned

Stay strategic when reviewing feedback

The design and testing phase of this project fell under a tight deadline, so I made impulse decisions based on feedback after mid-fi testing that veered away from the core user needs. This project really highlighted the importance of checking that all design decisions are tied back to user goals, even when a user provides feedback that presents itself as a quick fix!‍

check out my other projects