GoWheels: designing my first dashboard system

GoWheels was my first dashboard-heavy system, and my first time designing across five different roles inside one product. I joined as an intern with no prior experience building admin panels or multi-role systems. Passenger, driver, guide, agency admin, and a super admin panel, each needing its own interface off the same shared data underneath. The actual problem was never booking. Group trips were coordinated over phone calls, WhatsApp, and PDFs, which worked at a small scale and fell apart once trip size grew. Missed pickups, drivers arriving at the wrong location, guides left uninformed, agencies losing visibility the moment a trip actually started. Most of the failures were happening at the handoffs between roles, not inside any single screen. So I designed one core system with role-specific interfaces instead of separate tools or a single do-everything app, and moved coordination into trip-based communication tied to a trip ID, replacing the external WhatsApp groups that kept losing context Stakeholders reviewed and approved the design with no major rework requested. Rollout is currently on hold with the client over a payment logic decision outside the design scope, so it has not gone live yet. This was the project that actually taught me how to design dashboards, not a course or a tutorial. Real constraints, a small development team, a fixed budget, and a client who needed the coordination problem solved before anything else. First projects rarely feel finished. They just teach you the most. https://www.designedbyharish.in/work/gowheels-multi-role-mobility #uiuxdesign