> 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-well.md). # 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.
> 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.
> 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.
> 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.
***