Article 04 · UX Principles
Buttons Should Say What Happens Next
Why explicit actions are more usable than “Yes” and “No.”
Core principle
Favor recognition over recall and make consequences visible.
Users should not have to remember the question in a modal to understand what each button will do.
The hidden cost of generic labels
Buttons labeled “Yes,” “No,” “OK,” or “Continue” often answer a sentence rather than describe an action. Once the dialog disappears, users may not remember what they selected or what the system did.
Use verbs that describe outcomes
Replace abstract responses with direct actions such as “Discard Changes,” “Keep Editing,” “Submit Without Feedback,” or “Add Feedback.” The user can understand each option without rereading the message.
Hierarchy supports faster decisions
Primary and secondary actions should not compete with equal visual weight. The interface should make the recommended or most likely action easy to find while keeping alternatives visible and safe.
Sequence matters
For left-to-right reading contexts, actions should support a natural scan path. Placement should be consistent across the product so users can build a reliable mental model. Consistency is especially important because once a pattern is learned, changing it adds cognitive effort.
Make targets easy to reach
Buttons should also be large enough for touch, visually distinct in all states, keyboard accessible, and separated enough to reduce accidental activation. Accessibility is not an enhancement added later; it is part of interaction quality.
A button should explain the consequence — not merely answer the question.
Design takeaways
- Use action verbs instead of Yes/No labels.
- Create clear visual distinction between primary and secondary actions.
- Keep action order consistent across the product.
- Design touch targets and focus states for real human use.
Categories: UX Principles · Design Leadership · Human-Centered Design