SAVR
Overview
Making dinner is important. So important that a market exists with endless applications you can download for recipes and dinner ideas. The competition is fierce and if an application provides a lackluster experience, they likely lose a user for good. SAVR Recipes provides a service of providing users recipes on multiple levels of complexity. However this firm is seeking assistance to improve the user experience based on user feedback.
Problem Statement
The problem that SAVR Recipes is currently enduring is the lack of structure in providing cooking instructions. This is because of the many variables that occur when preparing and cooking complex dinners courses. This problem is relatively challenging because of the different factors that occur for each meal created. Finally the lack of detail that is provided from a recipe is causing mistakes and an unfavorable experience during the entire process.
My Role
My role in this modified GV Design Sprint case study was to enhance the user experience. By designing a framework that increases the quality of the cooking process and reducing breakdowns while cooking a meal.
How might we organize the cooking process better?
Day 1
Based off the user interviews and feedback, below show the major pain points from what I determined.
-
Unknown next steps
Issues with referring back to phone
Unsure if meal is going properly
Surprises hurt outcomes
When a user searched a recipe the design should provide options. Those include a video, recipe, instructions but most importantly a play by play.
Day 2
Based off my finding these particular features supported my position to add value in organizing the cooking process.
Step by step directions
Videos for a class
Checked boxes for progress
To reduce unfavorable outcomes during ideation I sketched to determine the best way to lay out multiple options and preparation for cooking the meal.
The layout has a video at the top, with the recipe and instructions at the bottom. Then leads into the step by step process.
Day 3
Story Board
This prototype is designed for a user to log in, search a dinner meal and have multiple methods of explanation of the process.
The goal for this prototype is it is easy to use and can a user operate it while cooking.
I hoped to learn during testing if the options add value to the application and where some design blind spots exist for the play by play process to cook a meal.
Day 4
The four slides here for the prototype show where I want to test. In addition a user would have to review recipe and instructions prior to starting.
Review Here
Day 5
Validation User Interviews
-
All were over 40 years old
Two stated reviews encouraged their decision to make new dish
Cooked between once to seven days a week 4 out of 5 did not watch a video when learning a new meal
Every user stated they started with Google for new recipes
-
Users agreed reviewing the recipe, instructions and video gave them confidence
All five users said they would select recipe first
Two of the three liked the pictures
One asked When does this app come out so I can download it?”
Felt the play by play structure was easy to follow
-
Users picked up the applications functions quickly
Users needed little direction when working through the play by play screens
Conclusions proved true of simplicity of process
Conclusion
By providing the recipe, instructions then a step by step the users followed the process without any breakdowns. Reduction in surprises is minimized due to having all the information up front. Each step has pictures to give a user comfort in where they are in the process.