Voice and content is a system layer that most teams don't realize they need until two writers ship two different conventions for the same kind of message. The systems below treat it as canonical — a documented voice, tone modulation rules, microcopy patterns for buttons and errors, and a small style guide that ships ahead of components.
Adopt this layer if more than one writer touches your product UI. The cost of inconsistency in copy is the same as the cost of inconsistency in components — it just shows up in different surveys.
- 01A documented voice (e.g. "plainspoken, friendly, never condescending").
- 02Tone modulation rules — the same voice in a celebratory moment vs an error moment.
- 03Microcopy patterns for buttons, error states, success confirmations, empty states.
- 04Plain-language test cases for jargon, abbreviations, and locale-specific terms.
- 05A small style guide (capitalization, punctuation, oxford-comma stance) that the whole team can quote.
- 01Two writers ship two voices and the product reads like it was made by competing teams.
- 02Error messages range from terse to apologetic depending on which engineer wrote them.
- 03Localizations don't preserve the voice and the brand fragments by region.
Mailchimp Design System
Mailchimp
Content Style Guide
The reference for friendly, plainspoken product writing — predates most modern design systems and still gets quietly copied.
Polaris
Shopify
Voice and tone documentation
Industry-leading content guidelines — Polaris's voice & tone is widely cited beyond Shopify's own surfaces.
GOV.UK Design System
UK Government
Plain English / Style guide
Plain-language standards engineered for users completing high-stakes services. The bar for copy clarity in critical flows.