Skip to content
Kayla Jung
← All cases
Case · 02 of 07
Cover·2022–2023 · B2B · AI · Enterprise

Dispatch & tracking for non-emergency medical transport

Bambi
Role
End-to-end designer + design system founder
Collab
Founders, Engineers, Stakeholders, NEMT dispatchers
Tools
Figma, Storybook, Miro, Slack, Zoom
Year
2022–2023
Chapter · 01

Triage by text

Before Bambi, NEMT dispatch ran on phone calls and spreadsheets. A team coordinating dozens of patient rides — dialysis, chemo, post-op pickups — would juggle three text threads, a paper schedule, and a separate billing tool. When a driver called out at 7am, it was triage by text. When a patient called to reschedule, the change might get written down. Or might not.

No one had a screen that showed the full day. So I designed one.

One screen for the whole day
The Bambi dispatcher dashboard

Drivers, patient rides, schedule changes, alerts — one live view. The first time a dispatcher could see the entire day at once instead of reconstructing it from three text threads.

Chapter · 02

One screen, the whole day

How do you give a dispatcher one screen that holds the entire day — drivers, patients, changes — without burying them in it?

The founders gave me end-to-end ownership: discovery, research, the dispatcher dashboard itself, and the design system foundation that would carry every screen after.

Chapter · 03

What I designed

  1. One screen for the whole day. Drivers, patient rides, schedule changes, alerts — surfaced in a single live dashboard. Sortable, filterable, never more than two clicks from a reschedule.
  2. The first design system Bambi ever had. Built in Storybook so engineers could ship the dispatcher view first and grow from there.
  3. AI that handles the boring parts. So humans handle the people.
The tension

A dispatcher is always mid-something. Every new ride or change is an interruption — so how do you let them edit without losing the day they're watching?

What I did

The rule I held was simple: never leave the dashboard.

A new ride or a change comes in as a slide-over, not a new page — so the live day behind it never disappears while the dispatcher fills in the details. And the most frequent moves — assign, reassign, flag, cancel — live at the row, on the dashboard itself, instead of behind a settings screen.

The day stays on screen. The edit happens on top of it.

The add-a-ride slide-over panel
Two clicks to a rescheduleA new ride or a change comes in as a slide-over, not a new page — so the day behind it never disappears while the dispatcher fills in the details.
The small moves, where the work is
Quick-action menu on a ride row
Row-level action dropdown

Assign, reassign, flag, cancel — at the row, on the dashboard. The most frequent actions never cost a trip to a settings screen.

Chapter · 04

What changed

  • 34% more efficient. Clients reported their dispatchers got through more work in less time after rollout.
  • Onboarding stopped being a Tuesday-long ordeal. New hires could read the dashboard on day one.
  • Fewer dropped calls. Fewer missed pickups. Real outcomes for patients waiting at curbs.
The receipts
+0%
dispatcher work efficiency (client-reported)
Credits
Client Bambi (NEMT operations platform)
Services Discovery, User research, UX strategy, Wireframing, Prototyping, Component creation, Design system foundation
Year 2022–2023