Work CasGo
B2B Platform Operations Web App UX Research

Casino shuttle management — from WhatsApp & spreadsheets to a single platform

Role Product UX Designer
Client Hard Rock Casino
Platform CasGo Web App
Timeline 3 Months — Q2 2022
Hard Rock Casino × CasGo

The problem in one sentence

Casino operations teams were managing player shuttles across WhatsApp groups, Excel sheets, and phone calls. Operators were unverified, schedules were missed, and real-time updates simply didn't exist.

CasGo was built to replace that chaos with a single B2B platform — giving casino admins control over operators, vehicles, agreements, schedules, and live tracking in one place.

Casino operations teams currently manage transport via spreadsheets, WhatsApp groups, or manual calls. Real-time updates are missing.

PAIN POINTS

Managing

Employers spend hours creating and verifying new operators with no centralised record.

Agreement

Manually checking books to confirm whether an operator is registered for a route or not.

Tracking & Scheduling

Operators often change operation areas based on demand — no visibility into which agreement is currently active.

Understanding before designing

User journey map and persona — Andrew George

Persona + journey map — 120 historical trip records reviewed to surface real patterns

Primary persona — Andrew George

Transport & Operations Admin, Las Vegas. Manages multiple shuttle operators, vehicles, and player pickups daily — entirely through WhatsApp, Excel, and calls. Constantly firefighting missed trips, unverified operators, and stale schedules.

Journey mapped across 3 phases

Managing Manually → Scheduling Routes → Tracking & Reporting. Pain was concentrated at agreement verification and live schedule updates — the two moments where the current tools failed hardest.

120 trip records reviewed

Internal logs surfaced the patterns: most delays traced back to operator onboarding gaps and no live status visibility during active runs.

12-week design process — Discovery through Delivery

12-week process — Discovery, Strategy, Architecture, Visual design, Iteration, Delivery

5 workflows. One platform.

Rather than a feature list, CasGo was designed around 5 real admin workflows — the jobs to be done that Andrew and his peers actually performed every day.

01

Adding Operator

Register transport operators with document tracking, vendor details, and active/inactive status — replacing hours of manual verification.

02

Creating Agreement

Link operators to specific properties and schedule types (weekend, weekly, monthly, yearly) in a 2-step flow — Agreement Details → Schedules.

03

Scheduling Buses

See all shuttle runs — picking up, departed, arrived — with live status tags and player counts. Add players via swipe card or universal ID scan.

04

Managing Operations

Live map tracking, trip detail feed, occupancy trend charts, and automatic failure alerts — all on the dashboard, filtered by property.

05

Reports

Historical data across trips, operators, and vehicles — surfaced in context, not buried in a separate reporting module.

CasGo Dashboard — live tracking, trip details, occupancy, alerts

Dashboard — live vehicle tracking, trip feed, occupancy trends, and arrival failure alerts

What this project taught me

Simple Workflows Are Powerful

The goal wasn't to add more features, but to reduce friction in everyday tasks.

Data Needs Context

Numbers are useful only when they're presented meaningfully, at the moment of decision-making.

Systems Thinking Matters

This project connected people, vehicles, routes, operators, agreements, schedules, and reporting. Designing meant thinking in relationships, not screens.

This project reminded me that good UX is not about making screens look pretty — it's about understanding the messy real world, and simplifying it.

LET THE DESIGNING BEGIN!
✅ Message sent! I'll get back to you very soon.
Please enter your name.
Please enter a valid email.
Please enter a subject.
Please write a message.