---
# === IDENTITY ===
id: business/brand-strategy/tone-of-voice-guide-template/2026
canonical_question: "How do I create a tone of voice guide — formal/casual, serious/playful, authoritative/approachable scales with examples?"
aliases:
  - "Brand tone of voice template with scales and examples"
  - "How to define voice and tone guidelines for content"
  - "Tone dimensions framework — formal, casual, playful, serious scales"
entity_type: execution_recipe
domain: business > brand-strategy > tone of voice guide template
region: global
jurisdiction: global
temporal_scope: 2024-2026

# === VERIFICATION ===
last_verified: 2026-03-11
confidence: 0.88
version: 1.0
first_published: 2026-03-11

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: stable
  last_breaking_change: null
  next_review: 2026-09-07
  change_sensitivity: low

# === CONSTRAINTS ===
constraints:
  - "Voice stays constant across all content; tone adapts to context and user emotional state"
  - "Each tone dimension must include concrete do/don't examples — abstract scales without examples are unusable"
  - "Content type tone mapping must cover at minimum: marketing, product UI, error messages, support, and legal"
  - "The guide must be validated with real writing samples from your existing content before rollout"
  - "Tone guides without stakeholder sign-off get ignored — secure executive and cross-team buy-in before distributing"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs full brand strategy including positioning and visual identity"
    use_instead: "business/brand-strategy/brand-messaging-framework/2026"
  - condition: "User only needs a content style guide (grammar, formatting, terminology)"
    use_instead: "Search knowledgelib.io for content style guides — no dedicated unit yet"
  - condition: "User needs to evaluate an existing tone guide against best practices"
    use_instead: "Search knowledgelib.io for brand voice audits — no dedicated unit yet"

