My learning 0 of 20 lessons complete
Start lesson 1 →

Unit 1 · Lesson 2 of 20

Make each action understandable

Connect an action cue, system state, and feedback in the check-in flow.

Ready to learnLearn the method, study the case, make a decision, and build your case file.
YOUR LEARNING PATH
02 / 20

01 / Learn

Learn the method

Fictional case

Mira enters her appointment code and sees a button labeled Check in. The next screen currently says Done.

Terms for this lesson

Action cue
A label or visual clue that helps a person identify an available action.
System state
The condition the service has reached at a specific moment.
Feedback
Information that shows the result or progress of an action.

An interaction becomes understandable when a person can see an available action, predict its result, and recognize what happened. A button label helps Mira predict that pressing Check in will tell the clinic she has arrived. The message after pressing it should describe the service event that actually occurred.

A system state is the condition the service is currently in. For this task, useful states include ready for input, sending the request, receipt confirmed, and request delayed. Feedback makes the current state visible to Mira. A brief progress message can cover the sending interval; a receipt message can mark the accepted request.

People form a mental model from the words, controls, and responses they encounter. Mira may interpret Done as confirmation that staff can see her arrival. The team can check that interpretation by asking her what she expects to happen next and observing whether she seeks additional confirmation.

Design the message and the underlying state together. A receipt-backed message can say 'The clinic has received your check-in. Please wait near reception.' A delayed request can show its current status and a staff-help route. This pairing gives Mira a dependable explanation of her progress.

Use the method

  1. List the states between code entry and accepted arrival.
  2. Connect each visible message to the event that creates its state.
  3. Ask a patient to explain the status and next action in their own words.
Key distinction

A clear status message names the event the service has reached and gives the person a usable next step.

Read alongside this lesson
See the idea in action →

02 / See the reasoning

Worked example

The team traces the current flow. Pressing Check in starts a request; Done appears before the appointment service replies. They move the confirmation to the receipt event and add a sending state for the interval. They then show the revised flow to Mira and ask what she believes the clinic knows at each screen. Her explanation reveals whether the labels support an accurate mental model.

Try a decision →

03 / Decide

Guided decision

The service reply takes several seconds. Which sequence gives Mira the clearest account of progress?

Choose the option you would try first

04 / Build the case

Your case file

Fictional case update

The kiosk receives a receipt while the reception queue still shows an older view.

Evidence and constraints

  • Fictional system detail: the appointment service issues a receipt after accepting the request.
  • Fictional operations detail: the staff queue refreshes every 90 seconds.
  • Fictional observation: Mira asks reception whether her check-in went through after seeing Done.

Write the kiosk message for the receipt state and a short explanation a receptionist can use during the queue delay.

Create: An annotated sequence for ready, sending, received, and delayed states, with exact status language.

Review your work against these criteria

Each message corresponds to a named state, and Mira can identify what action belongs next.

  • The action label predicts its result.
  • The receipt message follows the receipt event.
  • The delayed state provides a specific route to help.
Where this leads

A clear status helps Mira understand the service. The next lesson checks who can perceive and use that status.

05 / Keep working

Related patterns

Apply this skill: UX critique and problem statement →

Saved items