Relay Usability Testing: Key Takeaways from First Round

At Relay, we are dedicated to creating a seamless, family-focused ridesharing experience. As part of our iterative design process, we recently conducted our first usability test, focusing on two essential features: Creating a Request (for parents) and Posting a Ride (for drivers).

This round of testing included both internal evaluations and an external test with three participants aged 30–40—our target demographic of parents. Here’s a recap of what we learned, along with how we plan to address the feedback.

Feature 1: Creating a Request

Participants generally found the process efficient and intuitive, praising the clean design. They also highlighted the auto-complete feature for addresses as very useful, saving time and enhancing accuracy. However, some title text needs revision for better clarification and ease of understanding.

1. Children Selection Icons

Two participants were unclear about the process of selecting icons for children. To improve this:

  • The title will be updated to “Select which kid will join the ride”.
  • The default will be set to no selection for better clarity.

2. Group Sharing Options

All testers found the title for sharing requests confusing. We plan to update it to “Select group to share your request”, ensuring improved comprehension and usability.

Feature 2: Posting a Ride

This feature received positive feedback for its easy navigation, but a few usability issues stood out:

1. Static Map Misunderstanding

Two testers were unable to expand the map and assumed it was static. To address this, we will:

  • Add an icon for map expansion.
  • Enable the map with a location input function for greater interactivity.

2. Children Selection Icons

Similar to the request feature, participants found this step unclear. To improve clarity:

  • The title will be updated to “Select which kid will ride with you”.
  • The default will be set to no selection.

3. Date and Time Selection

Users could select past dates and times, leading to confusion. We’ll implement a restriction to ensure only future dates and times can be selected.

4. Vehicle Details Placement

Testers suggested moving the vehicle details section earlier in the workflow. This adjustment will:

  • Allow drivers to specify their vehicle details sooner.
  • Help optimize ride-matching decisions by considering seat availability upfront.

5. Request Information Context

Participants recommended providing additional details about ride requests to assist drivers in making informed decisions. We’re exploring ways to enrich request descriptions in upcoming updates.

What’s Next?

These findings offer valuable insights into how we can make Relay even more intuitive and user-friendly. As we move into our next sprint, we’ll focus on:

  1. Refining titles and labels for better clarity.
  2. Enhancing address input and map interactions.
  3. Adjusting the UI flow for vehicle details and request information.
  4. Implementing stricter date and time validations.

We’re excited to incorporate these changes and to continue building a community-driven ridesharing solution that parents can rely on.

Thank you to everyone who participated in this testing round—your feedback is invaluable!

Stay tuned for more updates next week!

 

Leave a Comment

Your email address will not be published. Required fields are marked *