AMyanYout
A logistics platform built to replace paperwork, phone calls, and scattered spreadsheets bringing parcel tracking, pricing, and operations into one real-time system.
Details
4 Months
Website
Dashboard
Delivery & Logistics
Figma + FigJam
What I do
I was the sole designer working with two developers. My scope covered stakeholder workshops, workflow mapping, information architecture, wireframing, UI design across three user types: customers, drivers, and operations staff, and full developer handoff with annotated specs.
EXISTING WORKFLOWS
As customer demand grows, manual paperwork and communication become bottlenecks to efficient operations.
The team was running a real business through whatever tools were available. Customers called to ask for prices. Parcel tracking lived in spreadsheets that someone updated by hand. Customer details were written on paper. When a delivery went wrong, drivers tried to remember what happened.
THE PROBLEM
Three different groups of people: customers, drivers, and office staffs were all working around the same gap. Each group needed different things, used different devices, and ran into different problems every day. The challenge was to design one system that worked properly for all three.
How might we replace every manual workaround with one connected platform, built for all three users without making any of them feel like an afterthought?
UNDERSTANDING THE EXISTING OPERATIONS
Map the existing workflow first, then find the priorities.
Before jumping into solutions, I mapped the current workflows with stakeholders to understand where the real friction lived - how pricing was communicated, how parcels moved through stages, how drivers logged deliveries, and where information got lost between roles.
Manual WorkFlow
Customer calls staff to ask for a price quote.
Solution
Self-serve pricing inquiry with two parcel type tabs.
Manual WorkFlow
Drivers scroll long lists to find the right parcel and update status by hand
Solution
Barcode scan triggers instant status update, no searching required
Manual WorkFlow
Parcel stages updated manually in Excel, entries missed or mislabeled
Solution
Five-stage pipeline with role-based automatic updates
Manual WorkFlow
Delivery disputes investigated from memory, no proof, no record
Solution
Proof of delivery: photo, driver name, attempt number, stored per customer
Manual WorkFlow
Customer records stored on paper, retrieval took minutes
Solution
Searchable digital database: centralized, secure, retrievable in seconds
UNDERSTANDING THE USERS
Three types of users.
I have to think about three types of users and how the system will relate to each other. A customer using a laptop to check their shipment has completely different needs from a driver checking payment status on their phone at someone's front door. And both of them are different from the office staff managing hundreds of parcels from a desktop.
Customers
Sending parcels from China to Yangon
Needs to get a price estimate, place an order, and track their shipment without calling anyone.
Website
Self-service
Drivers
Completing last-mile deliveries in the field
Needs to find the right parcel fast, know the payment type before arriving, and log proof of delivery on the spot.
Mobile Web
Field Use
Operation Staffs
Managing the entire pipeline from warehouse to delivery
Needs to track every parcel across five stages, manage pricing, handle customer records, and monitor the operation at a glance.
Operation
Dashboard
Customer experience - from phone calls to self-serve
Solution for manual Communication of fee inquiry
No more calling just to get a price.
Two tabs, because not all parcels are the same.
Parcels come in all shapes so I separated the flow into two tabs: same size/weight, and different sizes/weights. This small split lets customers navigate directly to what applies to them, without reading through irrelevant options.
B. One control, any quantity.
Rather than forcing customers to create a new entry for every parcel, a simple quantity control lets them adjust the count in one place, keeping the experience fast and frustration-free.
At the end of the flow, two buttons reflect two real customer intentions.
There are two buttons: "I am ok with the price and want to send my parcels": confirm and proceed with pickup, or "I will send later": save the details for later. No guessing which button does what.
Every inquiry and delivery are visible in one place.
Instead of calling to follow up, customers can review every price inquiry they've submitted and check the current status of any active delivery without contacting anyone.
solutions for manual Phone call order tracking
From phone calls to real-time visibility.
Before this system existed, tracking a parcel meant calling staff and hoping someone could find the record. Now customers enter an order number and see the full journey, including which driver handled pickup and delivery.
Additon of driver name changed dispute resolution.
Adding a driver name to the tracking view wasn't a UI preference. It was a direct response to a real operational problem: lost parcel complaints that took hours to investigate because no one could confirm who handled the delivery.
Driver experience - designed for the field, not the office
solutions for Duplicate parcel taken
One scan replaces a long scroll.
Drivers were updating parcel statuses by scrolling through long lists to find the right customer, which caused slow, error-prone, and frustrating when they're working fast in the field. Barcode scanning changed that: one scan, instant update, no searching required.
Phone-first, no app install needed.
Since a native app was planned for a later phase, I designed the driver surface as a mobile-optimized web interface. Drivers got a full phone-first experience from day one and no install required.
Four delivery states, each one tells a driver exactly what to do next.
Spot what's done at a glance.
Completed deliveries are highlighted in green with a primary action button, so drivers can scan the list at a glance and immediately spot what's done versus what still needs attention.
Know the payment before knocking.
Payment status is color-coded: green for prepaid, red for cash on delivery, so drivers know what to expect at the door before they even knock.
Proof of delivery are captured at the door, not recalled from memory.
When a driver completes a delivery, they log recipient details, pickup type, and payment status on the spot before leaving. Color cues confirm payment type at a glance. For behalf pickups, every extra detail captured here is what makes a dispute resolvable later, without chasing anyone for information.
Multiple parcels, same customer, nothing gets lost in the count.
When a customer receives multiple deliveries over time, a Delivery Attempt No. ties each one together, showing how many parcels arrived, how many attempts it took, and exactly which driver was responsible each time. It turns a potential source of confusion into a clear, auditable record.
Operations & Dashboard
Simplify internal operations
Behind every smooth customer interaction is an operations team managing it in real time.
Beyond individual workflows, operations staff had no way to see the business as a whole. How many parcels were in transit? Which stage had the most delays? These questions were answered by asking someone, not by looking somewhere. The operations side was designed to make the entire pipeline legible at a glance.
solutions for Relying on Different Messaging Apps
Customer records, searchable in seconds.
Paper records were replaced with a centralized digital database. Customer information is now secure and retrievable in seconds without being needed to flip through a folder or ask a colleague.
solutions for Inquiring correct fees
Pricing stays flexible to keep accuracy.
Since parcel pricing depends on chargeable weight (a mix of size and weight), I designed a pricing tool that lets staff manually adjust rates and select the correct tier, keeping accuracy in human hands where it belongs.
solutions for A bunch of Excel Files
Five stages, automatic updates, no missed entries.
Manual Excel updates were replaced with a structured five-stage pipeline: Arrive at China Warehouse → Airport Transit → Arrive at YGN Warehouse → Out for Delivery → Delivered. Each stage updates automatically based on staff role, removing the chance for entries to be missed or mislabeled.
Batch cards keep airport transit manageable.
Airport transit handles multiple batches daily. I used batch-based cards so staff can quickly access parcel details without scrolling through a growing list.
solutions for Trace of parcel Receiver
Delivery records are stored per customer, not on driver's phones.
Every delivery photo, recipient detail, payment status, and attempt number is stored per customer, not buried in a driver's phone. Operations staff can investigate any complaint without chasing anyone. The record is already inside the system.
What We Couldn't Fully Solve
Automated pricing hit a wall that reality built.
Automating fee calculation was the one problem we couldn't crack cleanly. Pricing depends on chargeable weight, a calculation that combines both parcel size and actual weight, and real-world variation made every automated approach fall apart.
Four attempts, four dead ends.
We tried four approaches.
Fixed size-based rates fell apart when actual dimensions didn't match categories.
Customer-input dimensions were unreliable, people guessed, and they guessed wrong.
Tiered pricing (small/medium/large) was too blunt for edge cases.
And simplifying to weight-only or size-only conflicted with how logistics pricing actually works.
For now, manual adjustment by staff is the most reliable path, not ideal but honest.
A staff member adjusting the price manually is still the way it works today. It's not the answer we wanted, but it's the honest one. And every approach we ruled out is documented, so when the business is ready to try again, there's a starting point already waiting.
Business Value
Four outcomes that change how teams wrok.
Self-serve pricing and tracking
For Customers
Customers can check prices and track their parcels on their own. No phone call needed on either side.
The whole operation in one view
For Operation Staffs
The team can see what's moving, what's delayed, and what needs attention without asking anyone.
Every delivery, fully documented
For Operation Staffs
Every delivery is logged with a photo, driver name, and payment status. Any complaint can be checked in seconds instead of investigated for hours.
No more manual stage updates
For Operation Staffs
For Drivers
Parcel stages update automatically as staff work through them. Nothing gets missed, nothing gets entered twice.
Takeaways
What I've learned
Designing for three different users on three different surfaces forced me to think in systems, not screens. Every decision I made for the customer side had implications for the driver and operations sides. I couldn't get one right without thinking about the others.
What I'd do differently
I tested the driver screens in an office, not in the field. Real drivers are working fast, often outdoors, sometimes with one hand. That context changes what works and what doesn't. Next time, I'd go out with drivers before finalising anything on their side.
What comes next
Pricing is still the unsolved problem. As the business grows, the time staff spend manually adjusting rates will start to slow things down again. The four approaches we tried and ruled out aren't dead ends. They're a documented head start for whoever tackles the pricing engine next.
Say hello!
I love discussing product ideas from different perspectives.