---
title: Content Strategy
slug: books/technical-writing/content-strategy
icon: 📝
createdAt: 2025-04-29T17:04:01.617Z
---

Starting out a documentation project can be overwhelming, but the process can be broken down into:

::::LinkArray
:::LinkArrayItem
👂

[Audience Analysis](#)

Defining the audience needs.
:::

:::LinkArrayItem
🕵️‍♀️

[Research](#) &#x20;

Understanding the to
:::

:::LinkArrayItem
✍️

[Writing](#)

Writing the actual documentation, while following a few basic principles.
:::

:::LinkArrayItem
🧐

[Reviewing](#)

Checking the content of the documentation to make sure it's accurate.
:::

:::LinkArrayItem
🧪

[Testing](#)

Checking the technical integrity of the documentation.
:::

:::LinkArrayItem
🚀

[Delivering](#)

Making the documentation available to end-users.
:::
::::

In a documentation context, a project doesn't have to be something big, like an entire help system. The principles apply even when you are just making small updates to a legacy documentation set.

:::BlockQuote
The next sections

**dive deeper&#x20;**

<u>*into each topic*</u><u>**.**</u>
:::

