REHALworkforce mobility, without the operational chaos.

The problem

Managing transportation for a handful of employees is straightforward. At enterprise scale, it's an entirely different challenge.

Built for enterprise organizations in Saudi Arabia, Rehal helps companies coordinate workforce transportation at scale — from assigning employees to vehicles and routes, to tracking daily operations — replacing fragmented manual processes with a centralized system designed for operational efficiency.

This project wasn't about designing another enterprise dashboard. It was about understanding how transportation teams actually work, and turning operational complexity into something intuitive.

Transportation teams were relying on disconnected tools, spreadsheets and manual coordination. Every change — assigning a driver, updating a route, accommodating a last-minute request — required multiple people and too many manual steps. As organizations grew, so did the complexity: managers needed visibility into thousands of daily trips, while administrators had to maintain vehicles, routes, drivers and company data without slowing operations.

End-to-end product design

I led the process from discovery through developer handoff.

Working closely with stakeholders, I translated real transportation and operational workflows into a scalable digital experience.

One decision changed the architecture

A transportation manager and a system administrator perform entirely different jobs.

One cares about today's operations. The other manages the entire transportation ecosystem. Trying to satisfy both through the same interface would only increase cognitive load — so I designed role-specific experiences instead of one feature-heavy platform.

Progressive complexity

Turn one complex dependency chain into six clear decisions.

An employee belongs to a company, works a shift, and needs a pickup. The pickup is assigned to a route, which requires an available vehicle, which requires an available driver — a small change to one element can affect the entire journey.

Rather than exposing this complexity all at once, I designed progressive workflows that guide users through each decision step by step. People only see what they need at that moment, keeping scheduling structured and predictable.

What's happening right now?

Transportation managers don't begin their day by opening reports.

That question shaped the dashboard. Instead of filling the interface with charts and navigation, the first screen prioritizes operational awareness over everything else.

• Active trips and pending pickups
• Vehicle availability
• Delays requiring attention
• Quick actions for common tasks

The result is a dashboard that supports decision-making rather than simply displaying data.

What guided the interface

Enterprise products get cluttered because every department requests new functionality.

Throughout the project, I challenged each addition with one question: does this help users complete today's work more efficiently? If not, it didn't belong on the primary experience.

Complex behind the scenes. Clear at the point of use.

By organizing the experience around user responsibilities instead of system features, Rehal became easier to navigate, easier to scale, and better aligned with how transportation teams actually work. While the platform handled thousands of operational variables behind the scenes, users saw only what mattered, at the moment they needed it.

What I carried forward

Complex systems don't need complicated interfaces. They need thoughtful structure.

Rehal reinforced something I continue to apply across every product I design. It wasn't memorable because of the number of dashboards or features it contained — it was memorable because of how information architecture and role-based experience simplified an operationally complex environment.

• Role separation reduced complexity before any UI styling did.
• Information architecture became part of product strategy.
• Operational dashboards work best when they lead to action.