Writing · Free lesson
UX handoff: name the trigger and state
“Update the button” leaves the engineer guessing. A useful handoff names the event and the text or state that follows it.
Professor Scott MendozaThe short answer
Use “When [event], [visible response].” For this fictional design: “When the user selects Save, show Saving. When the save succeeds, show Saved.” Starting an action is not the same as completing it successfully.
One event, one stated response.
In a repeatable interface rule, when introduces the event and the next clause gives the response. Use present verbs: the user selects, the save succeeds. Name the actor when it matters. Preserve the exact label the team agreed on. A selection can start saving without proving that saving has succeeded; write these as separate conditions.
Compare the examples
When the user selects Save, show Saving.
When the save succeeds, show Saved.
Show the message below the Save button.
These are supplied design decisions for the exercise, not universal rules for every save button.
Build the meaning step by step
Actor and event
When the user selects Save
Visible response
show Saving.
Separate success
When the save succeeds, show Saved.
Try it now
Match the event to the state
Read all answers and explanations
The user has selected Save, but saving has not finished. Which supplied state fits?
SavingThe supplied start state is Saving; success has not yet occurred.
What triggers Saved in this exercise?
The save succeeds.The specified trigger is successful saving, not merely visiting or pointing.
Which note names both the event and visible response?
When the save succeeds, show Saved.The when clause names the event, and show Saved names the response.
Put it into practice
Repair the handoff note
Keep these supplied decisions: selecting Save shows Saving; successful completion shows Saved. Choose the accurate handoff.
When the user selects Save, show Saved immediately.
See a model answer
When the user selects Save, show Saving. When the save succeeds, show Saved.
The edit preserves the design brief instead of inventing behavior.
A little more clarity
Common questions
A few useful details before you move on.
Can if also be used?
Yes, if can introduce a condition. When is useful here for a repeatable event-to-response rule; it is not the only grammatical option.
If the save succeeds, show Saved.
Should I rewrite the button labels?
Use the labels supplied by the design brief. The exercise is about clear handoff language, not choosing new interface copy.
Keep the agreed labels: Save, Saving, and Saved.
Take it into your day
Link the exact trigger to the exact visible response.
English for Careers · Coming Soon
Communicate design decisions in English.
English for UX Designers: Career Simulation is coming soon. The planned course follows connected UX work, including handoff communication. Sign up on the course page for its launch news.
Get launch updatesUX Designers · Career Simulation
Your next step · Available on Udemy
Strengthen your English foundations.
The available English Grammar and English Speaking Master Course develops broader grammar, sentence-building and communication foundations. Sentence structure helps you make conditions and results clear.
Explore the course English Master Course: English Grammar and English Speaking