Studies have found that Millennials are considered as the worst cooks in history and are cooking less than ever before. Through this 8 weeks course project at BrainStation, I wanted to explore this problem and design a solution by discovering what matters to this generation. What can I learn from Millennials' relationship with cooking and their experiences in using cooking apps? How can I create something that is more engaging and well fitted for them?
According to studies, Millennials are the worst cooks because of multiple reasons:
With these problems in mind, I asked myself how I may help Millennials solve their cooking problem by starting with the question "What they can cook with the current ingredients they have in their kitchen?"
To gain user insights and validate these hypotheses, I conducted interviews with five people between the age of 22 to 30 years old. I interviewed them about their relationship with cooking, their past experiences and interactions with recipes. The goal was to collect user patterns in regards to their pain points, motivations, and behaviours surrounding this topic.
Majority of the users said that they only have an average of 30 mins to cook during weekdays because of laziness and their busy work schedules. Also, they do not feel confident when they are cooking new dishes because they dislike being out of their comfort zone.
They value and prioritize low costs, convenience, and simpleness. However, they are extremely willing to learn how to cook better because cooking is an overall positive experience for them and also a way for them to be creative and calmness.
Interviewees have a short attention span to lengthy recipes but they gravitate towards videos. To save time, interviewees prefer to cook simple meals that only require basic ingredients. Affordability is critical as well so they dislike going out of their way to get specific ingredients to fulfill recipes, which leads them to live an ingredient-first lifestyle. In terms of meal preparation, they do not like to prepare their meals in advance. Their habit is to check what existing ingredients they have first to decide what to cook for the day. Their comfort zone is also significant as they are less adventurous and are open to reusing the same recipes.
I gathered my qualitative research and created two user personas to summarize and categorized my findings. Amanda is an amateur cooker who lacks basic skills and knowledge in the kitchen ,while on the other hand Alex is a more advanced cook who is more confident and adventurous in the kitchen.
I started the ideation process by creating the information architecture of the app. Reflecting on the user interviews I conducted, I concluded that there are two main goals that Millennials are seeking from a recipe app.
1. To find and explore matching recipes quickly
2. To create a comfort zone with recipes they love
Therefore, keeping the user's priorities in mind, I decided to have a menu with only two key features, Explore and Your Favourites. Explore is where users can find recipes based on existing ingredients or by simply using the search bar. Your Favourites is where users can create and store recipe in groups.
After I had finalized the information architecture and site map of the app, I proceeded to map out the four user flows I wanted to target.
Since time and simplicity are very important to the users, I want to ensure that the user flow can take users to their destination in the shortest amount of time.
I drew sketches to explore different concepts, although I wanted to incorporate a unique design and decided to prioritize a sense of familiarity. I based my design by having familiarity to support my app which aligns to other real-world objects which will help guide users to use the product without thinking. Since the users want “fast” and “simplicity”, it is most likely that they do not want to spend time discovering something new that requires time to understand how to navigate. Instead, familiar patterns and interactions will provide a more natural experience for them and will take them to their destination faster.
To solidify my favoured ideas, I refined my sketches to implement more details. Then, I created high fidelity wireframes using Figma.
I created an outline of the colour scheme, typography, and logo I wanted to use for Chefie. I kept the overall UI simple and clean as the main focus of the app should be and more directed to the colourful food photographs and videos to attract users.
To test out the key features of the app, I asked three users to complete a user testing and provide me feedback. Some similar insights I got from the users consist of:
The search bar allows you to explore a singular ingredient or recipe. Cooking time, rating, and ingredients are listed below each recipe card so you get all the information without a click.
Want to narrow down your search to get matched recipes quicker? Filter in the ingredients available in your kitchen to see what you can cook right away. Sort results by cooking time, matched ingredients, or rating.
"Like" a recipe to save it in a group in Your Favourites. Access your favourite recipes in one tap so you can reuse them whenever you want to.
The most enjoyable part of this project for me was being able to interview different users and listen to their stories about cooking. This practice gave me a deeper understanding of how to analyze results from interviews and eventually validating my hypotheses.
The next step in product development would be to further test the prototype on potential users and be more detailed in the tasks that I ask users to complete. Also, I would like to explore more business solutions on how the app can sustain. My current idea for this is to charge users a fee if they would like to reveal more recipes.