When the Van Departs but the System Doesn't : Aagan Sewa Yatayat runs one of Nepal's recognized EV van operations — connecting passengers across multiple cities through a network of daily trips that move fast, and leave on schedule. But behind every punctual departure was a counter system held together by memory, paper, and habit. Passenger details were tracked manually. Trip records were scattered across handwritten logs. When a ticket was lost, so was any proof of booking. Day-end reports for each vehicle drained time that counter staff simply didn't have. The people running these counters were experienced, fast, and deeply familiar with how the operation worked — but the tools they were given had never been designed with them in mind. That was the real problem. Not the technology. The assumption that technology alone was enough.
The User Nobody Designs For : Before a single wireframe was drawn, I made one decision that shaped everything that followed — I designed this app for the counter person, not the product manager. Counter staff at Aagan Sewa Yatayat were not digital natives. Many were not highly literate with technology, had never used a dedicated operations app, and were working in a fast-moving environment where confusion costs real time and real passengers. This wasn't a limitation to design around — it was the most important design requirement of the entire project. I began by understanding how the counter operation actually functioned in real life — the sequence of events from trip creation to passenger boarding — before translating that reality into user flows, information architecture, wireframes, and personas. The app was built to integrate with the existing ERP backend, but its soul was always the person standing at the counter.
Complexity Hidden. Clarity Shown.
The design challenge was this — build a system powerful enough to handle online booking, passenger management, ticket generation, seat reservations, trip cancellations, driver assignments, and day book reporting — and make it feel like it does none of that. Every screen was stripped to its single most important action. No unnecessary options competing for attention. No terminology that assumed prior digital experience. Visual hierarchy did the heavy lifting so that a counter person could look at any screen and immediately know what to do next without reading a manual or asking for help. A/B testing drove two versions of the app — the second shaped entirely by watching real counter staff use the first under actual operating conditions. The feedback wasn't about features. It was about moments of hesitation. Those moments became the roadmap for every iteration that followed.
The Counter That Finally Kept Up
The app launched to immediate approval — from the client, and more importantly from the counter staff using it every single day. Onboarding was smooth. The learning curve that everyone feared never arrived. People who had spent years managing trips manually found themselves navigating the system confidently from their very first shift — which was the only metric that truly mattered. Lost tickets became a problem of the past. Day book reporting that once consumed the end of every shift was now generated automatically. Passenger management, reservations, and cancellations moved from verbal coordination to a single organized screen. Aagan Sewa Yatayat's counter operation went from controlled chaos to a structured, digital-first system. But the real achievement wasn't the digitalization — it was proving that when you design for the person least expected to adapt, everyone else adapts effortlessly.
