Consistency is kind, but clarity wins when the two disagree. An error message should blame the system, not the person. We tested with five people and found the same problem four times.
A small example
The prototype answered in a day what the meeting could not in a month. Labels above fields beat clever placeholders every time. An error message should blame the system, not the person. Users scan, so headings carry more weight than paragraphs.
Labels above fields beat clever placeholders every time. An error message should blame the system, not the person.
Getting started
Whitespace is not empty; it is doing the grouping for you. Good defaults are the design most users will ever see. Type scale decisions ripple into every component downstream. An error message should blame the system, not the person.
- Check contrast early
- Design the empty and error states
- Prefer one clear action per screen
- Start from content, not components
We tested with five people and found the same problem four times. We removed three options and support tickets dropped by a third.
Context
Type scale decisions ripple into every component downstream. We removed three options and support tickets dropped by a third. An error message should blame the system, not the person. Consistency is kind, but clarity wins when the two disagree.
Contrast is not a style choice; it is whether people can read the page.
We tested with five people and found the same problem four times. Good defaults are the design most users will ever see.
Consistency is kind, but clarity wins when the two disagree. We tested with five people and found the same problem four times.
Leave a Reply