> For the complete documentation index, see [llms.txt](https://university.obvious.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.obvious.in/product-design/microcopy/how-to-write-phrases.md).

# How to write phrases

## 👋 Introduction

Titles, buttons and placeholders are short strings of text that help the user navigate, take actions and enter information.

***

## 1️⃣ Title copy

A title is often the first and ***only*** thing a user reads. It tells the user where they are in the journey or what action they might need to take. You can write different kinds of titles:

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

> **Brand as title**—When you want to reinforce the brand image, use the brand name as the page title.

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

> **Content as title**—When the screen is based on content like an FAQ or a blog post, use the title of the content.

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

> **Task as title**—When the user has to take an action, describe the task. Always use a verb phrase.

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

> **Summarise actions**—When there are many actions for a user to take, the title should summarise all actions. These titles are often ambiguous. They can be a noun phrase or a verb phrase.

***

## 2️⃣ Button copy

Buttons allows the user to commit to an action or navigate to elsewhere. It should be unambiguous.

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

> **Make it specific**—Use 1-3 words to describe the action.

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

> **Make it simple**—Use words that users would say in a conversation. You can sit in on research calls with users, read support tickets by users to learn about the words users are most familiar with.

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

> **Make it consistent**—When you’re using single task titles, use the same verb in the button and the title.

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

> **Make it reassuring**—A click trigger is a short reminder next to the button. Think about what the user would be concerned about when taking this action and address it in the click trigger.

***

## 3️⃣ Placeholder copy

Input fields appear when the user has to enter information or run a search. The placeholder text appears inside the input field and helps the user enter accurate information. You can write different kinds of placeholder text:

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

> **Questions**—Ask your users a question to guide the entry. This works well for search and open-ended questions.

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

> **Categories**—If the user can search for a range of things, define the categories to help the user.

<figure><img src="/files/1NOU5qyxYtf9c2j0MQkP" alt=""><figcaption></figcaption></figure>

> **Examples**—An example or sample text can show your user the best way of using the field.

<figure><img src="/files/7b6oT2ecd9bheSXZaScb" alt=""><figcaption></figcaption></figure>

> **Prompts**—For text fields where the answer is long and the user will have to think, a guiding sentence can give them a starting point.

***
