Problem Discovery

Test Results

Most users had no issues navigating through the screens, and selecting a recipe to cook. The confusion came after the recipes were selected, and there was two primary issues reported:

1. The "Prep work" tab was overlooked by multiple users, meaning it was too easy to miss

2. After completing a recipe, navigating out of the review page was very confusing

Savr is a cooking app for at home chefs. It helps users discover new recipes, and learn how to make them from scratch. Eventually, they started to receive negative feedback on some of their more compilated recipes.

Users were having trouble with timing, preparation, step order, and getting desired results. This was leaving them hungry, disappointed, and felling like they had wasted their time.

User Research

Based on their reviews, Savr conducted user interviews and provided research data for this sprint. The results were as follows:

• Users want to be fully prepared before starting recipes

• Users want to be efficient and minimize waste (wasting food, time, & dishes)

• Users are getting confused and making mistakes, causing a negative experience overall

Day 1: Mapping

Day 3: Storyboard

Flow Mapping

Based on user feedback, the simplest solution to the most users' problems would be providing a clearly labeled step in their flow, where they are guided through their recipe's prep work. After which, users will be able to view the full instructions and continue along with the recipe. Additionally, if there is any work to do while something else waits, it will be clearly indicated to users.

Day 2: Sketch

To inspire possible solutions, research was conducted on competing recipe apps, as well as basic tutorial apps and websites. Successful elements were marked for reference, while taking note of unsuccessful elements too. Then the sketch process began with a round of Crazy 8's:

After completion, the sketches were analyzed for which would best suit users needs. The keys here were recipe clarity, to clearly section off the prep work, and guide users through a more step-by-step process. The top left and bottom right screens were chosen to be combined into an MVP that showcased the following elements:

• Video recipe tutorial included

• Preparation has it's own tab

• Ingredients are listed on recipe front page

Day 4: Prototype

With MVPs chosen, the story board was underway. A standard user flow would include launching into the home screen, browsing for a recipe, cooking the meal, and leaving a review (optional). For optimal app experience, users should be able to revisit their favorite recipes, and save others for later. All of this was taken into consideration, and the MVPs were expanded into a full storyboard.

Day 5: Testing and Iteration

A prototype was created next day on Marvel. The application made it very easy to recreate the story board and link together the different slides. No design changes were made at this stage, the prototype was simply created to replicate the storyboard, and would soon be tested to gather user feedback.

Final Iteration

A few quick fixes were applied, and the final solution complete:

• The prep work tab was given a bolder text and underline

• The first step of each instructions page would now read "Complete the prep work," and link users directly to the prep directions

• The review page had its navigation fixed, now either directing users back home, or to their profiles.

Conclusion/Reflection

Completing this design sprint was a good introduction to the quick turnaround times that are possible with UX design. Learning how to design, prototype, and test while in a time crunch will be an essential skill I carry for the rest of my career in UX. The greatest challenge in this process was only having one point of user contact, and that being at the very end. As a result, I had to assume solutions based on user feedback provided on the first day, and I did not get to test those solutions until the final step. Despite its difficulty, this was good practice for putting myself in the mindset of a user, and designing according to their expressed needs.

The combination of a clearer layout of the steps and an optional video should help users of all experience levels have a deeper understanding of the recipe they are about to make.

A more detailed iteration would likely solve the first issue by increasing visibility, but the second problem was certainly an issue for user experience. Users could not be left feeling stuck after completing their recipes.