SAVR RECIPES:
DESIGN SPRINT EXERCISE

Savr is a startup that shows hundreds of recipes and cooking tips for at-home chefs. 

MY ROLE 

Lead UI/UX Designer

DURATION

5 Days

TEAM

SOLO

TOOLS

Adobe XD, Adobe Illustrator

DURATION

5 Days

LOCATION

Remote

MY CONTRIBUTIONS

User Road Map,  Lightning Demos, Crazy 8, Storyboarding, Prototyping, Usability Testing

THE PROBLEM

People have been finding recipes on the SAVR app with many steps or more advanced techniques disappointing due to their outcome. They did not feel the instructions were clear or easy to execute. 

 

Create a better experience for users when it’s actually time to cook the recipes.

THE CONSTRAINTS

The recipes are currently written as text, in ordered steps from start to finish.

 

The solution needs to be designed as a feature for the Savr Recipes native mobile app. 

 

It needs to help users when they are in the midst of cooking. 

DAY 1

The goal of the first day was to create a schedule of things to do for the whole week and develop a better understanding of the problem. 

 

USER FRUSTRATIONS

I  received a plethora of information including user quotes about frustrations and a persona. By condensing down the previous user research into problem statements it can help guide me through the design process and better answers to the original problem. 

 

How might we a complicated recipe less stressful?

 

How might we inform the user of what equipment and information they need for the recipe?

 

How might we educate the user on cooking techniques before they start cooking?

USER ROAD MAP

To prepare for day 2 I worked out a potential road map of screens to sketch. These steps correlate to a problem that the user research has identified and the problem statements I came up with. 

 

Less stressful recipe = Preparation of ingredients 

 

Equipment information = Kitchenware list

 

Technique Education = Technique videos

DAY 2

LIGHTNING DEMOS

I downloaded 3 of the highest-rated recipe apps to discover features I would want to include in my app.

 

Features I liked included video steps, cooking time reminders, and cooking time estimations. 

Crazy 8 Sketches

CRAZY 8

I chose my food prep or mise en place step to iterate on. The hope here was to see if I could better show how to prep food

 

After finishing, I felt like my sketches did not fully grasp what I wanted.

 

The best course of action now was to take inspiration from the Tasty App and do something more visual in nature while storyboarding for day 3.  

DAY 3

STORYBOARDING

This whole day was dedicated to storyboarding how I think someone would make their way through the recipe app. 

 

I made sure that all three of the main problem statements had a proposed solution, including time estimations, lists of kitchenware, and preparation of ingredients

 

Lastly, I incorporated more visual elements like technique videos and pictures to help educate the user. 

Storyboard

DAY 4

HIGH FIDELITY

Day 4 was all about finishing the high fidelity prototypes before testing on the final day.

 

I worked mainly on two screens: the homepage and the recipe page.

 

I relied heavily on pictures to help get the point across of what needs to be done on the prep and cooking parts of the recipe.

 

Before heading into user interviews on the final day, the biggest question was if my solutions would translate to a good experience.

DAY 5

USABILITY TESTING

Five individuals ages 24-65 were interviewed via moderated video call. All testees were familiar with recipe applications or websites.

 

The main prompt I had them follow was,

You found a great deal on whole chickens at the supermarket and you want to find a recipe on the Savr Recipes app to go along with it. You have searched for chicken using the discover feature and were given these results.

FINDINGS

  • One person found the amount of pictures great for learning the recipe the first time, but if they were going to do it again, they want the option for a text only recipe. 
  • The ability to share recipes was not immediately apparent to some users. 
  • The checkboxes next to ingredients and kitchenware were confusing to some users. They expected something to pop up after clicking them outside of the checkmark. 

WORK TO BE DONE

  • More iterations or a redesign of the top menu are needed on recipes that can help users navigate, share, and save recipes
  • I need a better way to indicate that you can create grocery lists by clicking on the boxes next to the ingredients. I can also eliminate that feature and keep it simple. 
  • There needs to be an option for text-only recipes, to reduce scrolling and limit potential heavy data usage for mobile. 

WHAT I'VE LEARNED

  • Overall, the reception of the high fidelity designs was taken surprisingly well. Mostly due to the great visuals. 
  • When it comes to recipe designs, sometimes it’s good enough to take inspiration from similar apps so that users are familiar with how your product works.
  • You don’t have to reinvent the wheel.