Unit 1 · Lesson 4 of 20
Earn trust through clear promises
Explain what the clinic asks, what it knows, and what happens next.
01 / Learn
Learn the method
Fictional case
The kiosk asks Mira for her appointment code and surname before showing her appointment details.
Terms for this lesson
- Purpose
- The service reason for requesting a particular piece of information.
- Consequence
- What happens to the person or service after an action.
- Reversibility
- The extent to which an action can be corrected after it occurs.
Trust grows when a service makes promises that match its behavior. Mira needs to know why the kiosk asks for information, how her arrival reaches the clinic, and which step follows. The clinic can answer these questions with concise copy tied to real system events.
Collecting information has a consequence. A shared kiosk may show a name or appointment time to people nearby. The design should ask for the smallest useful identification input, show sensitive details with care, and clear the screen after the task. A visible staff-help route lets Mira resolve a mismatch through a person with appropriate access.
The stakes of an action determine the amount of review it deserves. Entering an appointment code can use a simple correction path. Confirming the wrong appointment deserves a clearer review of date, time, and patient identity. The confirmation message should mark the accepted arrival and describe where Mira should wait.
Review trust at three moments: before Mira shares information, before she confirms the appointment, and after the service responds. At each moment, ask what Mira can see, what the system has established, and what control she has over the next action.
Use the method
- Explain the purpose of each requested detail.
- Show decision-critical information before confirmation.
- Tie the final message and privacy reset to actual service events.
Trustworthy copy is grounded in purpose, accurate service status, privacy, and a usable correction route.
- U.S. Web Design System: Establish trust ↗Explain why sensitive information is requested, what is needed, and what happens to it.
- Nielsen Norman Group: 10 Usability Heuristics for User Interface Design ↗System status, error prevention, and recovery as checks rather than recipes.
- GOV.UK Service Manual: Designing good government services: an introduction ↗Consider a service from beginning to end, front to back, and across channels.
02 / See the reasoning
Worked example
The current kiosk asks for an appointment code and surname under a heading that says 'Verify.' The team rewrites the introduction to explain that the details find Mira's appointment. Before submission, the kiosk shows the appointment time and a way to correct the entry. After a receipt arrives, it shows where to wait and clears the shared screen after a brief interval. Reception remains available for a mismatch.
Try a decision →03 / Decide
Guided decision
The kiosk finds an appointment whose time differs from Mira's reminder. Which first response helps her make an informed choice?
Feedback on your choice
What could change the answer: A clinic with a reliable self-service rescheduling route can add that option beside reception help.
Use this feedback to examine your choice and written reasoning.
Build your case file →04 / Build the case
Your case file
Fictional case update
A patient finishes check-in at a shared kiosk while another person waits behind them.
Evidence and constraints
- Fictional service detail: a receipt means the clinic appointment service accepted the arrival.
- Fictional setting: the kiosk is shared and stands beside the waiting line.
- Fictional operations detail: reception can investigate appointment mismatches.
Write the final confirmation and screen-clear sequence. Show the accepted service event, next step, and privacy treatment.
Create: A three-moment trust review and an annotated confirmation screen.
The design explains purpose, displays a verified status, supports correction, and protects the shared screen.
- Each requested detail has a clear purpose.
- The final claim follows the service receipt.
- The sequence includes a correction and privacy route.
The team has a theory about a trustworthy check-in. The diagnosis unit gathers evidence from real task behavior.
Unit complete
You completed understand experience quality.
You finished this unit's four case-file tasks. The next unit builds on the evidence and decisions you made here.
05 / Keep working