Microcopy is the wording people meet while trying to do something: a button label, a field hint, an error message, or the sentence confirming that a change has been saved. Its brevity makes precision especially important. A few words may carry the only explanation of what happens next.
“Get started” and “Submit application” are not interchangeable improvements on a generic button. One suggests the beginning of a process; the other may commit information for review. The best wording describes the action the product will actually take.
Write for the moment of use
Begin with what the person needs to know at that point. A field label identifies the information requested, a hint clarifies an unfamiliar requirement, and a confirmation explains the result. Avoid making one small piece of text carry several unrelated jobs.
In an illustrative account flow, “Invite colleague” is clearer when it sends an invitation, while “Add colleague” may imply access is immediate. The surrounding copy can explain which permissions the invitation grants and whether they can be changed later.
Use the audience’s vocabulary, supported by research rather than internal naming conventions. Copy testing can help examine wording, but functional text should also be tested in the interface because placement and sequence affect interpretation.
Give errors a useful next step
The GOV.UK Design System’s error guidance recommends explaining the problem and how to correct it. “Enter a date in the future” gives someone a route forward; “Oops, something went wrong” does not explain whether they made a mistake or the service failed.
A problem the user cannot fix needs different wording from an invalid field. State what happened, what was preserved where known, and what they can do next. Do not tell them to retry endlessly when the service is unavailable, or imply that their data is saved unless it is.
Tone should fit the situation. A playful phrase that seems engaging in a design review can become irritating when it blocks an important task.
Test understanding through action
Ask participants to complete a realistic task scenario, then examine where the wording helped or misled them. Questions about what they expect to happen can reveal a mismatch before they select a consequential control.
Evaluate comprehension, successful action, and recovery rather than asking only which phrase people prefer. A label can be popular and still create the wrong expectation. Keep related terms consistent across the journey, while allowing enough explanation where the decision needs it. Concision is useful when it removes unnecessary reading; it is less useful when it removes the information someone needed to proceed confidently.