A quiet observation: in high-stakes work, people don’t have time to translate.
Concept of the week — Predictability lives in the words
Words are part of the interface map: if labels don’t match users’ language, users pay for translation, incur extra confirmation steps, and avoidable errors occur. Under pressure, “close enough” terms increase the verification burden because users must infer intent rather than execute.
So we… name actions in the user’s terms, prefer standard vocabulary where available, and test comprehension before we ship.
Before the change, a patient monitor’s alarm control was labeled “Silence”—a legacy term that suggests “make it go away,” not “I saw this and took responsibility for it.” In an intensive care unit (ICU), that mismatch can trigger extra scanning and second-guessing: did I mute the sound, or did I actually acknowledge the alarm condition?
We proposed relabeling to “Acknowledge” and treated the wording as part of the safety interface—not copy polish. In this system, Acknowledge stops the audible alarm and marks the alarm as seen; it does not resolve the underlying condition or clear the alarm source.
We tested the new label with many nurses to check comprehension and fit with their mental model: what they believed the action meant in the workflow and in terms of responsibility.
The result was clear: “Acknowledge” matched nurses’ language better and aligned with the alarm-system standard (International Electrotechnical Commission [IEC] 60601-1-8). That combination—mental-model fit plus standards compliance—gave us the confidence to ship. Post-release feedback backed the change: fewer “what does this do?” moments and less re-checking during busy stretches.
In software and information technology (IT) consoles, the same failure mode occurs when “Mute,” “Dismiss,” “Acknowledge,” and “Resolve” are used interchangeably, leading to manual lookups and costly errors during incidents.
One thing to remember: Every ambiguous command label multiplies training material, localization, support scripts, and quality assurance (QA) and regression-test effort—because nobody can reliably predict what users think it means.
How teams ship this: Treat labels like an application programming interface (API): keep a versioned glossary for critical actions, and require a “term diff” note (what changed, why, who it impacts) for any rename.
Asset
Asset: The Action Label Checklist
A fast, repeatable way to validate that a command name matches user intent, system state change, and standards language (when applicable).
Action clarity: If a user reads only the label, can they predict the one action taken?
Mental model test: Ask 5–10 target users: “What will happen if you press this?” Capture first answers.
Confusables: List nearby terms users might confuse it with (e.g., Mute/Dismiss/Resolve). Ensure boundaries are explicit.
Standard language: If a domain standard exists (e.g., International Electrotechnical Commission [IEC] 60601-1-8), prefer its vocabulary unless there’s a proven comprehension gap.
Localization check (will it translate cleanly?)
Change control (publish a short “term diff” note: old → new, why, where users will see it).
Resource: Strategic Writing for UX by Torrey Podmajersky
Practical guide to treating user experience (UX) text as product work—aligning words to user and business goals, defining a consistent voice, applying proven UI text patterns (buttons, labels, errors, notifications), and measuring whether the language actually helps people complete actions.
Light wisdom & reflection
“Content precedes design. Design in the absence of content is not design, it’s decoration.”
Where in your product are you relying on “nice” labels to mask unclear actions—and what would users do differently if every control had to earn its meaning through the words alone?
Mindful practice
Pick one message you’ll send today (email, text, …) where you’re asking someone to do something.
Which verb in your message could be misread (e.g., “handle,” “fix,” “take care of,” “sync”)?
What would you rename that verb to so the action and outcome are unmistakable (and easy to confirm)?
Notice how often clarity is just one better verb away.
Best,
Andreas Walden
Share this with someone designing for clarity.