Led the design of a cross-border transportation platform integrating ticketing devices, an operator portal, and a captain app—bringing real-time visibility, operational control, and data-driven decision-making to international bus services.
The platform supports cross-border bus operators managing multiple moving parts simultaneously.
Fleet: Buses, captains, and ticketing devices
On-ground ticketing: Via handheld reader + printer devices
Route operations across countries and multiple stops
Revenue tracking and reporting across regions
Ticketing is offline-first and captain-driven—passengers board, request tickets, and pay via cash or digital methods.
No centralized visibility into trips, revenue, or fleet status
Manual ticketing prone to errors and revenue leakage
Complex route tracking across multiple stops and borders
No real-time linkage between devices, buses, and captains
Limited insights into high-performing routes or operations
Design a unified ecosystem connecting devices, captains, and operators in real time.
Enables real-time operational visibility
Reduces ticketing errors and revenue gaps
Simplifies captain workflows during live journeys
Provides actionable insights for business growth
"Cross-border bus operations lack a connected system to track ticketing, fleet activity, and revenue in real time—leading to inefficiencies, errors, and limited business visibility."
End-to-end ownership spanning the web portal, captain mobile app, and device workflow design.
Led UX strategy across web portal + captain mobile app + device workflows
Defined system architecture for device-to-bus-to-route mapping
Conducted user research with operators and captains
Designed dashboards, reporting systems, and mobile flows
Partnered with engineering on real-time data synchronization
Understanding the realities of on-road operations was essential to designing tools that work under pressure.
Revenue Blind Spots. Operators had no clear view of daily earnings until manual reconciliation at end of day—creating gaps and disputes.
High Cognitive Load on Captains. Captains managed passengers, payments, and stops simultaneously. Tools needed to be extremely simple.
Device Disconnection. Ticketing devices were not properly mapped to buses or routes, causing tracking inconsistencies and data loss.
No Trip-Level Visibility. Lack of structured trip data made it difficult to analyze performance or optimize route planning.
"Cross-border bus operations lack a connected system to track ticketing, fleet activity, and revenue in real time—leading to inefficiencies, errors, and limited business visibility."
Three interconnected layers covering admin control, device integration, and captain workflows.
System Architecture
Real-time sync across the entire ecosystem · Unified data layer
Centralized control for operators across all machines, routes, and captains.
Profile buses, captains, and ticketing devices with clear mapping and assignment.
Define routes with multiple stops across regions and countries.
Track daily trips, revenue, and active operations live.
Trip timelines, passenger breakdown (adult vs child), route performance.
Structured the hardware ecosystem for accurate data capture and sync.
Each device mapped to a specific bus + route for accurate tracking.
Captains input passenger count (adult/child) for automatic fare calculation.
Automatic fare calculation and instant ticket printing on handheld device.
Transaction data syncs to backend—online or offline-first with queue.
Minimal UI designed for use during live, high-pressure journeys.
Start-of-day workflow aligned with assigned trips and bus assignment.
Mark each stop as completed for accurate, real-time trip logs.
Minimal UI to reduce distraction and cognitive load during operations.
Quick reporting for delays, breakdowns, or border issues in-journey.
Separated complexity based on user context:
Created a structured relationship chain:
Designed all flows assuming real-world constraints:
Shifted reporting from generic logs to trip-level insights, enabling:
The core ecosystem connecting passengers, captains, devices, and the admin dashboard in a real-time data loop.
Transforming a fragmented, error-prone process into a structured, system-driven workflow.
Eliminated manual calculation errors
Created real-time transaction logs
Minimal, linear flow designed for on-road use with zero cognitive overhead.
Operator journey from overview to action — data-heavy but clear.
Reduced decision-making time during journeys
Large tap targets for on-road usability
Structured around the operator mental model: operations → analysis → action.
High-impact screen designed to move from raw data → actionable insights.
Visualizing journey progression with embedded data — a senior-level artifact for auditing trip performance & delays.
A senior-level system design detail: structured device-to-insight mapping that ensures data integrity.
Real-world scenarios covered — showing operational thinking, not just ideal flows.
Store transactions locally on device, auto-sync when connectivity is restored. Queue-based reconciliation.
Retry mechanism with timer + manual cash fallback option for captains. Transaction logged as pending.
Real-time alert surfaced in admin portal if a device is assigned to a different bus than expected. Auto-flagging.
Device enters power-save mode with essential ticketing functions only. Notification sent to admin.
No real-time tracking → 100% real-time trip visibility across all active buses
Manual reconciliation replaced with automated reporting dashboards
Frequent mismatches in ticket logs reduced by 35–45%
Improved trust in revenue reporting across regions
Complex manual workflows → reduced interaction time by 40%
Faster boarding process with simplified ticket entry
No performance insights → identified top-performing routes for expansion
Reduced revenue leakage and improved multi-country scalability
Low-tech environments vs system robustness. Designing for captains with varying tech literacy while maintaining data fidelity required careful trade-offs in UI complexity and automation.
Data accuracy vs ticketing speed. Captains needed to process tickets fast during boarding—adding validation steps improved accuracy but created friction under time pressure.
Usability under extreme pressure. Designing for captains during live journeys meant every tap, every label, and every flow had to work without cognitive overhead or reading instructions.
Designing for operations requires deep system thinking beyond UI—data flow and state matter as much as screens.
Real impact comes from connecting data across touchpoints—device, mobile, and web must speak the same language.
Simplicity in high-pressure environments is critical for adoption—complexity kills usage under stress.
Offline-first is not a feature—it is a foundation for any product deployed in the real world.
"Designed a cross-border bus operations platform integrating ticketing devices, a captain app, and an admin portal—improving real-time visibility, reducing revenue discrepancies, and enabling data-driven fleet management at scale."
