> For the complete documentation index, see [llms.txt](https://www.uxlibrary.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.uxlibrary.org/explore/ux-writing/books.md).

# Books

Improve your design workflow with our curated books on UX writing.

## Strategic Writing for UX by Torrey Podmajersky

When you depend on users to perform specific actions--like buying tickets, playing a game, or riding public transit--well-placed words are most effective. But how do you choose the right words? And how do you know if they work? With this practical book, you'll learn how to write strategically for UX, using tools to build foundational pieces for UI text and UX voice strategy.

{% embed url="<https://www.goodreads.com/book/show/44144500-strategic-writing-for-ux>" %}

## Microcopy by Niaw de Leon

In this book, you will learn how:&#x20;

* One retail firm increased its monthly revenues by $25,000,000 by changing one word&#x20;
* A website prevented hundreds of credit card billing errors using a single sentence
* An enterprise chat app used playful microcopy to grow to a $3.8B valuation

{% embed url="<https://www.goodreads.com/book/show/35151263-microcopy>" %}

## Nicely Said by Nicole Fenton & Kate Kiefer Lee

Learn from real-world examples and interviews with people who work in the world of UX writing and content strategy every day: Kristina Halvorson of Brain Traffic, Tiffani Jones Brown of Pinterest, Gabrielle Blair of Design Mom, Mandy Brown of Editorially, Randy J. Hunt of Etsy, Sarah Richards of GOV.UK, and more.

{% embed url="<https://www.goodreads.com/book/show/18847936-nicely-said>" %}

## Conversational Design by Erika Hall

In this book, research and information design expert Erika Hall explains what makes an interaction truly conversational and how to get more comfortable using language in design. From understanding the human interface, to effectively using the power of personality, to getting it all done, you’ll find out how the art of communication can elevate technology.

{% embed url="<https://abookapart.com/products/conversational-design>" %}

Find more books [here](https://blog.usejournal.com/a-mega-list-of-ux-writing-resources-d9f200d6dfde).

![](https://4049242671-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LXimC0bwl-iiW3Q7dFD%2F-LyTzBO9bfs7Jhqr4Q4d%2F-LyTzMN_2df8kzPj8tGD%2FBookmark.png?alt=media\&token=51723bee-09ec-4b36-8f46-b42c757a050f)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.uxlibrary.org/explore/ux-writing/books.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
