Skip to content

Instantly share code, notes, and snippets.

@monodyle
Last active February 14, 2025 08:59
Show Gist options
  • Save monodyle/812192bbb0761ad8a3fbabb8d86e4faf to your computer and use it in GitHub Desktop.
Save monodyle/812192bbb0761ad8a3fbabb8d86e4faf to your computer and use it in GitHub Desktop.
Voice and Tone

Voice and Tone in Application Content

A guide to creating content that aligns with your application’s voice and tone.

Introduction

Voice and tone shape how users perceive your application. This guide provides principles for crafting consistent, user-centered content across all channels—from user interfaces to emails, social media, and beyond.

Who Should Use This Guide?

Anyone involved in customer-facing communications: content designers, engineers, product designers, blog contributors, product managers, marketers, and more.


Core Principles

To create content that empowers users, follow these principles:

  1. Offer solutions when users need them most.
  2. Simplify complexity into digestible pieces.
  3. Inspire action by encouraging exploration.

With clear language, a relatable tone, and a deep understanding of your audience, your content can guide users effectively—then step aside to let them succeed.


Personality Traits

Your application’s voice should reflect these traits:

  • Bold
  • Optimistic
  • Practical, with a wink

Bold

  • Motivate users by offering best practices and actionable guidance.
  • Provide accurate information to help users make informed decisions.
  • Understand their struggles and deliver solutions that empower progress.

Optimistic

  • Highlight key benefits that matter most to users in the moment.
  • Build confidence by focusing on clarity and consistency.
  • Create seamless experiences across all touchpoints.

Practical, with a Wink

  • Be direct and concise.
  • Look for opportunities to offer helpful nudges.
  • Use clear, inclusive language that builds trust and belonging.

Voice and Tone Principles

Adjust your tone based on the user’s context, emotional state, and journey stage.

1. Inform to Build Trust

  • When to use: When users feel confused, apprehensive, or frustrated.
  • How: Be prescriptive and clear. Guide users through their journey with humble, warm language.
  • Examples: Error messages, onboarding tooltips.

2. Empower to Inspire Action

  • When to use: When users feel confident or curious.
  • How: Educate with empathy. Suggest best practices and next steps.
  • Examples: Feature modals, advanced tooltips.

3. Encourage Along the Path

  • When to use: When users feel uncertain or unsupported.
  • How: Acknowledge challenges and offer upbeat guidance.
  • Examples: Inline hints, progress notifications.

4. Motivate by Showing Possibilities

  • When to use: When users feel ambitious or inspired.
  • How: Highlight success stories and expert strategies.
  • Examples: Onboarding spotlights, pro tips.

5. Satisfy by Meeting Expectations

  • When to use: When users feel overwhelmed.
  • How: Deliver straightforward answers without fluff.
  • Examples: Warning messages, instructional text.

6. Delight with Unexpected Moments

  • When to use: When users feel successful or relieved.
  • How: Add subtle, playful touches—like celebratory microcopy.
  • Examples: Success animations, post-task rewards.

Applying Tone Contextually

Use these questions to refine your tone:

  • Emotional State: What is the user feeling at this point in their journey?
  • Enhance Positivity: How can your tone amplify moments of success?
  • Diffuse Frustration: How can your tone alleviate pain points?

Adjustments might include:

  • Boldness: Scale from prescriptive (less bold) to empowering (more bold).
  • Optimism: Balance reassurance with enthusiasm based on context.
  • Practicality: Prioritize clarity but add warmth where appropriate.

Final Tips

  • Be Consistent: Align vocabulary and messaging across all products.
  • Stay Human: Write like a knowledgeable teammate, not a robot.
  • Test and Iterate: Gather feedback to refine your voice over time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment