Error Messages That Actually Help Users

A design system is a set of decisions you no longer have to argue about. Type scale decisions ripple into every component downstream. We tested with five people and found the same problem four times.

A small example

We removed three options and support tickets dropped by a third. Whitespace is not empty; it is doing the grouping for you. Users scan, so headings carry more weight than paragraphs.

An error message should blame the system, not the person. Whitespace is not empty; it is doing the grouping for you.

Trade-offs

An error message should blame the system, not the person. Motion should explain a change, not decorate it. Users scan, so headings carry more weight than paragraphs. Whitespace is not empty; it is doing the grouping for you.

• Test with real data
• Check contrast early
• Start from content, not components
• Prefer one clear action per screen

Type scale decisions ripple into every component downstream. We tested with five people and found the same problem four times.

Getting started

Users scan, so headings carry more weight than paragraphs. Motion should explain a change, not decorate it. A design system is a set of decisions you no longer have to argue about. Type scale decisions ripple into every component downstream.

Users scan, so headings carry more weight than paragraphs. We removed three options and support tickets dropped by a third.

We tested with five people and found the same problem four times. Motion should explain a change, not decorate it.