Roadsurfer Agent & Manager Admin Page

Task Overview

This project was initiated independently as part of my ongoing practice with Figma Make. I wanted to challenge myself with a scenario involving multi-role communication, admin workflows, and real-time updates. While not tied to a client, the exercise allowed me to refine my UX process—from problem framing to prototyping and UI exploration.

Tools

1. Figma Make

2. ChatGPT for brainstorming and copywriting

3. Maze for usability testing

My approach

Competitive Analysis

The texts I highlighted in red are the ones I see as having potential for design 🧑🏻‍💻

Qualitative research

Interviewee Demographic

Define

See common pattern from the interview

personas

User Journey Pain Points

Sarah's User Journey: Processing a Vehicle Return

The Feelings I highlighted is the one I believe having the potential to develop a design.

Problem Statement

Roadsurfer's current fleet management system relies heavily on manual data entry by station agents,
leading to inefficiencies and potential errors.

Additionally, there are frequent communication breakdowns between managers and agents across multiple stations.
These issues result in slower processing times, reduced accuracy in vehicle tracking, and decreased overall operational efficiency.

As Roadsurfer aims to expand its operations, addressing these systemic problems is crucial for scalable growth
and improved customer service.

How Might We...🤔

"How Might We" (HMW) is a design thinking technique used to reframe challenges as opportunities, encouraging creative problem-solving by transforming identified issues into open-ended questions that inspire innovative solutions.

User Stories

To make my design clear, I need to focus on one specific task for the agent.
I'm focusing right now on an agent who monitors vans coming in and out on a daily basis.
The user story for my design will be: 

"How Sarah monitors the vans coming in and out and checks the list of available vans in the station."

User Flow

Common UI Pattern

Learning from others

Lo-fi Sketches

Mid-fi wireframes

Usability Testing

From the usability testing, I've learned and gained insights that for most users, the upcoming bookings and returns are important.

Additionally, the term "fleet turnovers" is quite niche and might confuse regular people.

With these insights, I decided to move the Fleet Turnovers widget to the left and change the term "Fleet Turnovers" to "Van In and Out."

Usability Testing (again 🤔)

Well, what can I say? After following what the user wants and tested again the screens, the success rate is 60%, which 20% less than I expected 😅

Conclusion

Through this project, I've discovered that a fleet management system is far more complex than simply managing car key handovers.
It encompasses a wide range of crucial aspects:


Safety: Ensuring vehicles are roadworthy and customers are well-informed.
Cleanliness: Maintaining high standards for customer satisfaction.
Administration: Streamlining processes for efficiency and accuracy.
User-Centric Design: Understanding and addressing the needs of agents, managers, and customers.
Communication: Facilitating clear information flow between all stakeholders.
Data Management: Leveraging information for better decision-making and forecasting.


This project has highlighted the importance of a holistic approach in designing systems that not only meet operational needs but also enhance user experience and business efficiency.

THANK YOU!