UI copy: buttons are verbs

Ask what the user is doing and what they fear, then decide what goes on screen. Visual tricks do not fix structural problems.

Task: Vague labels leave users unsure what happens.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - key actions and consequences
   - user vocabulary
   - brand voice
   - confirmation needed
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- buttons state the verb and result, not 'OK'
- destructive actions state the consequence
- confirmation repeats the object and count
- three misleading labels

[Process]
1. State the single job of this screen
2. Answer the user's current worry first
3. Order by information priority and delete
4. Design empty, loading and error states
5. Give a minimal usability test

[Output]
One job, priority, three states, test plan.

[Do not]
- Never two primary actions on one screen
- Do not test with lorem ipsum
- Never ignore the empty state
- Never use colour as the only signal