Back to projects
Shipped2021Web

Delivery Management System

Real-time delivery tracking and dispatch with route optimization.

Private — case study only

Period

2021

My role

Full-Stack Developer

Team

3 engineers

The Problem

Why this needed to exist.

A regional logistics operator was assigning deliveries via phone calls and tracking them on a whiteboard. Customers had no visibility, and dispatchers were re-routing drivers manually all day.

The Approach

How I solved it.

Built a MERN dispatch console plus a driver-facing mobile view. Integrated routing APIs for daily route optimization and exposed a customer tracking page powered by live driver location.

Personas

Who I designed for.

Each persona shaped a specific surface of the product. Goals and pain points were validated through interviews and shadowing.

DP

Tanvir

Dispatcher

Goals

  • Assign deliveries to the right driver fast
  • React to delays without phone calls
  • Hit daily SLA targets

Pain Points

  • Whiteboard breaks down at scale
  • No live visibility once a driver leaves
  • Manual reshuffling for every delay
DR

Asif

Delivery Driver

Goals

  • Get a clear list of stops with directions
  • Mark delivered or failed in one tap
  • Avoid back-and-forth calls

Pain Points

  • Paper run-sheets get lost
  • Phone tag with dispatcher
  • No record of failed-attempt reasons

Use Cases

Key user flows.

The most critical scenarios the product is designed to make effortless.

01

Dispatcher

Plan and dispatch the daily route

  1. 1Import the day's orders
  2. 2Cluster by zone and assign drivers
  3. 3Run optimizer; review proposed sequence
  4. 4Push manifests to driver devices
02

Driver

Complete a delivery

  1. 1Open next stop with turn-by-turn link
  2. 2Capture proof of delivery (signature/photo)
  3. 3Mark delivered or failed with reason
  4. 4Auto-advance to next stop

UX Process

How I got from problem to product.

The end-to-end design process — from research to ship.

  1. 01

    Field Shadowing

    Rode along with two drivers and a dispatcher for two days to surface real friction.

  2. 02

    Critical Path Design

    Optimized for the dispatcher's busiest hour and the driver's one-handed phone use.

  3. 03

    Pilot & Iterate

    Two-week pilot with one fleet; shipped fixes daily until adoption stabilized.

Roadmap

What shipped — and what's next.

Phased rollout, with each phase validating learnings from the last.

  1. Phase 1 — Dispatch console MVP

    Shipped

    Q1 2021

    • Order import + assignment
    • Driver list and roles
    • Basic status tracking

  2. Phase 2 — Route optimization

    Shipped

    Q2 2021

    • Daily optimization runs
    • Live driver location
    • ETA updates to customer page

  3. Phase 3 — Customer experience

    Shipped

    Q3 2021

    • Public tracking page
    • SMS notifications on key events
    • Failed-delivery reason capture

Tech Stack

Built with.

MongoDBExpress.jsReactNode.js

Engineering Challenges

Hard problems worth solving.

  • Battery-friendly background location on Android variants
  • Graceful degradation in low-signal delivery zones
  • Optimizer cost vs. quality on tight SLAs

Outcomes

The numbers that matter.

30%

Drop in support calls after launch

2x

Deliveries handled per dispatcher per day

Live

Visibility from pickup to drop-off

Previous case studyGarment ERP SystemNext case studyFlight Booking System