Your style guide doesn't need a tone section

You're documenting the wrong things

Your three-person content team doesn't need a manifesto about being "warm but professional" or "accessible yet authoritative." You need to know whether it's "log in" or "login," whether you capitalize job titles, and how you handle the Oxford comma.

Tone descriptions are vague. Usage rules are binary. One prevents arguments at 3pm when someone's trying to ship a page.

What belongs in a working style guide

Document decisions you've already made that someone will need to look up:

• Capitalization for your specific terms ("Help Center" or "help center")
• Punctuation in lists and UI copy
• How you write times, dates, and numbers
• Whether you use contractions
• Product and feature name formatting
• Common words you spell or hyphenate a specific way

These are answers, not principles. When someone asks "which way?" you point at the guide and move on.

The personality question solves itself

If you hire someone who writes like a press release and you needed casual how-to documentation, you hired wrong. That's not a style guide problem.

Voice emerges from the person writing and the [structure you give them](/category/structure). If your content templates and [field-level help](/posts/field-level-help-text-that-prevents-mistakes) ask for concrete user benefit, you get useful pages. If they ask for "engaging introductions," you get hot air.

You don't control tone by describing it. You control it by editing and by not publishing things that sound wrong.

Start with what causes actual confusion

Keep a running list for two weeks of every formatting question someone asks or every inconsistency you notice during editing. Those items become your guide.

Did someone ask whether to bold the labels in a definition list? Write it down. Did you catch three different phone number formats in one afternoon? Pick one, document it, fix the others.

Ignore aspirational descriptions of brand personality. Solve the small decisions that eat time when repeated fifty times across a site.

Make it findable or don't bother

A style guide in a PDF no one opens is decorative. Put decisions where people write:

• In your CMS as [help text](/posts/field-level-help-text-that-prevents-mistakes) on specific fields
• In a searchable wiki or doc with a shortcut everyone knows
• As comments in your [content templates](/posts/content-templates-arent-forms-to-fill-in)

If someone has to remember to check it, they won't. If it's right there when they need the answer, they will.

Most small sites don't need brand voice workshops. They need a list of thirty decisions, kept current, that prevents the same question from being asked twice.