# How to create a voice

## 👋 Introduction

To understand voice, think of the product as a person. How would that person speak? This is the product’s voice. A product’s voice is how the product speaks to the user across *all* touch points.

<figure><img src="/files/vh0tlbBuQTKU6QcuUT1k" alt=""><figcaption></figcaption></figure>

***

## 1️⃣ Understand your product

Go back to the roots of your product, and your users. Painting a vivid picture and thinking deeply about how you want your users to feel will help you craft a compelling voice for your product.

### What does the product do?

<figure><img src="/files/vUs1pRS7cVymdiArM4NB" alt=""><figcaption></figcaption></figure>

> Describe the details of your product.

### What does the product solve?

<figure><img src="/files/VDSNCPwPXwb82j3B4Zjq" alt=""><figcaption></figcaption></figure>

> Describe the problem your product tackles in 50 words.

### Who is the product for?

<figure><img src="/files/Yd2ravn8QvFU7Wh1seIh" alt=""><figcaption></figcaption></figure>

> Think about: Age, gender, location, level of education, tech savviness.

### How do you want users to feel?

<figure><img src="/files/INJWnyihTlV5smkBAFAE" alt=""><figcaption></figcaption></figure>

> Think about how the user should feel before using the product and after using the product.

### If the product were a person, who would it be?

<figure><img src="/files/dW3y1I17pPZQKyEsTe5h" alt=""><figcaption></figcaption></figure>

> Describe a person who shares the values of your product. Don’t think of your “ideal” user.

***

## 2️⃣ Create voice guidelines

Use the product understanding to build voice qualities for your product.

### Pick adjectives

<figure><img src="/files/l3oS9TEDZAtIVltUwIF1" alt=""><figcaption></figcaption></figure>

> When your users describe your product, what adjectives do you want them to use?

<figure><img src="/files/wxL4LEnUgv8A4s4DOYsn" alt=""><figcaption></figcaption></figure>

> List 6-9 adjectives. It’s okay if some are synonymous. These are your voice qualities.

***

### Make it specific

<figure><img src="/files/V55dp01Ll7KjKHzSKB1H" alt=""><figcaption></figcaption></figure>

> For each voice quality, think about how you **don’t** want to write.

<figure><img src="/files/Yvac1yVibuVyIOGHo5St" alt=""><figcaption></figcaption></figure>

> Create a spectrum that is a helpful contrast, but not a direct antonym.

<figure><img src="/files/oR1lkazr071UoMkyOdkh" alt=""><figcaption></figcaption></figure>

> Your product may not always be encouraging or comforting. Place pins on the spectrum to capture nuance in your product’s voice quality.

***

### Create examples

> Having real examples of copy in the product enrich your voice guidelines👇

<figure><img src="/files/jUI8zhX6ThW6j4DeeRbQ" alt=""><figcaption></figcaption></figure>

> **Bonus example!** See how Duolingo has created examples for their [voice qualities](https://design.duolingo.com/writing/voice#expressive) 👇

<figure><img src="/files/MQAPfXfgmIzogqnQJVIT" alt=""><figcaption></figcaption></figure>

&#x20;

{% hint style="warning" %}
**Your product may have multiple user segments.**

For example, Swiggy communicates with consumers, driver partners and business owners. Airbnb communicates with hosts and travellers. In such a case, you may want to create a distinct voice for each user segment. It’s natural for 1-2 voice qualities to overlap between segments, since they share the brand.
{% endhint %}

***

## 3️⃣ Use guidelines effectively

<figure><img src="/files/6JEu8abrF21pGMuxE4Lm" alt=""><figcaption></figcaption></figure>

> **Use it to write new text** for a flow or screen that sounds like your product.

<figure><img src="/files/DKBnlAbC1FO3ns2LnUPu" alt=""><figcaption></figcaption></figure>

> **Use it for feedback.** Use the voice guidelines as a common vocabulary.

<figure><img src="/files/55g5NIvJtDW1FdVBUJ6q" alt=""><figcaption></figcaption></figure>

> **Use it to onboard teammates.** The voice guidelines are a great resource for a new team member to write copy in the product’s unique style.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://university.obvious.in/product-design/microcopy/how-to-create-a-voice.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
