Learning by Doing!

Ranu Karanpuria
Service Design 2020
4 min readApr 6, 2020

April 5, 2020

Post photos/screenshots from your service prototyping and an explanation of what worked, what didn’t, and what you learned about your service through prototyping.

What worked and what din’t?

I feel the day we narrowed down to the idea of meal box, is the day when all of us started constructing the prototype in our minds. It was interesting to see the layers unfolding in front of us as we started building the scenarios followed by wireframes and then the prototype.

In the initial wireframes, we did see gaps between the actions and expectations between the user and the application that needed to be bridged before making a prototype. Laying out a high-level prototype, was a constructive step for us. We also tried exchanging a google form between us asking questions like:

  1. Who would you like to match with?
    This was to get a sense of if people were interested in exchanging a meal box with somebody they know or with a stranger.
  2. How long would you spend to prepare a dish?
    This question could help us match people with the complexity of the dish in order to make a fair exchange.

3. We also thought of giving the freedom of expressing their craving and ordering the meal based on that could be more interesting. However, it might lead to possibilities where a person might crave something but he receives something totally different. Therefore we realized it would be more efficient if we give the user , preset options to choose from.

4. One of the biggest challenges we are facing is to how might we aid user to feed the recipe on the app in the quickest way possible in a way that does not feel like a chore? In order to achieve that, we thought of breaking down the recipe under broader categories as shown below:

Recipe Breakdown

5. We also thought it could be helpful to have the app suggest ingredients once you type in the recipe in order to avoid typing and making it less of a chore.

6. The primary physical touchpoint is the delivery box, which is features the Potluck logo. The branding has been well received, but there is work to be done in bringing personality to the other sides of the box.

7. When opening the box, the first thing you encounter is a cover, which will reveal information about the who your mystery sender is, an overview of their recipe, where their recipe originates, and the a short note if applicable. The reverse side is where the recipe will be printed. With the content itself set, the graphics are to still be executed.

8. Once the insert is removed, two categories of ingredients are apparent. As is important in the experience of unpacking food from grocery shopping, you need to know which foods should make it into the fridge. On the left side of the box, the narrow compartment can be put directly into the fridge until preparation. The other ingredients can be found in the remaining box. In demoing the prototypes, concerns were raised about the functionality of the refrigerated packaging. Further research into an alternative with more temperature control is needed before the next iteration.

Lofi prototype

What we learned about the service through prototyping?

Couple of things we learned out of prototyping:

- Onboarding and reordering.
What happens when a person who has ordered once wants to order again.
How are we going to modify the onboarding process for the existing user?
Understanding what parameters are going to be constant or variable.

- In the process of designing the prototype, we learned that it would be useful to inform the user how close they are in the process of ordering a meal box. Therefore, we felt a strong need for adding a progress bar in our prototype.

-by Team Potluck

--

--