Content Design
Content design uses evidence about user needs to plan, structure, write, and maintain content that helps people complete a task.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/content-design/
01What 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.[1][2][3]
- 01Understand the needAudience, task, evidence, language, and barriers
- 02Model the journeyInformation order, decisions, channels, and dependencies
- 03Design contentPlain language, labels, guidance, errors, and alternatives
- 04Test in contextComprehension, task success, accessibility, and trust
- 05Publish + governOwnership, metadata, approvals, and source of truth
- 06Measure + maintainSearch, feedback, policy change, and content decay
Content design is not late-stage copy polishing; policy, interface, service, search, accessibility, and governance all shape whether words help.
02Why 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.
03When 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.
04How it works
- Describe the user, situation, need, and intended outcome using research rather than an assumed publishing request.
- Map the journey and decide whether content, interaction, service change, or no new material is the best response.
- Choose the smallest useful format and structure information around priority questions and decisions.
- Draft in plain language, prototype within the real interface, and test comprehension and task completion.
- Assign ownership, review dates, evidence signals, and retirement criteria so the content remains accurate.
05A 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.
06Where 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.
07Sources
- Understand Content DesignGovernment Digital Service · Government guidanceUnderstand Content Design
- Identify User NeedsGovernment Digital Service · Government guidanceIdentify User Needs
- Create a Clear Structure for Your ContentGovernment Digital Service · Government guidanceCreate a Clear Structure for Your Content