Start Your Order

The “Start Your Order” flow is the process where the system collects all of the information needed to start a user’s order and open a new cart.

Overview

The “Start Your Order” flow is the process where the system collects all of the information needed to start a user’s order and open a new cart.

This information is needed to ensure that:

  • The user builds a cart from the correct menu.

  • The order can be fulfilled based on the user’s requirements (location, time, etc.).

  • The correct cart type is created according to the order type.

There are two order types that this process must account for:

  1. Group order: the administrative user creates and pays for the order, but each group member adds their meal to the administrative user’s cart.

  2. Traditional catering order: the administrative users builds the entire cart and pays for the order.

Starting a group order is inherently more complex and time consuming than starting an order on a typical restaurant e-commerce site. This is because more information is initially required from the user.

Goal

Research

Solution

Outcome

Prior to identifying the most important metrics, I analyzed data from the original Scratch Kitchen website, a white label site focused on typical delivery orders, and combed through the Baymard Institute's restaurant e-commerce usability data.

This helped me to better understand how this feature would play into the product’s conversion rate. In particular, it stuck out to me that the white label site’s most comparable feature to the “Start Your Order” flow accounted for its single highest drop off point. With this information, I knew that the most impactful metric associated with this feature was the drop off rate among users who reached the flow.

So, I set a target to move ≥ 80% of users who clicked “Order Catering” through the flow and into an active order state. This would be a substantial improvement compared to the white label site.

I also identified other “sub-metrics” that could influence the drop off rate, like error rates and the average completion time (ACT) for the flow. Identifying these metrics helped me focus the team on an overarching goal, which allowed us to quickly settle debates, confidently make decisions, and manage scope creep.

What Information Do We Need to Collect?

Before diving into the research, I defined exactly what information this flow needed to collect from the user for each order type. I knew that my research would be more effective if I had a clear understanding of what I was designing. 

I utilized two different research methods and sources to inform the design of this experience. Below you will find the most interesting and relevant insights from each. 

The research phase yielded the following three strategies. Subsequently, we conducted usability testing on multiple prototypes aligned with these strategies, ultimately selecting the final designs showcased in the “Work Preview” section..

We exceeded out goal of moving ≥ 80% of users who clicked “Order Catering” through the flow and into an active order state. Our beta users described this feature as clear and easy to use.

Previous
Previous

Menu