Savr
Savr is a new startup that shows hundreds of recipes and cooking tips for at-home chefs
CONTEXT
Overview
Savr, a startup offering a wide range of recipes and cooking tips, identified a problem: users were excited about cooking but often found it difficult to follow recipes, leading to disappointment. To address this, Savr initiated a design sprint with my help to create a solution that would simplify recipe following and enhance the overall cooking experience.
Duration
February 2024 - February 2024
Objective
How might we help users follow recipes easily and confidently, making cooking pleasant and stress-free?
Outcome
Reimagined the user experience to eliminate cooking stress and increase engagement.
PROBLEM
Users faced several challenges:
Users had to interrupt their cooking to check their devices frequently.
Uncertainty about cooking progress, and confusion about the next steps and techniques, led to mistakes and frustration when results fell short.
The constant need to consult their phones for guidance added stress, turning cooking from a joy into a tense task.
SOLUTION
Reimagining the user experience to eliminate cooking stress and increase engagement:
By introducing different viewing modes tailored to various cooking skills.
Preparing a comprehensive list of necessary tools upfront so users don’t have to get things out during cooking.
By providing ingredient details with prep times and instructional slides with photos, I aimed to equip users with the knowledge and confidence needed for a seamless cooking experience.
To further enhance the experience, include detailed instructions for plating so users feel more satisfied with their creations.
A platform for users to share their cooking experiences, tips, and creations, making cooking more interactive and rewarding.
5-Day Design Sprint
5-Day Design Sprint
DAY 1
Mapping
On the 1st day of the design sprint, I crafted a map outlining various solutions within the app, all aimed at seamlessly guiding users toward successfully preparing the meals. This exercise enabled me to broaden my ideas and generate a wide range of potential solutions, regardless of their feasibility.
[Mapping - Imagining possible solution]
DAY 2
Sketching
On Day 2, I started by sketching several solutions from the map to refine the concepts further. This process allowed me to consolidate my ideas into tangible options and identify the most viable ones. Utilizing the Crazy 8s Sketch Exercise and the 3 Solution Sketches, I successfully narrowed down ideas to integrate into my final solution.
Ideas for the Prototype:
Different viewing modes to accommodate the user’s cooking skills
The progress bar shows at the top of the recipe for users to know what percentage of the process they’ve finished.
Show all tools needed before cooking so users don’t need to get them out during cooking time.
Separate the prep and cooking times, allowing users to prepare all ingredients in advance. This approach ensures users can concentrate on cooking without feeling rushed to prepare ingredients during frying, baking, or boiling.
Display the ingredients before and after preparation, enabling users to be better equipped for the cooking process and reducing any feelings of confusion.
Have the plating description at the end so users can be more satisfied with the results.
Make a review section where users can leave comments, and tips, and upload their finished dishes.
[Crazy 8s Sketch Exercise]
[The 3 Solution Sketches]
DAY 3
Storyboard
On Day 3, I started transforming the solutions into a 12-panel user flow through storyboarding. This step solidified my ideas into tangible solutions. At this point, all previously selected ideas evolved into features within the app, providing me with a clear path toward prototyping.
[Storyboard]
DAY 4
Prototype
On Day 4, I developed a prototype in Figma, guided by the storyboard. During this phase, I discovered that the status progress bar at the top of the recipe page was redundant. Given that each step was numbered and users were informed about prep and cooking times, tracking the percentage completion of the recipe seemed less critical. This insight emerged as I delved deeper into the development process.
The prototype started when the user selected their desired dish. To address the identified issues, I consolidated all the key features into a single screen with tabs, enabling users to navigate effortlessly while cooking.
Different viewing modes:
Directions (w/no pictures) - This is for the users with more advanced skills who want to see the list of steps on one screen.
w/Images - Users with more intermediate skills need pictures to follow the steps clearly.
Step by Step - One slide per step with directions, ingredients, and the tools needed to follow the recipe.
Join playdates with other local moms
Connect with moms nearby to exchange/buy/sell kid’s books and toys
2. Fostering connections through meeting new mom friends.
Go through profiles of moms to find new mom friends
Send friend requests
Chat with new connections
3. Empowering Meaningful Interactions through playdates and exchanging used baby items.
DAY 5
On the fifth day, I conducted prototype testing by interviewing five individuals with diverse cooking abilities. The tests were conducted via Zoom, allowing me to observe the participants interacting with the prototype and discuss their actions throughout the testing process. Each participant had prior experience with using online recipes, giving them a general understanding of navigating the app. Below is a summary of the findings from the interviews:
All testers liked the idea of prepping the ingredients and tools before cooking.
The tester, who is not proficient in cooking, thought directions on each slide were helpful but still had to return to the phone every time.
Some testers said that the ingredients list needed to be easier to read. They wished the font size was larger and in a table more than in the list.
It would be helpful if the slides turned automatically so they don’t have to touch the phone.
The review section is hidden underneath the directions. They want to see a tab for the review at the top so they can read it before deciding if the recipe is doable for them.
Some testers said they like to follow recipes on YouTube. They would like to see a video version of the cooking so they can follow it without reading the recipe during cooking.
I gathered valuable comments from these tests:
Most people wanted to see the videos for the recipe, and it would be an effective solution for many of the addressed problems. If I had to do this over, I would implement the video of how to cook the recipe after consulting with the stakeholders for feasibility.
I would re-design the ingredient and tools tab so they’re much easier to read during cooking.
I agree with some testers that the review section needs to be more exposed so the user can access it before deciding to cook the recipe.
Test
ITERATIONS
Lesson Learned: Less is More!
Initially, I arranged several profiles on a single screen, allowing users to scroll down to view additional profiles to make the app fast and user-friendly. Usability testing revealed that the layout was overly cluttered and slowed users' ability to choose a profile, leading me to decrease the display to two profiles. Subsequent usability testing showed that presenting a single profile per screen allowed users more time to absorb the information and complete tasks more efficiently.
I discovered that my attempt to simplify the user journey by compressing information into a smaller space and reducing the number of required actions actually backfired. Instead of making the app more user-friendly, it resulted in a cluttered interface and made the information harder to access.
Reflection
At the beginning of the project, I fell into the common pitfall of trying to simplify the user experience by compressing information, mistakenly believing this would streamline and expedite the app's use. This approach, however, had the unintended consequence of complicating navigation and usage. This experience taught me that a more condensed user flow does not inherently equate to a more intuitive user experience.
CONCLUSION
Reflecting on this project, I gained valuable insights into the daily challenges of work-at-home moms, who often feel under-supported by their family and friends. Should I have the opportunity to revisit the project, my priority will be to deepen my empathy for the users. I aim to introduce features that highlight their challenges more and foster a community that supports and empowers mothers to balance careers and family.