Write product microcopy to help a person understand what is happening and take the next safe action. Name the state, explain the consequence when necessary and give a specific recovery or continuation step. Keep the brand voice recognisable, but adjust tone to the stakes. Clarity, accessibility and trust take priority over personality in errors, consent and irreversible actions.

Start with the user’s task and state

Microcopy includes labels, buttons, validation, notifications, onboarding and empty states. Its job depends on the person’s task.

Before writing, record:

  • what the person is trying to do;
  • what the system knows has happened;
  • what the person may not know;
  • what action is available now;
  • whether the action is reversible; and
  • the consequence of misunderstanding.

Do not make the interface pretend to know a motive or emotion. “You forgot your password” is less accurate than “The email or password is incorrect”, which also avoids confirming whether an account exists.

Write controls that predict the result

Labels and buttons should name the outcome. “Save billing address” and “Delete draft” are more informative than “Submit” or “Yes”. Use consistent terms.

Use the brand vocabulary guide to settle preferred product terms, definitions and deprecated language. Consistency reduces the interpretive work users must do.

Avoid putting essential information only in placeholder text. It disappears as people type and may not act as an accessible label.

Make onboarding support progress

Onboarding should help people reach a meaningful first outcome, not tour every feature. Explain requirements and whether a step can wait.

Break complex setup into a visible sequence. If a permission is optional, explain what will not work without it.

Celebrate progress in proportion to the event. A brief acknowledgement can reassure; excessive confetti or praise can feel obstructive, especially in frequent or serious workflows.

Write errors for recognition and recovery

An error message should identify the problem in plain language, place it near the relevant field or action and explain how to fix it. Preserve valid input where possible.

A useful pattern is:

  1. What happened: “The file could not be uploaded.”
  2. Why, if known and helpful: “It is larger than 10 MB.”
  3. Recovery: “Choose a smaller PDF and try again.”

Do not blame the person, show only internal codes or promise an unsupported recovery time. If the cause is unknown, explain what to try.

Use empty states to explain possibility

An empty state may be a first-use state, a completed state, no search results, filtered-out content or missing permission. Diagnose which one before writing.

First-use copy can explain what will appear and offer the next action. “No results” should summarise the query and suggest an adjustment.

Do not use every blank space to promote another feature. Sometimes the honest message is that nothing requires attention.

Adapt tone to risk and emotion

Voice remains the organisation’s consistent character; tone responds to context. The tone-by-context method can define how language changes across routine, positive, difficult and high-stakes moments.

Humour may suit a harmless empty state but not lost work, missed payments or account failure. In urgent situations, use calm instructions and a support route.

Handle confirmation and irreversible actions

For deletion, payment, permission and public sharing, name the object and consequence before commitment. Distinguish a reversible archive from permanent deletion. Use a confirmation step when the impact is serious and accidental activation is plausible; avoid confirmation fatigue for routine actions.

Button pairs should be unambiguous. “Delete report” and “Keep report” are clearer than “Yes” and “No”. After the action, confirm the resulting state and offer undo when the system genuinely supports it.

Review accessibility and translation

Ensure errors are associated with fields, status changes reach assistive technology and meaning does not depend only on colour, position or an icon.

Write complete, literal phrases that can be translated without reconstructing fragments. Leave room for text expansion and avoid embedding variable words inside a sentence when grammar will change across languages.

Test important flows with people who use different devices and access methods. The cross-channel voice guide can keep product terms aligned with support and marketing without forcing identical tone.

Use a microcopy review checklist

For each string, ask:

  • Does it match the actual system state?
  • Does it use the established term?
  • Is the next action specific?
  • Is the consequence visible before commitment?
  • Is necessary help available at the point of need?
  • Does tone suit the stakes?
  • Can the message be understood without colour or icon alone?
  • Will it still work with a longer name, number or translation?

Review strings in the live interface, not only in a spreadsheet.

Illustrative example

Imagine an empty project dashboard that says, “Nothing here! Let’s make magic.” It does not explain what a project is or what happens next.

A clearer version is: “Projects group tasks, files and decisions for one piece of work. Create a project or join one using an invitation.” Buttons say “Create project” and “Use invitation”. This example is illustrative; it does not describe a real product.

Recognise the trade-offs

Short copy reduces visual load but may omit recovery details. Progressive disclosure can keep the main message concise while making help available. Personality can create warmth but also ambiguity, translation difficulty and an insensitive tone.

Standardising patterns improves consistency, yet edge cases still need contextual writing. Treat the design system as a starting rule with documented exceptions, not a phrase factory.

Frequently asked questions

How short should microcopy be?

As short as it can be while preserving the state, consequence and action. A two-word label may be enough; a high-stakes error may need several sentences and a support route.

Should error messages apologise?

An apology can be appropriate when the service caused disruption, but it should not replace explanation and recovery. Avoid repeated apologies for errors the interface could prevent.

Who owns product microcopy?

Ownership varies, but product, design, engineering, support, accessibility and legal specialists may all contribute. Give one role editorial accountability and maintain shared patterns and terms.

Your useful next step

Choose one critical product journey and capture every label, hint, button, error and confirmation. Mark where the user’s state or next action is unclear. Rewrite the highest-consequence string, then test it in context with keyboard and screen-reader checks.

Publication note: This guide is published by To-Do Growth and reviewed under our Editorial Policy. Illustrative examples are labelled and are not presented as customer case studies.