GV DESIGN SPRINT
SAVR Recipes - Case Study
My Roles - UX Design, UX research and UI Design
Duration - 1 week
PROBLEM BACKGROUND
Working with Savr Recipes, to come up with a solution for their problem, their users find it difficult to follow instructions for preparing new recipes at home. They are looking to create a better experience for their users while cooking new recipes.
Users have expressed problems with timing on recipes not being accurate for a new user with not a lot of cooking experience. As well as the steps in the directions could be laid out clearer and indicate when to prepare for the next step sooner. Users have also expressed they would like to see techniques explained more, such as tips, tricks and maybe an image to show what the recipe should look like at certain points in the recipe.
Main goal is to focus on creating a better experience for users when it’s actually time to cook. Such as giving a better user experience in the beginning process of preparing for the meal, making sure each step is clear with proper definition when suitable.
DAY 01
UNDERSTANDING /
MAPPING
HOW MIGHT WE (HMW)
After creating the persona a problem statement was developed “how might we” questions
to give a clearer statement as to why this app is being developed.
How might we make cooking fun and easy at the same time? Or How might we make the cooking experience worthwhile?
Spent some time looking at other competitor products for inspiration and to see how they solved the problem similar to the one I’m trying to solve. The three competitor apps I looked at were AllRecipes, RecipeBox and Slowcooker. All three had great features and lots of inspiring ideas. As I went through each of them I took notes on how information for ingredients and directions were laid out since these were the target for solving the problem. I’ve attached some screen captures of the apps I went through.
Competitor Products
Crazy 8
Three-Panel Board
After looking at competitor’s it was time to start sketching the most critical screen using the Crazy 8 method. Taking the ingredients screen as the most critical screen since this is where users gathered most of their knowledge about the recipe. Also using the information from the user interview and user input as to where they struggled. As well as incorporating the user's frustrations, goals and behaviors.
Once the critical screen was sketched into 8 different ideas it was time to decide which sketch was stronger when it came down to solving the problem for the users.
After deciding the strongest sketch the next step was to create a three-panel board of (1) the screen that comes before your critical screen, (2) the critical screen itself and (3) the screen that comes after your critical screen. Creating a small storyboard of how the user will interact with each screen, what the results from the user interactions and what the user will do next in a real life scenario.
DAY 02
SKETCH YOUR SOLUTION
DAY 03
DECIDE AND CREATE
A STORYBOARD
After taking some time to create a three-panel board sketch it was time for the next step. Start making wireframes, they would be used to tell the user story of how they navigate through the app. This was done using Figma and also plugins from the community of Figma.
Home screen would start the app for the user. At the home screen the user would choose from feature recipes, a recipe be level of experience or a recipe with specified timing. From this screen they would be directed to a screen with another breakdown of what kind of meal they’re looking for such as breakfast, lunch, dinner, ect.
Once a recipe is chosen the next screen will be all the information about the recipe. The ingredients, directions and brief will be a tabbing system so the user can click on the tab needed without having to scroll around or going to another page leaving the recipe. Everything about the recipe should be all in the same place for the user. Using all information from the user research is how the features to the screens were added. Such as a breakdown of time, level of experience, specified ingredients details, images while cooking through steps and a quick briefing of the recipe including any tips.
DAY 04
PROTOTYPE YOUR SOLUTION
Now that the basics of the app is laid out it’s time to start adding more detail to the screen to enable the prototype to be built out for testing. Since the wireframes were built in Figma already, they should easily transform into detailed prototype screens.
This prototype is built with the bare essentials to enable the users to test the functionality of the design. Using the prototype function in Figma I will now use these screens to build out an interactive prototype for the testing portion of the design sprint.
DAY 05
VALIDATE
Last day was spent interviewing participants to test the prototype for SAVR Recipes. As I evaluate each user's interaction with the prototype I will be able to see if the problem has been addressed correctly. As well as getting feedback from the user, this will also help identify the aspects of the prototype that work and the pieces that don’t.
I came up with a usability testing script to use while conducting these interviews. In this script there are 5 tasks/questions that will be asked to participants. Notes will be taken while conducting these usability tests and evaluated as to see if the problem was solved for the users.
1st Round Prototype
USABILITY TESTING
During the usability testing notes were taken from each participant. After conducting these interviews it was time to go through them and find any patterns the user had while conducting the usability testing. Usability testing is extremely useful when connecting with the app's participants, it gives you a clearer result when trying to solve the problem. Also give you insights as to what's not working or what might need a little more tweaking.
NEXT STEPS
This was a very insightful Design Sprint, from only being conducted in 5 days. You still get all the information but at a much different pace. Next I’ll take the notes from each of the usability testing and implement the ideas that came from the users. Hope to do another usability test down the road to see if the changes made make the app even more user friendly. So far I have had great results, everyone said this would definitely be an app them or their entire family could use
2nd Round Prototype
