Brand voice: turn a personality into usable writing rules

Keep the voice steady while the tone responds

A brand voice guide is useful when it helps someone make a choice while writing, not when it only supplies a list of adjectives. This analytical exercise uses a fictional home-repair service to show the distinction. It does not describe a real company, interview, campaign or customer response.

Mailchimp’s published guide separates voice, which it describes as relatively consistent, from tone, which changes with context and the reader’s emotional state. It also says clarity should take priority over entertainment. [1] That offers a practical starting point: define a small set of durable communication principles, then describe how those principles sound in different situations. “Friendly” alone does not tell an editor what to do when explaining a delayed appointment or a technical limitation.

Turn personality words into decisions

Imagine the fictional service wants to sound capable, considerate and direct. Those words become useful only when each one has a writing behavior and a boundary. “Capable” might mean naming the next step and the information a customer needs to prepare; it should not mean claiming expertise the company has not documented. “Considerate” might mean acknowledging a disruption before explaining a policy; it should not mean using forced cheerfulness when someone is frustrated. “Direct” might mean putting the service and location in the first sentence, rather than hiding the offer behind a slogan.

Add examples that demonstrate the decision. A vague line such as “We make home care easy” can become “Book a repair visit and tell us which appliance needs attention.” The second version states an action and the information requested. These are proposed lines for a fictional business, not published brand copy. The guide should also include a counterexample and explain why it fails, so a producer can recognize the boundary instead of memorizing one preferred sentence.

Adapt the tone to the moment

Use a simple matrix for the situations a small marketing team actually publishes: a service page, a booking confirmation, an appointment-delay notice, a short demonstration video and a social post. For each, record the reader’s likely question, the emotional context, the information that must be clear, and the tone adjustment. A delay notice may be calm and apologetic; a demonstration can be more energetic. Both can still use the same plain language and avoid unsupported promises.

Google’s developer writing guide recommends conversational, respectful language, straightforward wording and care for readers with different levels of English proficiency. [2] That guide is written for developer documentation, so a marketing team should treat it as a useful reference rather than a universal brand standard. The transferable test is whether the message remains understandable without insider vocabulary or a joke that depends on cultural context.

Connect the voice to claims and evidence

Voice rules should also cover what the organization is allowed to say. Build a short claims table with four columns: proposed statement, evidence needed, approved wording and review owner. “Appointments available this week” requires a current schedule; “same-day repair” requires a defined service area and a real capacity check. If the evidence is missing, the copy should describe the service without implying the unverified promise. This is a proposed editorial control, not a claim about a particular company’s compliance process.

The point is not to make every sentence cautious. It is to give confidence a factual basis. A useful guide can show the difference between a supported specific statement, a general description and a claim that needs approval. Mailchimp’s guide, for example, connects its voice principles to plainspoken writing and avoiding overstatement. [1] A team can apply that principle to its own evidence and risk without borrowing Mailchimp’s personality or wording.

Test the guide with real production tasks

Before distributing a voice guide, give two people the same short brief and ask each to draft a service-page introduction, a confirmation message and a 15-second video opening. One writer should know the guide; the other can use only the brief and guide, without verbal coaching. This is a proposed exercise, not a usability study or a result. Review whether both drafts preserve the facts, make the next step clear and sound recognizably related without using identical wording.

Mark every place where a writer had to guess: whether humor fits, how to describe a delay, which technical term to explain, whether a claim needs evidence, and how much detail belongs in a short format. Revise the rule that left the ambiguity. Keep a small “before and after” library with the reason for each change, then assign an owner and a review date so the guide can evolve when services or audiences change. Do not evaluate success by counting how often people repeat a slogan; check whether the rules support accurate, clear communication across actual materials.

A practical next step is to select three upcoming assets, write their reader questions and required facts, and use them to draft the first voice-and-tone matrix. Treat the initial language as a working system to inspect. The creative value comes from giving writers enough consistency to make the brand recognizable and enough context to respond appropriately, while keeping every promise tied to evidence.