Your brand voice document is a fiction.

Somewhere in your shared drive is a brand voice document. It says things like "confident but not arrogant," "warm but professional," "human." It has a spectrum chart. It may even have a celebrity comparison: "if our brand were a person, they'd be part Brené Brown, part Anthony Bourdain." The team references it during quarterly brand reviews and ignores it every other day of the year.

Meanwhile, the actual brand voice, the one your customers hear, lives in places nobody audits. The support ticket templates. The sales deck the regional team modified. The CEO's LinkedIn posts. The error messages in the product. The hold music. That's the real voice document, and nobody wrote it on purpose.

The document describes an aspiration

Voice guides almost always describe the brand's desired self, not its actual self. This isn't dishonesty; it's the natural outcome of the process. A brand team sits in a room, talks about who they want to be, and writes down adjectives. Nobody walks across the hall, pulls up the last fifty customer service emails, and reads them out loud.

I've done this exercise with consumer brands, B2B platforms, and nonprofits, and the gap is always there. The guide says "empowering." The support tickets say "per our policy." The guide says "playful." The onboarding emails read like a compliance filing. The distance between the aspirational voice and the operational voice is the actual brand problem, and the document is hiding it.

Voice is an output, not an input

Here's the structural issue: most voice guides treat tone as something you decide and then distribute. In practice, voice is an emergent property of the organization. It comes from who gets hired, how they're trained, what gets rewarded, and what gets edited. A company that punishes risk in copy will sound cautious no matter what the guide says. A company whose legal team reviews every customer-facing sentence will sound like legal wrote it, because legal did.

You can't fix an organizational voice problem with a PDF. The PDF is a symptom.

What a useful voice guide actually looks like

The voice documents I've seen work share three traits. First, they're built from an audit of what the brand actually sounds like today, not a workshop about what it should sound like tomorrow. You have to start with the truth to move away from it.

Second, they include real examples from the organization (not hypothetical copy, but actual emails, actual product strings, actual social posts) shown in before-and-after pairs. The team needs to see themselves in the document, not a fantasy version of themselves.

Third, they're short. A voice guide that's forty pages long is a novel nobody reads. The best ones fit on a single page: three principles, each with a concrete do/don't, each with a real example. If you can't compress the voice into that space, you haven't actually found it yet. You've listed synonyms.

The audit nobody wants to do

Pull the last thirty customer-facing communications from across the company. Not the marketing ones, the operational ones. Support replies, billing notices, onboarding sequences, error states. Read them in order, out loud, as if they were written by one person. If that person sounds coherent, you have a voice. If that person sounds like they have a dissociative disorder, you have a voice document you need to throw away and start over.

The work isn't writing the guide. The work is closing the gap between the guide and the inbox.