Error states
Errors are information, not judgment. They name what went wrong, say what the user can do, and never blame the user for something the system did.
Inline field error#
That doesn't look like a valid email address. Try name@domain.com.
Request failed — connection#
We couldn't reach the search index
Likely a brief network hiccup. If this keeps happening, please let us know.
500 — something broke on our end#
That's on us
Something broke loading this page. We've recorded it and are looking into it. In the meantime, try reloading or head back to the directory.
Rules#
- Name the error. “We couldn't reach the search index” beats “An error occurred.”
- Own our failures. If it's our fault, say so. “That's on us.” Users appreciate honesty over vague third-person passives.
- Never trap the user. Every error offers at least one way out — retry, go home, report.
- Use tone to signal severity. Warn tone (amber) for recoverable; error tone (red) for user action or system fault.
- Don't make the user feel stupid for typos. Field errors are corrections, not accusations.