.png){kind=small}
By Raissa Talehata
Define & Ideate
DEFINE
We over-purchase and stockpile food
From the survey analysis, I came to an understanding that the issue of food waste is tied to a complex set of actions: planning, shopping, storing, preparing, and consuming.
So, I reached out to 3 people from the survey respondents as well as observing some bloggers on YouTube about their shopping routines to empathize with users. This process could help me determining
the point of intervention in designing solutions for behavioural change.
​
With the help of Fishbone Diagram, I was able to break down the potential causes of stockpiling behaviors. Then, implementing Jobs-to-be-Done Framework I was able to empathize with users by deconstructing their situations, motivations, and outcomes.
Fishbone Diagram
Jobs-to-be-Done Framework
= Situation
= Motivation
= Outcome
Synthesizing User Problems
ISSUE 1
We buy and store food more than being consumed
When I’m at the grocery store, I’d like to know what I have at home, so I shop mindfully and don’t end up buying food more than I need.
ISSUE 2
We lose track of our produce and how long it’s been there, especially what’s inside our fridge
After doing a grocery shopping, I want to be able to keep track of what I buy and know how long they could last, so I can make sure that I finish my produce before it goes bad.
IDEATE
Designing for Behavior Change
The goal of this project is to promote new behavior that will allow end consumers like you and I to be more aware with our shopping, consuming, and discarding habit. Amy Bucher in her book called Engaged explained that: for a product to effectively influence behavior, it’s important to understand where and how designer could intervene users to interact with the product and then ask them to do something differently.
With that concept in mind, I decided on setting a goal that focus on preventing people from shopping impulsively and set a point of intervention during and after shopping. So, I created this storyboard to map the ideal journey as how I imagined Froot to pan out and what the desired user experience might entail.
Storyboard
Scenario
​
Cassidy has a deep passion for cooking and she’s a creative cook herself, but she has a very busy schedule that prevent her to properly plan her grocery shopping. She usually cook meals for 3 - 4 days a week and at least go to grocery story store twice a week which usually happened right after work.
​
Tonight, she’s thinking of making her favorite meal
because it’s simple and always taste good: a meat sauce linguine with onion, mushroom, and bell pepper. She knows that she’ll also have 2 more leftover meals from it. So, she goes to the grocery store to make a quick round to get some mushroom and ground beef for her dinner tonight. While she’s at the store, she also get few other stuff such as bacon, salad, and bread to prepare for her lunch and breakfast.
IDEATE
Product MVP
The storyboard really helps me to figure out actions and features that will be beneficial for the user. So, I decided to sketch ideas for the 3 main features:
Kitchen Page
This is going to be the home page that user will see, which will visualize the fresh produce they have at home.
Product Page
The item page will show detailed view of each produce where user will be able to see the quantity, where it is stored, and how long it’s been there. Apart from that, this page is also the section where user can learn more about storage, preserving, and assessing the produce.
Shop Produce
This page is proposed to use an object identification technology for users to add produce to their kitchen in real time. Just like a plant identification app, Froot will also implement this technology to by allowing user to take picture of the produce and the app will identify it and send back information about their shelf life.
Initial Sketch
For the initial sketch, I created 2 models to show different ideas in visualizing the concept. After consulting with my advisor (Tania Schlatter), she shared few important feedback before I moved forward with the low fidelity wireframe.
Kitchen & Item Page
Shop Produce
Design Feedback
01
“What if the language is not "expiring", but usage focused? Can you shift from creating awareness of expiry, to promoting awareness of prioritizing use? Items that are older could have "high priority" use status, with prompts to use/extend.”
02
“I like the "assess me" idea, or what to look for. We don't want the app to be liable if someone gets sick, so you should not want to tell people what to do, but do want to provide general tips about use for the item.”
03
“I think this needs more thought, because it is busy, more like a dashboard, and I think will be too much info at once for in-store use.”