---
type: Content Design Concept
title: UX Writing
description: CTAs, labels, helper text, errors, empty states, terminology consistency, and voice/tone.
tags: [ux-writing, microcopy, terminology, voice-tone]
---

# Purpose

Use this concept when writing or evaluating interface copy, marketing copy, report summaries, forms, navigation, errors, empty states, prompts, and CTAs.

# Rules

- Use the user's language, not internal taxonomy.
- Put the result before supporting detail when the user is deciding.
- Write CTAs as action plus object or result.
- Write errors as problem plus fix, without blame.
- Write empty states as current state plus next step.
- Use the same term for the same concept everywhere.
- Avoid vague labels such as "OK", "Submit", "Manage", "Process", and "Click here" unless context makes the result unmistakable.
- Do not repeat the heading in the first sentence.
- Voice is stable brand personality; tone changes with user risk, urgency, and emotional state.

# Component Copy Patterns

- Button: action plus result.
- Label: what the field or control is.
- Helper: format, reason, or consequence before input.
- Error: what is wrong and how to fix it.
- Alert: problem, impact, and next action.
- Link: meaningful out of context.
- Toast: what changed, with undo when practical.

# Contract Fields

Record:

- Voice and tone.
- Canonical terms.
- Words to avoid.
- CTA rules.
- Error and empty-state rules.
- High-risk copy assumptions.
