Define Brand Voice and Situational Tone

Translate personality into writing decisions

Choose principles that affect actual sentences. Words such as “human” or “bold” are too broad unless the guide explains what they mean in use. Describe vocabulary, sentence structure, directness, and the relationship with the reader. Include what the principle does not justify, so it cannot become an excuse for vague or inappropriate copy.

In a hypothetical volunteer coordination product, “clear and encouraging” might mean naming the next action and acknowledging the person’s effort without excessive celebration. It does not mean calling every small update amazing. Show a short before-and-after example that demonstrates the decision. Writers should be able to use the principle to revise a sentence, not merely recognize an attractive personality label.

Adapt tone to the person’s situation

Consider the user’s likely goal, emotional context, and consequence of the message. A successful sign-up, a missed deadline, and a failed save need different emphasis. The voice can remain recognizable while humor, enthusiasm, and detail change. Prioritize the information the person needs to act, especially in stressful or uncertain situations.

For the volunteer product, a shift confirmation can feel warm and positive, while an unavailable shift should explain the change and alternatives calmly. A playful error message may be frustrating when the person is unsure whether their commitment was saved. Write tone guidance around situations rather than creating one rigid style that every screen must imitate.

Create examples and usable boundaries

Build a small collection covering headlines, onboarding, validation, support replies, and important status messages. Pair examples with the principle they demonstrate. Include a few inappropriate alternatives and explain the problem, such as overpromising, blaming the user, or hiding the action in a metaphor. This helps contributors understand the reasoning rather than copying phrases mechanically.

In the volunteer tool, a save failure should identify the failed action and next step. A launch announcement can be more expressive, but it should still explain the product. Keep terminology stable for task labels and statuses. If a playful phrase replaces an established term, check whether it improves recognition or simply makes the writer enjoy the copy more.

Review the guide through real content

Apply the guide to a representative set of current messages. Look for contradictions between principles and the product’s actual behavior. If the voice promises calm control but the interface produces unclear outcomes, copy alone cannot resolve the mismatch. Revise either the experience or the promise. Assign an owner who can update examples as the product changes.

Ask writers and support colleagues to apply the guide independently, then compare decisions. Differences can reveal vague instructions or missing contexts. Avoid enforcing identical sentence patterns everywhere. The goal is recognizable judgment, not uniform rhythm. Keep the guide brief enough to consult during work and specific enough to help someone make a difficult tone choice.

• Define principles as concrete writing decisions.
• Adapt tone to context and consequences.
• Include useful and unsuitable examples.
• Review the guide against real product messages.

If the product also needs a name, carry the audience language and intended associations into explicit naming criteria instead of selecting a word by personality alone.Run a Product Naming Workshop with Clear Criteria