# How to write well

## 👋 Introduction

All text in digital products is microcopy. When used well, it reduces confusion, creates confidence, provides feedback, encourages actions, improves conversions and reinforces brand familiarity.

***

## 1️⃣ Good copy in the wild

You will find microcopy everywhere in interfaces—button labels, error messages, tooltips, onboarding instructions, form field placeholders, and even the labels on navigation elements. Here’s a small curation.

<figure><img src="https://1713760500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5WvjZe1MeyuSKcswT743%2Fuploads%2FnKgq2hk8efU0GcnqKK6z%2Fmicrocopy1.jpg?alt=media&#x26;token=16b302a4-97b0-465b-88d9-60314a6c8770" alt=""><figcaption></figcaption></figure>

> During onboarding, titles and buttons invite the user to explore and get started. In user guides, step-by-step breakdown of features helps users learn how to use the product.

<figure><img src="https://1713760500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5WvjZe1MeyuSKcswT743%2Fuploads%2Fpo5Zhju1iyu2rSTFKtrq%2Fmicrocopy3.jpg?alt=media&#x26;token=54738f45-6c3a-49b7-af5b-6b87370799a5" alt=""><figcaption></figcaption></figure>

> On forms, field titles, placeholders and descriptions assist users to fill the form correctly in fewer attempts. On search pages, category titles and labels make the content structure visible to the user.

<figure><img src="https://1713760500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5WvjZe1MeyuSKcswT743%2Fuploads%2F4C4IcirKsGk99edZTPMd%2Fmicrocopy2.jpg?alt=media&#x26;token=9ca745b2-e415-4c3b-934e-b79122383993" alt=""><figcaption></figcaption></figure>

> On bottom sheets, titles, instructions and feedback explain what happened, what to do differently next time, available next steps, and what to expect on picking an option.

***

## 2️⃣ The 4-step edit

Writing good copy can be easy. This exercise will get you to 80% of the way really quickly. Use it to write everything from short phrases for buttons, complete sentences for error messages, and entire paragraphs for how-to guides.

### **Make it purposeful**

Put down everything important and relevant for the user. Leave out nothing. It’s okay if it’s long.

### **Make it concise**

Rewrite the message to be shorter without losing the essence. Decide if the focus is the verb or the noun and lead with that.

### **Make it conversational**

If the message sounds abrupt or machine-like, rewrite it like a person would say it. Writing in active voice helps.

### **Make it clear**

Finally, check if the intended message might be confusing to users in any way. Testing with teammates and users helps.

<figure><img src="https://1713760500-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5WvjZe1MeyuSKcswT743%2Fuploads%2Fh7q1DOuTsdXZwPJTVwZC%2F125.jpg?alt=media&#x26;token=2ae60eff-20c5-4b3d-8b01-1405cb063ec8" alt=""><figcaption></figcaption></figure>

***


---

# 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-write-well.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.
