Savr: Modified Design Sprint
Context
Savr is an app for a community of at home chefs who want to learn more about cooking while following recipes.
What I did:
Google Ventures style design sprint — understand, map, sketch, prototype new feature for Savr.
What I learned:
Inspiration can come from unrelated places. I.e. Groggs knots provided the best step by step instructions I could find.
Design constraints:
Recipes are written in basic text lists i.e.: 1, 2, 3 etc.
Solution should be ‘feature’ for Savr native mobile app
Focus: on when user is following recipe (not how to find recipe etc.)
Day One // Understand & Map
Despite the design constraint that the recipe lookup feature be native to Savr, I chose to design the mobile site and native app to look identical. I committed to the assumption users were more likely to use an app exclusively, if they first had some success (i.e. discovered it) on the mobile version.
Day Two // Sketch
For sketching ‘crazy 8’s I decided the critical screen was the action step. I.e. the recipe instructions. This page has to interface with ingredients, imagery, instructions and forward looking prep steps.
Most importantly, the recipe instructions is the screen users will navigate to and from the most while cooking.
The ‘three panel board’ would then naturally have to address the screens before and after the main recipe instructions. So, search results before, and step by step instructions after the main recipe instructions.
Day Three // Storyboard
Storyboarding a relatable moment… From fridge, to ingredients, to recipe search, final decision, checking ingredients needed, double checking the prep steps, to step by step instructions, plating and finally eating.
Day Four // Prototype
I intentionally chose to layout recipes two ways.
The first, for the glance and scroll cook —quickly scroll down to recipe ingredients and instructions and glance at photos.
The second, for those more invested —click the simple viewer play button and move through a swipeable navigation with video segments for each step, written critical instructions for the current step (with all previous steps deprioritized but still displayed), and an easy access tab to view all ingredients at any time.
Day Five // Test
I ran 5-testers aged 18-65 through the a hi-fidelity prototype. Users had fun and found the information easy to access and search. The prototype suffered from the expected downfalls of not having ready made video segments or .gifs of the cooking steps —meaning the simple viewer had to be explained and imagined (sub optimal).
Going forward, accessibility should be considered and audio instructions and search patterns may be added.