How to Define Your Brand Voice (Framework + Worked Example)

To define your brand voice, audit what you actually publish, name three or four traits that describe the best of it, pair each trait with a do and a don't, ban the words that make you sound generic, and turn it all into rules a draft can pass or fail. One focused afternoon covers the first working version.

Most voice projects skip straight to adjectives and die in a slide deck nobody opens again. This framework works backward from enforcement: every step produces something you can hold a draft against. Here's the process, then a worked example so you can watch it run end to end.

What is a brand voice, actually?

A brand voice is the consistent personality in everything your company writes: the traits, vocabulary, and rhythm that make a paragraph recognizable as yours before anyone sees a logo. Voice stays constant across channels. Tone, how that voice flexes for a support reply versus a launch post, moves with the situation.

That distinction matters because you're defining the constant here; the ranges come later. For the full picture of how tone flexes around a fixed voice, the complete guide to tone of voice covers it. For now: voice first, tone second.

Step 1: Audit what you actually publish

Your real voice lives in what you ship, so start with the writing, never the brand deck. Pull ten to fifteen recent pieces from across your channels and read them in one sitting, out loud if you can stand it.

• Three or four blog posts or guides
• A week of social posts
• Two onboarding or lifecycle emails
• A handful of support replies
• Your homepage and pricing page

Mark every sentence that could only have come from you, then every sentence a competitor could publish unchanged. The first pile is your raw voice. The second pile is what you're about to fix. For a faster baseline, run the 90-second Brand Genome and it will score how consistent and distinct your published copy already is.

Step 2: Name three or four traits, each with a do and a don't

Pick three or four adjectives that describe the best sentences from your audit, then make each one enforceable by writing a do and a don't beside it. The pairs are the point. A trait without them is a mood-board word.

Two traps to watch. Generic traits describe every company on earth, so qualify each one until it excludes someone. Friendly says nothing by itself; blunt-friendly, the way a good bartender is friendly, starts to mean something. And past four traits, writers can't hold them all in their head while drafting, so the extras quietly stop existing.

A pair in practice looks like this. Plainspoken: do say the price, the limit, and the catch in the first two sentences. Don't cushion bad news inside three paragraphs of context.

Step 3: Write the ban list

The ban list is the fastest rule you'll ever enforce: words and phrases that never appear in your copy, whoever wrote it. It needs no judgment call, which is why it actually gets used. A draft either contains the words or it doesn't.

Start with whatever your audit flagged as could-be-anyone language, the jargon everyone in your category leans on, and the filler your team reaches for when tired. Most B2B lists end up banning things like synergy, best-in-class, cutting-edge, and empower. We keep a running list of corporate words worth banning if you want a head start.

Step 4: Turn traits into rules a draft can fail

A voice guide only works if a draft can fail it. Rewrite each trait and pair as a yes-or-no check, because any rule two reviewers can argue about is decoration, and decoration loses every deadline fight.

• Testable: contractions are mandatory in product copy.
• Testable: no exclamation points outside genuine celebration.
• Testable: every feature sentence names what the reader gets, in second person.
• Decoration: we sound approachable yet authoritative.

Rules in this shape have a second advantage: software can hold them. Savra reads exactly this kind of rule set as guardrails and applies it to every draft automatically, which is what keeps a voice intact once volume picks up.

Step 5: Pressure-test on your worst channel

Test the voice where it's hardest to keep, because that's where it will break first. For most teams that means support macros, character-limited ads, or the emails nobody wants to send: payment failures, price increases, saying no to a refund.

Rewrite two or three of those in the new voice. If a trait keeps buckling, tighten its don't or cut the trait entirely; a voice that only survives the marketing site was never a voice. This exercise also hands you your first before-and-after examples for the guide itself.

A worked example: Fernbrook's afternoon

Fernbrook is a made-up bookkeeping app for freelance designers. The brand is fictional, invented for this guide, but the steps are exactly what you'd run. Here's how the afternoon plays out.

The audit

Fifteen pieces in one sitting. The blog reads like every software blog alive. The homepage hedges. But the support replies are great: direct, dryly warm, allergic to jargon, firmly on the customer's side of the desk. That's the raw voice, hiding in the least glamorous channel.

The traits and rules

Fernbrook picks three traits: plainspoken about money, dryly warm, on your side of the desk. Each gets its do and don't, then a short ban list (grow your empire, financial wellness journey, empower) and a handful of testable rules, including one lifted straight from the best support reply:

Name the number first. Any sentence about money starts with the amount, the date, or the percentage, never with reassurance.

The pressure test

The worst channel is the failed-payment email. The old version spent four paragraphs apologizing before naming the amount. The rewrite passes every rule: number first, one dry line of warmth, next step in bold. The voice survived its hardest room, so it ships, and the whole guide fits on one page.

That's the full framework. Run the audit this week even if the rest waits; ten minutes of reading your own copy aloud will tell you exactly how much of an afternoon you need.