The patient's stated priority, not the team's assumption
5 min read
Lesson objectives
- Map a patient's stated priorities to observable touchpoints, separate patient needs from staff assumptions, and identify an access barrier without making a clinical decision.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
The patient's stated priority, not the team's assumption
A service journey is a sequence of touchpoints visible to a patient: seeking an appointment, arriving, registering, receiving an explanation, leaving, and following up. Backstage work may be invisible, such as transmitting a referral or sending a result. A useful map records the patient's action, question or need at that moment, the team's action, and an observable point where the handoff could fail. Keep an event separate from an explanation of its cause. “The appointment message did not reach me” is a reported event; “the system is broken” is a hypothesis requiring a check. A journey map is not an organization chart. Its purpose is to show what the person must do to move from one stage to another and where effort or uncertainty appears.
Ask the person about priorities instead of inferring them from age, language or disability. A wheelchair user might prioritize knowing an accessible entrance, but the immediate concern might instead be privacy at registration. Both are plausible and neither should be recorded as fact without asking. On the map, label “the patient stated,” “we observed,” and “we assume” separately. This lets the service team test a small change rather than commit to a large solution built on a stereotype. A different contact channel or accessible format may help, but first establish the person's preference and follow the organization's rules for sharing their information. Do not turn an accommodation question into an unsolicited clinical assessment.
Set an observable criterion for each touchpoint instead of writing that it should feel “smooth.” Did usable location information arrive before the visit? Does the person know where to ask a question after leaving? Was an answer actually received? Distinguish a process record from a reported experience. A valid send log may establish that a message was sent, but it does not show that it was read or usable. A patient who reports reaching the wrong building despite the message provides evidence of a possible comprehension or access gap. Review both records and accounts before choosing a change. This example does not establish a real city's access conditions or local practice.
Lesson summary
Map needs at service touchpoints, separating stated priorities from staff assumptions. Select a small access test grounded in observable evidence.