# Content Design

Content design uses evidence about user needs to plan, structure, write, and maintain content that helps people complete a task.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/content-design/>)

## What it means

Content design is the practice of deciding what content a service should provide, in what form, and at what point in a user journey. It begins with a verified need rather than a request to publish words. Content designers shape structure, language, format, links, and governance while working with design, research, policy, and technical constraints.

## Why it matters

Content is often the interface through which users understand choices, provide information, and recover from problems. Designing it as part of the service prevents duplicated pages, reduces reading effort, and connects organizational knowledge to real tasks. It also gives teams criteria for deleting or declining content that does not serve a clear need.

## When to use it

Use content design when creating or improving services, guidance, onboarding, forms, support, notifications, or transactional journeys. It is particularly valuable when stakeholders propose a page before defining its purpose, when users contact support despite abundant content, or when the same subject is explained inconsistently.

## How it works

1. Describe the user, situation, need, and intended outcome using research rather than an assumed publishing request.
2. Map the journey and decide whether content, interaction, service change, or no new material is the best response.
3. Choose the smallest useful format and structure information around priority questions and decisions.
4. Draft in plain language, prototype within the real interface, and test comprehension and task completion.
5. Assign ownership, review dates, evidence signals, and retirement criteria so the content remains accurate.

## A practical example

A city receives requests for a long “moving home” guide. Research shows residents mainly need to update council tax, parking permits, and school records. The team creates a short task-based hub, reuses existing transactions, explains required evidence before each start button, and removes duplicate departmental pages.

## Where it breaks

Not every outcome can be improved through wording or structure; policy, process, and system constraints may be the real problem. User-needs statements can become speculative if they are not connected to evidence. Content design also requires ongoing authority to update or remove material—without governance, even well-tested content decays.

## Common mistakes

- Accepting “we need a page” as the need.
- Writing polished copy before understanding the journey and service constraints.
- Publishing without an owner, review trigger, or plan to remove obsolete content.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/content-design/#visualization-content-design>)

## Sources

1. [Understand Content Design](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/plan-manage-content/understand-content-design/>) — Government Digital Service · Government guidance
2. [Identify User Needs](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/plan-manage-content/identify-user-needs/>) — Government Digital Service · Government guidance
3. [Create a Clear Structure for Your Content](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/writing-guidelines/clear-structure/>) — Government Digital Service · Government guidance

## Related topics

- [UX Writing](<https://wiki.soroush.uk/topic/ux-writing/>)
- [Plain Language](<https://wiki.soroush.uk/topic/plain-language/>)
- [Content Hierarchy](<https://wiki.soroush.uk/topic/content-hierarchy/>)
