Unit 1 · Lesson 1 of 20
What counts as an experience?
Map a person's task across interfaces, people, and time.
01 / Learn
The idea
An interface is only one part of an experience. The visitor's goal is to arrive, be recognized by the clinic, and know what to do next. The kiosk, appointment record, staff handoff, waiting area, and eventual call all affect whether that goal succeeds. A screen can be easy to operate while the overall service remains uncertain.
Start a UX review by naming the person, their goal, the setting, and what happens before and after the visible interaction. Trace each handoff: what information moves, who relies on it, and how the person learns that progress occurred. Include another channel when the primary one is unavailable. This makes it possible to locate a problem in the service rather than treating every problem as a screen-layout issue.
A polished check-in screen proves that check-in is complete. The visitor needs evidence that the clinic received the action and a clear next step.
02 / See the reasoning
Worked example
Fictional scenario
A visitor checks in at a clinic kiosk and waits to be called.
An expert reviewing a kiosk that says 'Checked in. Please wait near reception' would ask what event triggers that message. If it appears before the staff system acknowledges receipt, the words may create false confidence. The expert maps kiosk submission, staff receipt, and visitor confirmation as separate moments before recommending a change.
Try a decision →03 / Decide
Guided decision
The kiosk can receive a staff-system acknowledgment, but has no printer. Which first change would you test? Choose one and explain what you would verify.
Feedback on your choice
What could change the answer: If the staff system cannot give a reliable acknowledgment, use a clearly provisional status and an alternative confirmation route instead of claiming completion.
This feedback helps you examine the decision; it does not grade your written reasoning.
Apply it somewhere new →04 / Apply elsewhere
Independent application
Fictional scenario
A warehouse handheld scanner saves a stock count locally, then synchronizes when connectivity returns.
Map the worker's full task from scanning to a confirmed inventory update. Distinguish local capture from remote sync and identify who needs to know when either step fails.
Make: A one-page task and handoff map with an annotated confirmation and recovery sequence.
The map connects an interface detail to the worker's actual outcome, includes the offline state, and does not claim remote success from local capture.
Lesson complete
You applied the method in a new context.
You studied the idea, tested a decision, and made an artifact for a new context. Keep the reasoning for your next UX question.
05 / Keep working