Journey Map

Unexpected Skip

Arriving on Time, Skipped Anyway

Booking a clinic appointment should reduce uncertainty. You pick a number, you calculate your time, you show up.
Krystal did all of that. She called the day before, received ticket no. 11, and arrived ten minutes before her expected turn. Eight of the ten patients ahead of her were no-shows. The queue moved without her.
This scenario caught my attention because the failure is invisible from the outside. The clinic ran on schedule. The queue moved efficiently. Only Krystal knew something had gone wrong.

WHERE THE SYSTEM GOES QUIET

This map traces what happens between booking and being seen, and where the system stops communicating with the patient.
No-shows happen, and skipping past them is a reasonable way to keep a queue moving.
The map shows two things. The queue jumps ahead without alerting anyone on their way, and the rule waiting at the front desk was written for latecomers. Krystal arrived on time and still served the penalty, waiting for two more patients before she was seen.

The queue updates. The machine updates. The patient does not.

THE GAP

One notification. One line of text sent when the queue accelerates. That is the distance between a frustrating experience and a functional one.
What I did not expect was how much of the emotional weight sits in that gap. Krystal left without complaining, having quietly absorbed something that was not her fault. A service like this runs on time and still feels slightly unfair, every time.
And because that unfairness is dispersed, it stays unaddressed. Each patient absorbs the friction alone, and nothing adds the skips up, so no collective voice ever forms. The clinic, meanwhile, is untouched. It runs on schedule, with no financial or operational reason to fix a problem no one is formally raising. The system survives by quietly passing its flaws on to the people using it.