How a small design change uplifted the goshop experience

Fatih Hamzah27 May 2022

Problem

GoShop is a Gojek service where a customer writes what they need, marks the shop on a map, and a driver buys the items. Many bookings were never completed because drivers could not find the shop. Small shops often have no name on Google Maps, and some drivers were new to the area and relied on the map alone. The post gives no figure for incomplete bookings.

Example from the article: Customers could attach a note to the shop location on the map screen, but a funnel check showed that very few did, and it was rarely used at checkout either, because that meant an extra step back to the map.

Solution in brief

Interviews with customers and drivers explained the failure, and the team concluded that the customer, who knows where the shop is, should supply that detail. The team moved the note input onto the checkout page, where users review their order, and ran an A/B test against the old flow. More users wrote location notes, and booking completion rate rose with statistical significance.

Questions this case answers
  • How to increase task completion on a two-sided service when the performer fails because the requester left out information the performer needs
  • How to make users fill in an optional field that improves the outcome for the other side of the transaction
  • How to raise the completion rate of orders that depend on a free-text detail the customer must supply
  • How to find out why an existing optional input field is rarely used

Tools and methods

  • Funnel analysis — showed how rarely the location note was filled, at the top of the flow and at checkout.
  • A/B test — compared checkout without the note field (control) with checkout showing it.
  • Customer and driver interviews — found why drivers failed to find shops.
Continue reading — it's free

Google or a one-time email code. No password.