Content Design
Date: 2026-08-17
Treating content as something designed to meet a need, not written to fill a space. The discipline’s contribution is deciding what to say and whether to say it at all — which frequently means removing content rather than improving it.
Content design is the practice of determining what content a user needs, in what form, at what point — starting from the need rather than from the format.
Content writing — fill this box well.
Content design — does this box need to exist, and what does the person actually need here?
Start from the need, not the page
WRONG "we need a returns page"
→ write a returns page
RIGHT "what do people need to know
about returns, and WHEN?"
→ 1 line on the product page
→ 1 line in checkout
→ the detail on a page
→ the process in the
confirmation email
The same information, placed where the question is asked. A comprehensive returns page nobody reads is worse than one sentence at the moment of hesitation — Trust Signals.
Content is an interface
The distinction that makes this a design discipline: content is not decoration on the interface, it is the interface.
THE LABEL on a button IS the control
THE ERROR message IS the recovery
THE PRODUCT description IS the
decision support
THE CONFIRMATION IS the reassurance
Which is why content decisions are made with the design rather than after it — a layout designed around lorem ipsum will not fit the real content, and the real content will be forced to fit — Microcopy.
The practice
1 IDENTIFY THE NEED
what question is being asked here?
← from research, search logs,
support tickets
2 DECIDE WHETHER TO ANSWER IT HERE
right place? right moment?
3 DECIDE THE FORM
sentence · list · table · diagram
· video
4 WRITE IT PLAINLY
— Readability
5 TEST WHETHER IT WORKS
can people find and act on it?
6 MEASURE AND MAINTAIN
See: Readability
Step 2 is where most of the value is and the step most often skipped. A lot of content exists because someone asked for a page, not because anyone needed one.
Structure is content design
HEADINGS navigation for skimmers and
screen readers
→ descriptive, not clever
— Screen Readers
FRONT-LOADING the important word first
people read the first two
words of a line
— Reading Behaviour Online
CHUNKING one idea per paragraph
LISTS for anything enumerable
TABLES for anything comparable
→ specifications should
never be prose
See: Screen Readers · Reading Behaviour Online
Product specifications written as a paragraph is the most common content-design failure in retail, and converting it to a table takes minutes.
Deciding not to write
The most under-used move:
REMOVE INSTEAD OF IMPROVING
a paragraph nobody reads
a page with no traffic
an FAQ answering questions nobody
asks
boilerplate reassurance
REPLACE PROSE WITH STRUCTURE
a spec table
a comparison
a diagram
FIX THE THING INSTEAD
an FAQ explaining a confusing
process is a design problem being
documented rather than solved
An FAQ is frequently a list of design failures. “Why can’t I change my delivery address?” answered in an FAQ is a question that should have been answered by making it changeable — Error Prevention and Recovery.
Evidence to work from
SITE SEARCH the words they use, and
what they can't find
— Search and Findability
SUPPORT TICKETS the questions your
content didn't answer
PRODUCT Q&A objections your
descriptions missed
REVIEWS the vocabulary customers
actually use
ANALYTICS which content gets read
RESEARCH — Usability Testing
See: Search and Findability · Usability Testing
Support tickets are the highest-value input — every recurring ticket is content that doesn’t exist, isn’t findable, or isn’t clear.
Measuring it
TASK COMPLETION can they find the answer
and act on it?
← the real measure
SUPPORT VOLUME by topic, before and
after
SEARCH REFINEMENT searching again means
the first answer failed
SCROLL AND is it being read
ENGAGEMENT
CONVERSION for decision-support
content
Support volume by topic is the most persuasive measure internally, because it converts content work into a cost saving that finance recognises.