# === AGENT HINTS ===
inputs_needed:
  - key: brand_maturity
    question: "Does the brand have existing voice/tone documentation?"
    type: choice
    options: ["no existing guidelines", "informal guidelines exist", "formal guide exists but needs updating"]
  - key: content_volume
    question: "How much content does the team produce?"
    type: choice
    options: ["low (1-5 pieces/week)", "medium (5-20 pieces/week)", "high (20+ pieces/week)"]
  - key: team_size
    question: "How many people create content for the brand?"
    type: choice
    options: ["solo creator", "small team (2-5)", "large team (6-20)", "enterprise (20+)"]
  - key: industry_formality
    question: "What level of formality does the industry expect?"
    type: choice
    options: ["highly formal (finance, legal, healthcare)", "moderate (B2B SaaS, consulting)", "casual (consumer, lifestyle, social)", "mixed (varies by audience segment)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Brand mission and values"
      source: "brand-strategy/brand-positioning or user input"
      format: "text document or bullet list"
    - name: "Target audience profiles"
      source: "customer-research or user input"
      format: "persona documents or descriptions"
    - name: "Existing content samples"
      source: "current website, emails, social media"
      format: "5-10 representative text samples across content types"
  outputs:
    - name: "Tone of Voice Guide"
      format: "document (Google Doc, Notion page, or PDF)"
      description: "Complete guide with voice attributes, four tone dimensions with slider positions, do/don't examples per dimension, content type tone map, and reference writing samples"
    - name: "Tone Decision Matrix"
      format: "spreadsheet or table"
      description: "Quick-reference card mapping content types to tone positions for each dimension"
    - name: "Before/After Writing Samples"
      format: "document"
      description: "Rewritten versions of existing content demonstrating the defined tone, used for training and calibration"
  tools_required:
    - name: "Document editor"
      purpose: "Writing and formatting the tone guide"
      tier: free
      cost: "$0"
      alternatives: ["Google Docs", "Notion", "Confluence", "Word"]
    - name: "Spreadsheet"
      purpose: "Tone decision matrix and audit scoring"
      tier: free
      cost: "$0"
      alternatives: ["Google Sheets", "Excel", "Airtable"]
  credentials_needed: []
  estimated_duration: "4-8 hours for initial guide; 2-3 hours for review and revision"
  estimated_cost: "$0 (self-directed) to $2,000-5,000 (agency/consultant)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/brand-strategy/tone-of-voice-guide-template/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-11)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "business/brand-strategy/brand-messaging-framework/2026"
      label: "Brand messaging framework — building the positioning statement, value propositions, proof points and differentiators"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "The Four Dimensions of Tone of Voice"
    author: Nielsen Norman Group
    url: https://www.nngroup.com/articles/tone-of-voice-dimensions/
    type: technical_blog
    published: 2016-07-17
    reliability: authoritative
  - id: src2
    title: "The Impact of Tone of Voice on Users' Brand Perception"
    author: Nielsen Norman Group
    url: https://www.nngroup.com/articles/tone-voice-users/
    type: technical_blog
    published: 2016-07-31
    reliability: authoritative
  - id: src3
    title: "Voice and Tone"
    author: Mailchimp Content Style Guide
    url: https://styleguide.mailchimp.com/voice-and-tone/
    type: official_docs
    published: 2025-01-01
    reliability: authoritative
  - id: src4
    title: "Choosing the Right Voice and Tone for Your App"
    author: Slack
    url: https://api.slack.com/start/designing/voice-tone
    type: official_docs
    published: 2024-06-01
    reliability: authoritative
  - id: src5
    title: "Writing for GOV.UK"
    author: GOV.UK
    url: https://www.gov.uk/guidance/content-design/writing-for-gov-uk
    type: official_docs
    published: 2024-01-01
    reliability: authoritative
  - id: src6
    title: "The Voice of the Brand: 5 Principles for Great Marketing Copy at Slack"
    author: Slack Design
    url: https://slack.design/articles/thevoiceofthebrand-5principles/
    type: technical_blog
    published: 2023-09-01
    reliability: high
  - id: src7
    title: "How to Develop Your Brand's Tone of Voice"
    author: Backlinko
    url: https://backlinko.com/brand-tone-of-voice
    type: technical_blog
    published: 2025-04-01
    reliability: high
---

# Tone of Voice Guide Template

## Purpose

This recipe produces a complete Tone of Voice Guide that defines your brand's voice attributes and positions your tone across four measurable dimensions — formal/casual, serious/playful, respectful/irreverent, and enthusiastic/matter-of-fact. The output includes slider positions for each dimension, do/don't writing examples, a content-type tone mapping matrix, and before/after writing samples — ready for team distribution and AI tool configuration. [src1]

## Prerequisites

- [ ] **Brand mission and values** — documented positioning statement or at minimum a clear articulation of what the brand stands for and who it serves
- [ ] **Target audience profiles** — at least 2-3 audience personas with demographics, communication preferences, and emotional needs
- [ ] **Existing content samples** — 5-10 representative pieces across content types (marketing page, product UI text, support email, social post, error message)
- [ ] **Document editor** — Google Docs, Notion, Confluence, or Word for authoring the guide
- [ ] **Stakeholder access** — ability to get feedback from marketing, product, support, and leadership teams

## Constraints

- Voice is constant; tone adapts. The brand voice (personality attributes) never changes. Tone shifts based on context, audience emotional state, and content type. Conflating the two produces inconsistent writing. [src3]
- Abstract scales without concrete examples are worthless. Every tone dimension position must include at least 3 do/don't pairs with real sentences. [src1]
- Content type coverage must include at minimum: marketing copy, product UI microcopy, error messages, customer support, and legal/compliance text. Guides that only cover marketing fail at the first error message. [src4]
- Tone guides require validation against real content. Build the guide, then rewrite 5-10 existing pieces using it. If the rewrites feel wrong, the guide needs adjustment.
- Humor in error states is high-risk. Users in distress need clarity and empathy, not jokes. Tone adaptation must account for user emotional state. [src2]

## Tool Selection Decision

```
Which path?
├── Solo creator or small team, no existing guidelines
│   └── PATH A: Lean Guide — 1-page tone card + examples
├── Small-to-medium team, some informal guidelines
│   └── PATH B: Standard Guide — full document with all 4 dimensions
├── Large team, high content volume, needs governance
│   └── PATH C: Comprehensive Guide — full guide + decision matrix + training materials
└── Enterprise, multiple sub-brands or regions
    └── PATH D: Scalable System — modular guide + per-channel tone profiles + AI tool config
```

| Path | Tools | Cost | Time | Depth |
|------|-------|------|------|-------|
| A: Lean Guide | Google Doc | $0 | 2-3 hours | Core voice + 2 dimensions |
| B: Standard Guide | Google Doc + Sheets | $0 | 4-6 hours | All 4 dimensions + examples |
| C: Comprehensive Guide | Notion/Confluence + Sheets | $0 | 6-10 hours | Full guide + matrix + training |
| D: Scalable System | Notion/Confluence + AI tools | $0-5K | 10-20 hours | Modular, multi-brand, AI-ready |

## Execution Flow

### Step 1: Voice Attribute Discovery

**Duration**: 45-60 minutes
**Tool**: Document editor

Define 3-5 core voice attributes that describe your brand's personality. Voice is the constant — it does not change across content types or situations. [src3]

```
Voice Attribute Workshop:
──────────────────────────────────────────────────

1. List 5 adjectives that describe how your brand SHOULD sound:
   _________, _________, _________, _________, _________

2. List 5 adjectives your brand should NEVER sound like:
   _________, _________, _________, _________, _________

3. "We are _________ but not _________" (complete 3-5 pairs):
   • We are confident but not arrogant
   • We are _________ but not _________
   • We are _________ but not _________
   • We are _________ but not _________

4. If the brand were a person, how would colleagues describe them?
   _____________________________________________

Example outputs:
  Mailchimp: "plainspoken, genuine, has a sense of humor (dry, not slapstick)"
  Slack: "clear, concise, human — like a friendly, intelligent coworker"
  GOV.UK: "direct, informative, authoritative but never bureaucratic"
```

**Verify**: Voice attributes pass the "but not" test — each attribute has a clear boundary. "Friendly but not familiar" is specific. "Nice" is not.
**If failed**: If attributes are too generic (e.g., "professional, innovative, quality"), interview 3 team members about what makes the brand's communication different from competitors.

### Step 2: Position on the Four Tone Dimensions

**Duration**: 45-60 minutes
**Tool**: Document editor + visual slider

Position your brand on each of the four NN/g tone dimensions. Each dimension is a spectrum from 1-10. Most brands do not sit at extremes. [src1]

```
TONE DIMENSION POSITIONING
══════════════════════════════════════════════════

Dimension 1: FORMAL ←──────────→ CASUAL
Position: ___/10  (1 = very formal, 10 = very casual)

  1-3 (Formal): "We regret to inform you that your transaction
                  could not be processed at this time."
  4-6 (Neutral): "Your transaction didn't go through.
                  Here's what you can do."
  7-10 (Casual): "Hmm, that didn't work. Let's try again —
                   here are your options."

YOUR POSITION: ___
Example in your voice: _________________________________


Dimension 2: SERIOUS ←──────────→ PLAYFUL
Position: ___/10  (1 = very serious, 10 = very playful)

  1-3 (Serious):  "System maintenance is scheduled for Saturday
                    02:00-06:00 UTC. Save all work before this window."
  4-6 (Neutral):  "We're doing some maintenance this Saturday night.
                    Save your work before 2 AM UTC to be safe."
  7-10 (Playful): "We're giving our servers a spa day this Saturday.
                    Save your stuff before 2 AM and you're golden."

YOUR POSITION: ___
Example in your voice: _________________________________


Dimension 3: RESPECTFUL ←──────────→ IRREVERENT
Position: ___/10  (1 = very respectful, 10 = very irreverent)

  1-3 (Respectful): "We understand this process can be complex.
                      Our team is here to support you every step."
  4-6 (Neutral):    "This part's a bit tricky, but we've got
                      guides to walk you through it."
  7-10 (Irreverent): "Yeah, this part's kind of a pain.
                       But we've made it way less painful."

YOUR POSITION: ___
Example in your voice: _________________________________


Dimension 4: MATTER-OF-FACT ←──────────→ ENTHUSIASTIC
Position: ___/10  (1 = very matter-of-fact, 10 = very enthusiastic)

  1-3 (Matter-of-fact): "The report is ready for download."
  4-6 (Neutral):        "Your report is ready. Download it here."
  7-10 (Enthusiastic):  "Your report is ready! Check out the
                          insights we found."

YOUR POSITION: ___
Example in your voice: _________________________________
```

**Verify**: Each dimension has a specific numerical position AND at least one example sentence written in YOUR voice (not copied from templates above). Review with 2-3 team members — if positions differ by more than 2 points, discuss and align.
**If failed**: If the team cannot agree on positions, collect 10 existing content samples and independently rate each on all four dimensions. Average the ratings to find the de facto position.

### Step 3: Build Do/Don't Examples for Each Dimension

**Duration**: 60-90 minutes
**Tool**: Document editor

For each dimension, create 3-5 paired examples showing what your tone sounds like versus what it does not sound like. Use your actual products, features, and scenarios. [src3]

```
DO/DON'T EXAMPLE FORMAT
══════════════════════════════════════════════════

DIMENSION: [Formal/Casual — Position: 7/10 (casual)]

Context: Welcome email
  ✓ DO: "Hey [Name]! Welcome aboard. Here's the quick
         tour to get you started."
  ✗ DON'T: "Dear [Name], Thank you for registering your
            account. Please find enclosed your onboarding
            documentation."
  WHY: We're casual and direct. Formal language creates
       distance we don't want with new users.

Context: Payment failure notification
  ✓ DO: "Your payment didn't go through. Update your card
         details and we'll try again."
  ✗ DON'T: "Whoopsie! Your payment took a tumble.
            No worries though!"
  WHY: Even at position 7/10 casual, payment issues require
       clarity over personality. Tone shifts serious in
       high-stakes moments.

Context: Feature announcement
  ✓ DO: "You asked, we built it. [Feature] is live —
         here's how to use it."
  ✗ DON'T: "We are pleased to announce the general
            availability of [Feature] effective immediately."
  WHY: ________________________________________________

[Repeat for each dimension × 3-5 contexts]
```

**Verify**: Every do/don't pair references a real content type you actually produce. Generic examples ("We're excited to announce...") teach nothing.
**If failed**: If examples feel forced or unnatural, your dimension positions may be wrong. Return to Step 2 and re-evaluate.

### Step 4: Create the Content-Type Tone Map

**Duration**: 45-60 minutes
**Tool**: Spreadsheet or table

Different content types require different tone positions. An error message and a marketing email should not sound the same. Build a matrix mapping each content type to its tone shift from baseline. [src4]

```
CONTENT-TYPE TONE MAP
══════════════════════════════════════════════════

Baseline tone: F:7 S:6 R:4 E:7
(Formal/Casual, Serious/Playful, Respectful/Irreverent,
 Matter-of-fact/Enthusiastic)

Content Type        │ F/C │ S/P │ R/I │ M/E │ Notes
────────────────────┼─────┼─────┼─────┼─────┼──────────────
Marketing landing   │  7  │  6  │  4  │  8  │ Enthusiasm up
Blog post           │  8  │  6  │  5  │  7  │ Most casual
Social media        │  8  │  7  │  5  │  8  │ Most playful
Product UI copy     │  6  │  4  │  3  │  5  │ Clarity first
Onboarding flow     │  7  │  5  │  3  │  7  │ Warm, guiding
Error messages      │  5  │  2  │  2  │  3  │ Serious, clear
Support emails      │  6  │  3  │  2  │  5  │ Empathetic
Legal/compliance    │  2  │  1  │  1  │  2  │ Formal, precise
API documentation   │  3  │  2  │  2  │  3  │ Technical, direct
Internal comms      │  8  │  7  │  6  │  7  │ Most relaxed
Press releases      │  3  │  3  │  2  │  5  │ Professional
Sales proposals     │  4  │  3  │  2  │  6  │ Confident

Key insight: Tone adapts to user emotional state.
 • User is happy (success, onboarding) → enthusiasm OK
 • User is frustrated (error, support) → serious + empathetic
 • User is deciding (pricing, features) → clear + confident
 • User is worried (security, billing) → respectful + precise
```

**Verify**: Every content type in the map corresponds to content your team actually produces. Remove any rows for content types you do not create.
**If failed**: If you cannot determine the right tone for a content type, write the same message three ways (serious, neutral, playful) and ask 3 team members which feels right.

### Step 5: Write Before/After Samples

**Duration**: 60-90 minutes
**Tool**: Document editor

Take 5-10 real pieces of existing content and rewrite them using your new tone guide. This validates the guide and creates training material. [src7]

```
BEFORE/AFTER REWRITE FORMAT
══════════════════════════════════════════════════

Content type: [Error message]
Tone position: F:5 S:2 R:2 E:3

BEFORE (existing):
"Error 404: The requested resource was not found on this
server. Please verify the URL and try again."

AFTER (new tone):
"We couldn't find that page. It may have been moved or
the link might be outdated. Try searching for what you
need, or head back to the homepage."

WHAT CHANGED:
- Removed technical jargon ("Error 404", "requested resource")
- Added helpful next action (search, homepage)
- Shifted from passive to active voice
- Kept serious tone — no jokes in error states

──────────────────────────────────────────────────

Content type: [Feature announcement email]
Tone position: F:7 S:6 R:4 E:8

BEFORE (existing):
"We are pleased to announce the release of Version 3.2,
which includes several enhancements to the reporting module."

AFTER (new tone):
"Big news: reporting just got a major upgrade. Version 3.2
lets you build custom dashboards, export in 5 new formats,
and schedule automated reports. Here's what's new →"

WHAT CHANGED:
- Led with impact, not version number
- Casual direct address instead of corporate passive
- Specific benefits instead of vague "enhancements"
- Enthusiastic but specific — not empty excitement
```

**Verify**: Show before/after pairs to someone unfamiliar with the project. They should be able to identify the tone difference without explanation. If they cannot, the rewrites are too subtle.
**If failed**: If rewrites feel indistinguishable from originals, your tone dimensions may not be differentiated enough from your current voice. Revisit Step 2 and push positions further from center.

### Step 6: Assemble and Distribute the Guide

**Duration**: 30-60 minutes
**Tool**: Document editor

Compile all components into a single, accessible document.

```
TONE OF VOICE GUIDE — TABLE OF CONTENTS
══════════════════════════════════════════════════

1. Introduction
   - What this guide is (and isn't)
   - Voice vs. tone: the core distinction
   - How to use this guide

2. Our Voice
   - Voice attributes (3-5 "we are X but not Y" pairs)
   - Voice personality description (2-3 sentences)

3. Our Tone Dimensions
   - Dimension 1: Formal ←→ Casual [position + examples]
   - Dimension 2: Serious ←→ Playful [position + examples]
   - Dimension 3: Respectful ←→ Irreverent [position + examples]
   - Dimension 4: Matter-of-fact ←→ Enthusiastic [position + examples]

4. Do's and Don'ts
   - 3-5 do/don't pairs per dimension
   - Organized by content type where relevant

5. Content-Type Tone Map
   - Full matrix (content type × 4 dimensions)
   - User emotional state guidance

6. Writing Samples
   - Before/after rewrites (5-10 examples)
   - Organized by content type

7. Word Lists
   - Words we use (with context)
   - Words we avoid (with alternatives)

8. Quick Reference Card
   - One-page summary for daily use
   - Printable/pinnable format

DISTRIBUTION CHECKLIST:
  [ ] Share with all content creators
  [ ] Present to marketing/product/support leads
  [ ] Pin in team communication channels
  [ ] Add to onboarding materials
  [ ] Configure AI writing tools with tone settings
  [ ] Schedule quarterly review (set calendar reminder)
```

**Verify**: At least 3 people from different teams (marketing, product, support) have reviewed and confirmed the guide reflects the brand accurately.
**If failed**: If teams disagree on fundamental positions, run a calibration workshop: present 10 content samples, have everyone independently rate them, then discuss discrepancies.

## Output Schema

```json
{
  "output_type": "tone_of_voice_guide",
  "format": "document",
  "sections": [
    {"name": "voice_attributes", "type": "object", "description": "3-5 brand personality attributes with 'but not' boundaries", "required": true},
    {"name": "tone_dimensions", "type": "array", "description": "4 dimensions with position (1-10), rationale, and example sentences", "required": true},
    {"name": "do_dont_examples", "type": "array", "description": "3-5 do/don't pairs per dimension with context and reasoning", "required": true},
    {"name": "content_type_map", "type": "table", "description": "Matrix of content types × 4 dimensions with numerical positions", "required": true},
    {"name": "writing_samples", "type": "array", "description": "5-10 before/after rewrites demonstrating the tone in practice", "required": true},
    {"name": "word_lists", "type": "object", "description": "Preferred and avoided words with context", "required": false},
    {"name": "quick_reference", "type": "document", "description": "One-page summary card for daily use", "required": true}
  ],
  "expected_sections": "7",
  "sort_order": "logical flow (voice → dimensions → examples → application)",
  "deduplication_key": "voice_attributes"
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Voice attributes defined | 3 attributes | 3-5 with "but not" pairs | 5 with examples + anti-examples |
| Dimension coverage | 2 of 4 dimensions | All 4 with positions | All 4 with positions + do/don'ts |
| Do/don't examples per dimension | 1 pair | 3 pairs | 5+ pairs across content types |
| Content types mapped | 3 types | 6-8 types | 10+ with emotional state notes |
| Before/after samples | 2 rewrites | 5 rewrites | 10+ across all content types |
| Team validation | 1 reviewer | 3 reviewers (same team) | 3+ reviewers (cross-functional) |

**If below minimum**: The guide is too thin to be useful. Prioritize adding do/don't examples and content-type mapping — these are the sections teams actually reference daily.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Team cannot agree on dimension positions | Different mental models of the brand | Audit 10 existing content pieces — rate independently, average scores to find de facto positions |
| Do/don't examples feel artificial | Examples not grounded in real content | Replace generic examples with rewrites of actual content from your website, app, or emails |
| Guide is completed but nobody uses it | Distribution failure or guide is too long | Create a 1-page quick reference card and integrate into existing workflows (PR templates, Slack reminders) |
| Tone sounds inconsistent across channels | Content-type map not specific enough | Add sub-rows: split "marketing" into "landing page", "ad copy", "email campaign" with distinct positions |
| AI writing tools ignore the guide | Tone instructions not formatted for AI prompts | Extract key rules as explicit prompt instructions: "Write at formality level 7/10. Use contractions. No exclamation marks in error states." |
| New team members produce off-brand content | Onboarding gap | Add the guide to onboarding checklist, assign a "tone buddy" for first 2 weeks of content production |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| Document editor | Google Docs ($0) | Notion Team ($8/mo) | Confluence ($6/user/mo) |
| Content audit tools | Manual review ($0) | Grammarly Business ($15/user/mo) | Acrolinx/Writer ($50K+/yr) |
| Stakeholder workshops | Self-facilitated ($0) | External facilitator ($1K-3K) | Brand agency ($5K-15K) |
| AI tool configuration | Manual prompts ($0) | Jasper/Writer ($50-100/mo) | Custom fine-tuning ($2K+) |
| **Total for initial guide** | **$0** | **$1K-3K** | **$10K-20K** |

## Anti-Patterns

### Wrong: Defining voice and tone as the same thing
Many guides use "voice" and "tone" interchangeably, producing documents that either change personality per channel (inconsistent) or apply the same rigid tone everywhere (robotic error messages, inappropriately cheerful billing warnings). [src3]

### Correct: Voice is personality (constant); tone is mood (adaptive)
Define voice attributes once ("confident, warm, clear"). Then map tone adaptations per content type and user emotional state. Mailchimp's guide exemplifies this — their voice is always "plainspoken" and "genuine," but tone shifts from enthusiastic (onboarding) to serious (account issues).

### Wrong: Building scales without concrete examples
A slider showing "formal ←→ casual" at position 7 is meaningless without sentences showing what position 7 actually sounds like. Teams interpret abstract scales differently, producing inconsistent output. [src1]

### Correct: Every scale position paired with 3+ real examples
Each dimension position must include do/don't sentence pairs using your actual product names, features, and scenarios. Generic examples teach nothing.

### Wrong: Ignoring context-specific tone adaptation
Applying the same playful tone to a marketing landing page and a payment failure notification alienates users. Research shows that inappropriate humor in error states significantly damages brand perception. [src2]

### Correct: Map tone to user emotional state, not just content type
Error states require seriousness and empathy regardless of overall brand playfulness. Build a content-type tone map that accounts for the user's likely emotional state at each touchpoint.

## When This Matters

Use this recipe when a brand needs to create or overhaul its written communication guidelines. It produces a structured, actionable tone guide — not a branding document. The output is designed for daily use by writers, designers, product managers, and AI writing tools. Essential when scaling content production beyond one writer, onboarding new team members, or configuring AI content generation tools to match brand voice.

## Related Units

- [Brand Positioning Statement Builder](/business/brand-strategy/brand-positioning-statement-builder/2026) — prerequisite: defines what the brand stands for before defining how it sounds
- [Content Style Guide Builder](/business/brand-strategy/content-style-guide-builder/2026) — next step: grammar, formatting, and terminology rules complement tone
- [Brand Voice Audit Checklist](/business/brand-strategy/brand-voice-audit-checklist/2026) — evaluate existing content against the completed guide