Writing Interface Instructions People Can Act On
Interface instructions should explain the immediate task using the information already visible. Long background explanations can obscure the one detail a person needs to proceed.

Put guidance beside the decision
State what to enter, choose or review and explain any important consequence. Use the same names as the fields and controls. Move optional background information into a secondary help area rather than repeating it beside every input.
Practical checklist
- Use the visible control names.
- Explain unusual requirements.
- Keep consequences near the action.
- Remove instructions that repeat the label.
How to review the result
Ask someone to complete the task without a demonstration. Their first question usually identifies the missing instruction more effectively than adding another paragraph everywhere.