# Content design

Content design is a way of thinking about the content in a product or service that puts the reader or user’s needs first.&#x20;

It is more than just writing and editing. We use the tools of user-centred design to understand the user’s needs before creating any content at all.

We organise and label content, to help people find what they need in the place they expect it to be. We write clear and simple instructions for the steps in a service. Or provide advice and supporting information to help people with a specific problem. We don’t just work with words. We choose pictures, script videos, or create diagrams if those are the best ways to convey information for our users.

We’re strategic thinkers, who explore how best to share information.  So don’t be surprised if we ask lots of questions. &#x20;

We make content that is:&#x20;

* **Findable** – Is it where the user expects it to be? Can they find it when they search for it?&#x20;
* **Useful** – Does it serve a purpose?&#x20;
* **Actionable** – Does a user understand what to do next?&#x20;
* **Clear** – Can it be misunderstood?&#x20;
* **Accessible** – Can everyone use it, no matter what their background, knowledge, and what assistive technologies they use?&#x20;

<figure><img src="/files/fITtyYrY5dlNVIyTcN7s" alt="&#x22;&#x22;" width="563"><figcaption></figcaption></figure>

For example, when designing a website to sells book online, the content designer would start by structuring the architecture of the site to make sure information was where the users would expect it to be. And then we’d look at categorising books. We might even specify the use of icons to categorise genres or audiences and make the search easier for the buyer.

We’d also make sure the instructions are clear on the website and write book descriptions, so people better understand what they’re considering buying. We’d look at words on buttons and help text in forms to best guide the purchaser. Everything works to make the buying process easier.


---

# 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://playbook.necdigitalstudio.com/capabilities/user-centred-design/design/content-design.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.
