What it is
Documented guidance on the product’s consistent personality (voice) and how it flexes by situation (tone), so all content sounds coherent and appropriate.
When to use it
During Prototype and Implement, as content scales across people and surfaces.
Why (value)
Keeps content consistent and on-brand across many writers and contexts, and ensures tone adapts appropriately (e.g., errors vs. celebrations).
How to run it
- Define the core voice attributes with examples.
- Describe how tone shifts by context.
- Provide do/don’t examples.
- Socialize with everyone who writes.
- Maintain as part of the design system.
Inputs and outputs
- Inputs: Brand personality, audience understanding, content examples.
- Outputs: Voice and tone guidelines with examples.
Time and effort
Medium. Drafting plus adoption.
Evidence and limitations
A consistency framework; whether the voice resonates with users can be validated with research. See Evidence and limitations.
Tips and pitfalls
- Show examples, not just adjectives.
- Distinguish voice (constant) from tone (contextual).
- Cover error and sensitive situations.
Variations
Voice charts, tone spectrums, content style guides.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Plain-language editing — Rewrite content so people can read, understand, and act on it the first time.
- Design principles — A short set of shared values that guide decisions and resolve trade-offs consistently.
- Design system work — Build and maintain the shared components, tokens, and guidelines a product is made from.
