top of page

Project : Moving Assistant

Digitizing an offline service request

portfolio content (3)_edited.jpg

​​​​

  • Auto-ethnographic walkthrough

  • Content Analysis

  • Interviews

  • Surveys

  • Thematic Analysis

  • Usability Test

 

 

 

PROJECT DESCRIPTION:   

 

The product is a mobile and web app that lets users request delivery services from available drivers. The original app grouped all additional service options under one section. Customers and drivers have reported issues with the additional services tied to delivery orders.

​

Scope

 

Prioritize moving assistant related action for the additional service investigation:

✔️ Top selected services across most markets

✔️The nature of the moving assistant related service aligned with the business priorities

 

Research phases

​

1. Discovery:

 

Understand the current state of the moving assistant related services (performance, experience, pains, and existing expectations)

​

2. Solutions:

 

Identify the solutions and test the design functionality​

 

Research: Discovery

 

3.png
2.png

Root cause discovery

Customers and drivers have a mismatch in their understanding of the service scope for moving-related services, so disputes often surface at delivery.​

​​

 

Screen Shot 2026-09-16 at 6.29_edited.jpg

​How did the mismatch occur?

​

  • Drivers received training and service scope education through driver training sessions. 

​

  • Customers rely on what they see on the app. The current customer app lacks service-scope education, leading users to form their own assumptions about what’s included and what's not.

​

  • The current arrangement of the additional services is grouped all together despite representing different needs (service, equipment, extra fee), which could hinder users from properly selecting all the choices they need

 

pains insights portfolio content.png
portfolio content (1).png

Ideate - Solution - Test

 

​Solutions (first phase)

​

  • Increase awareness by changing the service naming.

  • Reduce service ambiguity

    • Options for the two distinct service natures in a simple, less text-to-read approach​

    • Include core information that was lacking in the original layout and causes disputes (both customer and driver app)

​

​​

 

​Considerations

​

  • Power users will be using this service multiple times. Much longer steps to complete each order can create huge frictions

​

  • Flexibility for different business use cases (e.g., Some business is unaware of the delivery conditions at the end stops)

​

​​

 

​​

​

  • Include only the must-have info that will impact price and service needs.

​

  • Make it clear that it is optional and users don't have to input all information asked on the app if they don't have the visibility.

​

​​

 

Screen Shot 2026-09-16 at 6.34_edited.jpg
Screen Shot 2026-09-16 at 6.15_edited.jpg
bottom of page