The average American consumer discards 219 pounds of food waste every year. During my pastry chef years, I took interest in the idea of a recipe system that could help minimize food waste.
In this case study, I introduce the development of Zecipe: A zero waste recipe project, based on publicly available research data about food waste and cooking habits.
When I first joined the kitchen, I was taught to hand-write all the recipes I learned, or to learn them by heart.
While it did help me recognize some repetitive patterns in recipes a bit — and it does make a sentimentally beautiful collection — no one can argue that this is a sustainable method. I tried organizing them Alphabetically, categorically, often-to-rarely-made-mically, but nothing seemed to successfully organize this pile of knowledge. There began my obsession with a recipe organization system.
I was looking into simple notecard applications at first, but I couldn’t find a suitable option for a cooking process. I eventually decided to design my own solution by starting from the one question I always ask myself when I’m cooking:
"What's in my fridge?"
Unless I’m in the mood for a slice from Joe’s Pizza, I always start cooking by opening up my fridge. Call it a kitchen habit, or a stern grandma’s lesson - but I always try to use up what I have. Here’s why:
“In the United States, food waste is estimated at between 30-40 percent of the food supply. This estimate, based on estimates from USDA’s Economic Research Service of 31 percent food loss at the retail and consumer levels, corresponded to approximately 133 billion pounds and $161 billion worth of food in 2010. This amount of waste has far-reaching impacts on society”
If I were to commit to this project, I wanted to make sure that I had a goal that could suggest a solution. In other words, I didn’t want to design a product for the sake of designing one. I knew that eliminating the food waste problem would be far beyond my power, but establishing and promoting healthy cooking habits that minimized waste would be tremendously meaningful.
In order to be ‘scrappy’ or to gain the most information from limited resources, I published a custom survey on Typeform while collecting cooking-related statistics from various sources that were publicly available. Here are some key results I scraped:
I also organized user interviews amongst the people who answered "I want to cook more often" in the age of early 20 to mid 50 to create problem statements. Here are some interesting takeaways I found:
Based on these findings, I set my design directions for Zecipe.
It should be sustainable
• I want to know what I can make with what I have first and foremost
It should be comprehensive
• I want a singular tool experience without a complicated process
It should be prospective
• I want a product that can be branched out with further implementation and usage.
I wireframed 3 screens based on different priorities and took them to usability testing.
I reached out to my dear friend Dakota to help me out with engineering. We created a rough data model based on the wireframe C. Based on this draft, it was clear which information would be required for each recipe:
A successful search-based platform needs content — lots and lots of content — preferably with multiple writers or import systems that can supply the content automatically. However, if we create a template with standardized measurement units, we can open the door for the interactive yield amount feature. Plus, with reusable templates, we won’t have to worry about writing custom pages every time new content is published.
To start with standardized measurement units across the platform, I decided to use the recipe pile that I've collected over the past few years. As any manual content process goes, this was the most hands-on part of the project and it took hours. We implemented the functionality for redeploying the app so that whenever new content is published, it triggers a new build, and we can see the changes reflected on the site immediately.
I created a High-fidelity mockup of the MVP for the priority screens: Search functionality, categorized curation that’s connected to the search results, and the actual recipe page. Since these are the core functionalities of the product, I identified everything else as a V2 arrangement.
I created prototypes to communicate interactions and to evaluate design decisions. We were able to get more feedback on the navigational expectation and UI components which will be updated shortly after the build.
If we had more resources and time for this project, we might have considered developing Zecipe as a mobile application. However, it would be wasteful to release this product as a mobile application from the get-go. We want more data, flexibility, and compatibility. After a short discussion, we were convinced to create Zecipe as a web application, since it was the most cost-effective and manageable option available to us.
As much as I would love to say “j'ai terminé!” and throw my dishes away, there are iterations, new features, and further applications that I want to explore for Zecipe.
In the world of smart objects, Zecipe is a comprehensible product for smart home electronics. I would be thrilled to keep track of what I have in my fridge, on my fridge. The idea is to not stop at:
‘What’s in my fridge?’
...but to provide solutions to follow-up questions such as:
"Ok, What can I make with these?"
"What’s about to go bad?"
"What’s something I haven’t made in a while?"
Special thanks to Dakota, Fullstack Engineer
Surveys and statistics from USDA, Typeface, ReportLinker, and HunterPR