The one-sentence test
Ask three people on the team to write, separately, one sentence describing what the product is for. If the sentences differ, the product will too: in its navigation, its priorities and its arguments. Agreeing that sentence is the cheapest design work you will ever do.
Labels that describe outcomes
“Submit”, “Process” and “Continue” describe the machine. “Send booking request”, “Pay £24.00” and “Save and choose a time” describe what will happen to the person. Outcome labels reduce hesitation and errors, and they are free.
The art of the empty state
The first time someone opens a product, most screens are empty. An empty list is an opportunity to explain what will appear there, why it matters and how to add the first item. Design empty states first; they are the product's introduction.
Release notes people read
Lead with the benefit, describe the change in the reader's terms, mention anything they must do differently, and stop. Keep engineering detail in the change log.
Writing a brief
A good brief describes people, tasks, constraints and what success looks like, and leaves the solution open. The brief composer gives you a starting structure.
Inheriting a product
Before changing anything, learn how it is built, deployed and backed up, and write that down. Then add tests around the most valuable behaviour. Most inherited products are worth keeping; most rewrites take longer than planned.