The annotated journal
Web content roles, and which one your problem needs
Content roles are a checklist of responsibilities someone must own, whether or not they are job titles. The decision tree from symptom to role, each role compressed to what it owns and the signs it is missing, and how small teams combine roles without dropping work.

Roles start as responsibilities
Every content role started as a responsibility somebody had to own. Editor, strategist, content designer: each one exists because a kind of work goes wrong when nobody owns it. Large teams give the responsibilities separate job titles. Small teams give several of them to the same person. The failure mode is identical in both: a responsibility that everyone assumed someone else held.
So read the roles below as a checklist rather than an org chart. For each one, the question is whether a named person owns it today.
Which role your problem needs
The way into content roles is not the titles. It is the problem you have noticed:
| The problem you notice | The role that owns it | Where it is covered |
|---|---|---|
| Nobody can say what we publish next, or why | Content strategist | The strategist’s responsibilities |
| Pages do not answer what people actually ask, and support absorbs the difference | Content designer | This page |
| Good pages are invisible in search for the terms that matter | SEO content strategist | The SEO specialism |
| Quality swings wildly between pages | Editor | This page |
| The same content exists in 3 places with 3 different versions of the truth | Strategist and editor together | This page |
| Nobody can connect any of it to a business result | Strategist’s measurement plan | The strategist’s responsibilities |
One boundary is worth drawing. If the problem is who to involve in a piece of work rather than what to publish, that belongs to a different set of roles: stakeholder engagement roles, covered in the engagement cluster.
What each role owns
| Role | What it owns | Signs it is missing |
|---|---|---|
| Content strategist | What gets published, for whom, to serve which decision, and how it is measured | Random publishing; content nobody can justify; no measurement |
| Content designer | Meeting identified user needs with the clearest content, in the right format and place | Support queries a page should have answered; duplicated journeys |
| SEO specialist | Search visibility: technical health, keyword targeting, on-page quality | Pages that answer their question but rank nowhere |
| Editor | Consistency of quality, tone and accuracy | Wild swings between pages; errors reaching production |
| Writer and copywriter | Drafting that serves the strategy and the user need | Strategy that never becomes drafts |
| Designer and developer | The forms content takes: layout, interfaces, the build that carries it | Content crammed into unsuitable templates |
| Analyst | The numbers that connect content to decisions | Dashboards nobody uses; activity counts only |
The writer and copywriter distinction is intent. Writers inform; copywriters persuade toward an action. Both serve the strategy and the user need, and the best ones swap hats without arguing about the boundary.
The content designer, defined properly
The term content design comes from government digital teams, and the clearest definition is the public one. GOV.UK’s publishing guidance is direct: "Good content design helps people quickly find out what they need to know or do." The practice starts from a user need, meaning what a specific person is trying to do, and asks what the smallest piece of content that meets it looks like, in which format, published where. The role is wider than writing: in service teams, content designers work end to end, from a single page to the whole journey. The full guidance is understand content design on GOV.UK.
How small teams hold several roles
Most teams under 20 people give one person several roles. That works. What does not work is the silent version, where combining roles quietly drops one of them: the strategist work happens, the editing does not, and nobody notices until quality swings. Name the hats. "This quarter you are strategist and editor, and editing happens on Thursdays or it does not happen." Explicit combinations survive. Implicit ones decay.
None of these roles needs a specific degree. The analyst role is the one most often credentialised, and the credential matters less than the habit: a number connected to a decision, repeatedly.
Which combinations hold, and which one does not
Not all pairs of hats sit equally well on one head. Most combine without trouble. One does not, and it is the pair teams reach for first.
| Combination | How it holds |
|---|---|
| Strategist and editor | Holds well. Both judge work against the same standard, and the strategy makes the editorial calls easier |
| Strategist and analyst | Holds well. The person who decides what to publish is the right person to want the number |
| Content designer and writer | Holds well. Same craft at different altitudes |
| SEO specialist and strategist | Holds, with a caution. The distribution argument starts to drive the publishing decisions rather than serve them |
| Designer and developer | Holds. A common and productive pairing |
| Writer and editor, on the same piece | Does not hold |
The last row is the one worth protecting. Editing your own draft is a different cognitive task from writing it, and the writer already knows what the sentence was supposed to mean, which is precisely the knowledge an editor must not have. A writer can edit somebody else's work well and their own work poorly on the same afternoon.
Where a team is too small to separate them, the workable substitutes are distance and a checklist. Leave the draft overnight so you return to it with less memory of your intent, and read it against a written standard rather than against your own judgement, because the standard is the part that does not drift.
The order to fill the roles in
A team that owns none of these should not hire in the order of the table above. The sequence that tends to work runs strategist, then editor, then whichever specialist the recurring problem names.
The strategist comes first because every other role needs the decisions the strategist makes: the designer needs to know which need, the writer needs to know for whom, the analyst needs to know what counts as working. Hiring a writer into an organisation with no strategy produces prolific, well-written content that nobody can justify.
The editor comes second because that is the point at which volume starts to outrun consistency. Specialists come third, and which one you need is a question the first table answers rather than a matter of preference.
One adjacent role belongs to a different discipline: the marketing operations owner, who makes the content machinery run. The role of marketing operations management covers it as its own subject.
Name an owner for each gap
Write down the last 3 content problems you complained about. Find each in the first table. Beside it, write the name of the person who owns that responsibility now. Blank names are your gap, and the next hire, contractor or reassigned hat fills it deliberately.