Patient journey & engagement
Mapping care as the patient experiences it, not as the org chart draws it — and why 'engagement' is usually a metric about our convenience wearing the patient's name.
In one line
A patient journey map describes care as the patient actually experiences it — including the waiting, the confusion, and the four times they explained the same thing. Almost every health system designs around its own departments instead, and then wonders why patients are unhappy.
The org chart is not the journey
Draw how a hospital sees a hip replacement: referral → outpatient → pre-op assessment → theatre → ward → discharge → physio. Tidy boxes, each owned by a department, each with its own system.
Now draw what the patient experienced:
Waited eleven weeks not knowing if anything was happening. Told my history to five different people because none of their systems talk. Got a letter in language I didn't understand. Nobody mentioned I'd need someone at home for two weeks — found out the day before. Discharged at 9pm with a leaflet. Rang the number on it; nobody answered.
Same care. Both true. The first is what we measure and manage; the second is what determines whether the operation worked, because whether she does her exercises and takes her anticoagulant is decided in the second story.
The gaps between departments are invisible on the org chart and are the entire experience for the patient. That's the value of journey mapping: it makes the handoffs — the places nobody owns — visible.
What journey mapping actually surfaces
- Waits nobody owns. The eleven weeks weren't anyone's KPI. Every department hit its target.
- Repetition. Re-telling a history five times is an interoperability failure the patient experiences as indifference.
- Anxiety as an outcome. Not knowing what happens next is a harm. We don't measure it, so it isn't real to us.
- The moments that decide everything. For most conditions, the decisive moments are at home, not in the building — and we have no visibility of them at all.
"Engagement" — say what you mean
Here's the uncomfortable one. When a health system says "we need to improve patient engagement", it very often means: we need patients to do what we want. Take the medication. Attend the appointment. Use the portal. Stop calling.
Those aren't bad goals. But naming them "engagement" launders an institutional interest into something that sounds patient-centred, and it produces a specific failure: we measure our own convenience and call it their experience.
Look at the standard engagement metrics — portal logins, app opens, message response rates. Every one of them measures effort the patient spent on our system. A patient who never logs in because their care is going fine scores zero. A patient logging in daily out of anxiety scores brilliantly.
The honest version of engagement is much narrower: does this person have what they need to participate in decisions about their own body? That's it. Sometimes that means an app. Often it means a phone call from someone who has time.
Non-attendance, reframed
The classic tell. Health systems call it "DNA — did not attend" and treat it as the patient's failure. Journey mapping reliably shows otherwise: the appointment was at 10am on a Tuesday, the patient is a daily-wage worker, the letter arrived late, the bus is ninety minutes, and nobody asked.
They didn't fail to attend. We failed to offer something attendable. Renaming it "was not brought" for children was a real change in a real health system, and it changed what people did about it — which tells you the label was doing work all along.
Where design decides
- Waiting is a design surface. "Your referral was received; typical wait 8–10 weeks" costs almost nothing and removes a large share of the distress.
- Discharge is the highest-risk moment and usually the worst-designed. Most readmission prevention is discharge communication, not medicine.
- Scan & Share is patient-journey design, whatever else you call it — it removed the queue, which was the patient's actual complaint. Nobody in that line was asking for interoperability.
The discipline: watch the journey, not the chart. And when you say engagement, be honest about who is being engaged, and for whose benefit.