Most brand guidelines spend twenty pages on logo clearance and two paragraphs on voice. Then a copywriter ships a campaign, a product manager writes an onboarding email, and a support rep answers a complaint. The customer ends up meeting three strangers wearing the same logo. Voice and tone are not decoration. They are how your positioning becomes legible to a human being. Get them right and every touchpoint reinforces the same character. Get them wrong and your brand is just a color palette.
This guide is practical: a framework you can actually use, say-this/not-that examples, and the upstream logic that explains why voice work can’t start with word lists.
Voice vs. tone: the distinction that matters
“Voice and tone” is often said in one breath, as if the words are interchangeable. They aren’t, and conflating them is the source of most voice-doc failures.
Voice is who you are. It is fixed. Your brand’s voice doesn’t change between a blog post and a legal notice, between a good quarter and a bad one, between a first-time visitor and a ten-year customer. Voice is the set of persistent character traits that make every piece of writing unmistakably yours. Think of it like a person: someone who is direct, a little dry, and deeply informed about their craft doesn’t become gushing and vague on a stressful Tuesday. Their voice holds.
Tone is how you express voice in context. Tone flexes. The same direct, dry, informed brand adjusts its weight when the context calls for it. A homepage hero and a shipping-delay email are both on-brand, but the hero leans confident and forward, the delay email leans honest and accountable. Same voice, different tone. Think of a person who’s warm at dinner and brisk in a boardroom without becoming a different person.
The practical test: if a trait belongs in a voice doc, ask whether it could plausibly flip in a different context. If yes, it’s tone. If no, it’s voice. Many teams write “conversational” in the voice column and then wonder why it feels wrong in a product liability disclaimer. Conversational is a tone setting, not a personality trait.
Voice is who you are. Tone is how you sound right now. Both matter. Neither substitutes for the other.
Start upstream: voice is downstream of positioning
Here is where most voice projects fail. A team runs a workshop, generates adjectives, picks five, writes examples, and ships a doc. Six months later nobody uses it because the adjectives don’t feel connected to anything real about the brand.
Voice is downstream of positioning. If you haven’t decided what space you’re occupying, what category you’re playing in, and why a buyer should choose you over the obvious alternative, then voice work is just creative writing without a brief. The character traits in your voice doc should follow logically from your position: expressions of why you exist, not personality choices made in isolation. Brand archetypes offer a useful vocabulary for naming that character before you write definitions, but the definition has to trace back to your specific position to stick.
A brand positioning guide will get you to those decisions: what makes you different, who you’re for, and what you’re not. Your voice traits should feel like natural extensions of that position. Direct because you’re confident in the work. Precise because you don’t improvise strategy. Unimpressed by hype because you’ve seen behind it enough times to stop performing it. The traits are earned from the position, not assigned by committee.
The same logic applies to messaging architecture: your north-star message and pillars are the substance that voice delivers. Voice without substance is just style; substance without voice is a report nobody wants to read. Do the upstream work first.
Build the voice framework
A workable voice framework has four components. Not a list of adjectives, but a structure you can use when writing, editing, or onboarding someone new.
1. Character traits (with definitions)
Pick three to five traits. Not adjectives alone: each trait needs a one-sentence definition and a brief explanation of why this trait is true of this brand specifically.
“Bold” is not a trait. “Direct: we state what we believe without qualifying it to death, because we’re accountable for our recommendations” is a trait. The definition does the work. Without it, “direct” becomes a Rorschach test, and in six months one writer is aggressive while another is vague.
Keep the list short. Every trait beyond five dilutes the ones that matter. If two traits are nearly synonymous, cut one. If a trait describes every brand in your category, it’s table stakes, not identity.
2. Anti-traits
For every voice trait, there is a shadow: a misread of the trait that tips into something wrong. Define these explicitly.
- Direct → not abrasive
- Confident → not arrogant
- Plain → not simplistic
- Warm → not sycophantic
- Expert → not jargon-heavy
Anti-traits are as useful as traits during editing. When a writer flags a line as “too harsh” or “too salesy,” they’re pointing at an anti-trait without naming it. Name it and the note becomes actionable.
3. Tone modes
Map the contexts your brand writes in and assign tone settings to each. Four to six modes cover most of it:
- Thought leadership / editorial: confident, a little opinionated, shows the reasoning
- Marketing and campaign copy: energetic but grounded, no hype, benefit-forward
- Product and UI: plain, efficient, useful (personality in small doses)
- Support and service: warm, accountable, efficient (no corporate deflection)
- Legal and policy: clear and honest, still reads like a human wrote it
For each mode, write two or three lines of example copy, not rules. Examples are remembered; rules are consulted and then ignored.
4. Say-this / not-that examples
This is the component teams actually use at 9pm before a deadline. It should be specific enough to be useful and broad enough to cover the real cases.
Context: announcing a delay
- Not that: “We apologize for any inconvenience this may have caused.”
- Say this: “We’re behind. Here’s what happened and what we’re doing about it.”
- Why: Own it plainly. Passive corporate language erodes trust faster than the delay itself.
Context: describing a service
- Not that: “Leveraging cutting-edge solutions to supercharge your brand ecosystem.”
- Say this: “Strategy, brand, and build. Run by the people who scoped the work.”
- Why: Specifics are credible. Jargon clusters read as evasion.
Context: a call to action
- Not that: “Don’t miss out on this opportunity to transform your business.”
- Say this: “If this sounds like the kind of work you’re trying to do, let’s talk.”
- Why: Urgency manufactured from nothing is a beg dressed as confidence. Drop it.
Context: editorial / thought leadership
- Not that: “In today’s fast-paced, ever-evolving digital landscape…”
- Say this: Start the actual argument in the first sentence.
- Why: Opening hedges are a tell. Every reader knows what year it is.
Build your own examples from real copy your team has written or reviewed. The examples pulled from your own work are the ones people remember.
Voice connects downstream to every piece of copy
Positioning and messaging are upstream. Voice is the channel those decisions flow through. The implications run downstream to everything, and that’s the part that’s easy to underestimate.
Every channel, every writer
Voice docs fail when they’re treated as a one-time deliverable for the brand team. A doc that only the brand manager has read is not a voice. It’s a file. Voice is operational when it shapes the email a sales rep sends on a Friday afternoon, the error message a developer ships without review, and the caption a coordinator writes at 8pm.
That means the doc has to travel. Short enough to read in fifteen minutes. Example-heavy. Opinionated enough to give people permission to edit copy that sounds wrong, even if they can’t name why. And embedded wherever your team creates. A Notion doc nobody visits doesn’t count.
This is why brand guidelines teams actually use look different from guidelines built to look comprehensive. Usable beats complete.
The edit test
Before any piece of copy ships, run it through two questions:
- Could a competitor have written this? If yes, it’s generic, not on-brand.
- Would a reader of only this piece be able to guess the other traits in the voice doc? If not, the traits aren’t showing up in the writing.
The second test is harder but more revealing. Voice isn’t a collection of rules applied mechanically; it’s a character detectable in any sample. If you have to consciously inject the trait, it’s not voice yet. It’s a checklist.
Voice as part of the brand system
Voice doesn’t live in isolation. It’s one component of a brand system, sitting alongside visual identity, typography, color, sonic identity, and the logic that ties those decisions together. The brands that feel coherent across a billboard, a product screen, and a support reply are coherent because someone made all those decisions from the same center of gravity.
Voice is that center of gravity made verbal. An isolated voice doc is an artifact. A connected voice system is a capability. The same connective logic applies to motion: a logo that moves or a transition that plays should feel like the same character your copy expresses.
How Strynal approaches voice
At Strynal, voice work is a branding engagement, not a copywriting add-on. We start from positioning. Without knowing what space you’re occupying, we can’t say what traits serve it. We build the framework with enough definition to be genuinely useful, not so long that it collects dust. And because strategy, brand, and build sit under one roof, the voice we establish carries through to the website, the campaign, and the product, with no translation needed between a strategist’s deck and a writer’s draft.
Every engagement starts on a blank page. Your voice framework reflects your position and your character, not a template, and not a list of adjectives the last agency liked.
If your brand sounds slightly different in every channel and you can’t quite put your finger on why, that’s almost always a voice problem. It’s one of the more fixable ones. Reach out and we’ll help you define the thing the whole team can write from.