Savr

Responsibilities

I took on this solo project to design a digital product that connects with a complex physical task. I aimed to build a supportive tool within the bounds of a modified Google Ventures Sprint.

While the project is in the prototype stage, I'd enjoy developing it further.

Understanding Savr's customers

I reviewed the interviews and personas on day one to define the user needs and problems. I synthesized the user feedback through affinity mapping, where I grouped common themes and identified the following core points.

• People want to see their cooking progress so they can learn and correct errors.
• Touching mobile devices disrupts the cooking process and users want a more hands-free experience.
• People want to visualize the entire cooking process and identify opportunities to save time.

Scoping an end-to-end solution

After identifying the core problems, I jumped into imagining possible solutions and developing user flows.
I split the cooking process into two main phases: Prep and Cooking.

• Prep: Users need to prepare for the cooking process by collecting the required tools and ingredients, learning new techniques, and reviewing the overall steps.
• Cooking: When users start cooking, they need a tutorial experience that walks them through the recipe so they can reference tutorials and visuals.

Finding inspiration

On day two, I reviewed other products to understand how others solve these problems in a solo lightening demo format.

I reviewed five products, to learn how they approached step-by-step tutorials and voice command controls. I was inspired by the following features:

• "Step-by-step" modes allow users to focus on each cooking step and learn new techniques.
• Video media is an effective way to teach users and help them confirm they are following the recipe correctly.
• Voice-controlled assistants need to show when they are listening to commands.
• Suggested commands help users understand the capabilities of the assistants.
• The assistant experience should be conversational and engaging.

Sketches and storyboards

Following the lightning demo, I used the Crazy 8s method to ideate different solution screens quickly.

Before starting the exercise, I selected the recipe step page in the Cooking section of my end-to-end flow because the users expressed many frustrations from inefficient steps that often ruined their cooking experience. I also wanted to find a way to minimize touching the device when navigating or completing tasks.

I ideated eight ideas and selected my sixth idea to develop further in my day three storyboard.

Testing with people

After completing my prototype on day four, I conducted five usability tests on day five to iterate on and improve the solution.

I tasked participants to prepare a cookie recipe and gave them scenarios where they would need to engage with Sage, the voice assistant bot. I verbally assisted with the voice commands because it was beyond the prototype's functionality.

Participant feedback prompted the following core changes to the design:

1. Added more tutorial content through video visuals and "Tips" to give users more learning opportunities in the app.
2. Rebranded the voice assistant with a more friendly persona and better defined its scope with a new introduction message.
3. Redesigned the timer button and added "Up next" previews to create more straightforward navigation in cooking mode.

What's next?

I enjoyed addressing a design challenge through the Google Ventures Sprint methodology.

The time constraints and new strategies helped me learn about pacing myself and challenged my creativity.
I would love to participate in another design sprint with a team to experience the entire process.

I'm also interested in further developing this project and delving deeper into conversational bots and hands-free interactions. This project highlighted the complexity behind creating engaging interactions with a bot, where design choices must reduce ambiguity so users feel comfortable engaging with the tool.