This case study.

This case study will only cover the dish variants feature that was added as an enhancement 3 months after app launch.

Background (first iteration)

To release quickly, the initial release contained a basic dish creation feature as we wanted to get to market quickly and gather real user feedback on which advanced features they want.

Observation in production

When we received our first 10 orders, 2 of those orders resulted in chefs contacting us as the eaters (buyers) did not specify the type of protein they wanted for a dish as part of their order.

We did start observing the new chefs behaviour and we also noticed their work around for this was to add instructions to the customer in the description of a dish or they have to create the same dish multiple times with different size variations or meat variation.

Problem statement.

Eaters (Customers) need a way to accurately specify their desired dish variables when making an order. This will ensure no errors or assumptions are made by the chefs when preparing the order.

Hypothesis.

Adding a way for chefs to define a controlled list of variants within a dish will result in a better experience for both Chefs & Eaters by ensuring:

• Important dish selections/choices will not be missed by the eaters.

• Smoother operational process for the chefs, less errors & no assumptions are made by chefs when preparing the orders.

• The chefs menu will look neater.

Rapid wireframing.

I started exploring how similar apps were offering the dish creation feature e.g.MyFitnessPal, UberEats, Doordash, Menulog. They were all very different and apart from MyFitnessPal this was mostly done in a web app not on a mobile device (our MVP release was mobile app only).

Usability testing & findings.

Using invision, I performed A/B testing with a 8 participants to test out the chef variant creation feature.

———

Prototype A: There was some confusion around the mandatory selection and the minimum number of items to be selected.

Prototype B: did not allow the user to select a min selection option for a multi-select variant hence not covering all possible cases.

Note: We didn’t end up proceeding with either prototype A or B as the final version

Revised Prototype.

The insights from the useability testing inspired a third prototype which we tested with 3 additional participants and this performed very well covering different types of variants (optional, mandatory, single select, multi select). It performed better as the user was led down a clear path.

Implemented in productions.

We implemented the feature in production after testing the revised prototype and it was great to see what chefs are creating in production.

This advanced feature wasn’t for everyone but it was great to see 65% of our chefs using it for at least one dish.