Clarity first: plain language rules

Clarity beats everything else in interface writing. If a sentence is clever but unclear, it fails. Plain language is not about dumbing things down. It is about removing effort so people can focus on their task.

Seven rules to start with

1. Use common words. Write "use" rather than "utilise" and "start" rather than "initiate".
2. Put the most important words first. "Delete project" is easier to scan than "Click here if you want to delete this project".
3. Use active voice. "We sent you an email" is clearer than "An email has been sent".
4. Address the reader as you. It feels direct and makes instructions easy to follow.
5. One idea per sentence. Split long sentences joined by "and" or "which".
6. Be specific. "Saved 2 minutes ago" is more useful than "Recently saved".
7. Cut words that do not add meaning. "In order to" becomes "to", and "please note that" can usually go.

Remove jargon

Teams invent internal names for features, and those names leak into the interface. If your team calls a saved filter a "lens", users may not. Use the words your users use. Support tickets, search logs and interviews are good places to find them.

Technical terms are fine when your audience genuinely uses them. A database tool for engineers can say "schema". A budgeting app for families should not say "transaction reconciliation".

A quick test

Read your text aloud. If you would not say it to a person sitting next to you, rewrite it. Then try cutting it by a third. Here is an example from our app:

• Before: "In order to proceed with the creation of your new project, it is necessary to provide a name."
• After: "Give your project a name."

The second version is four words instead of nineteen, and it says the same thing.

Consistency is part of clarity

Use one term for one thing. If you say "project" on one screen, do not say "workspace" on the next unless they are different things. Inconsistent terms make people wonder whether they are looking at something new. Keep a simple word list as you go: it becomes the start of your style guide later in the course.