A content designer works out what people need to know or do, then designs the content that gets them there: deciding whether something should be a page, a table, a form or nothing at all, and writing, testing and refining it. Content designers usually work in multidisciplinary teams with user researchers, service and interaction designers, developers and subject matter experts. They’re accountable for whether the content works for the people using it, not only whether it reads well.
The title spread from UK government digital teams in the early 2010s and is now common in product companies, charities and public services in many countries. It overlaps with UX writer, and many organisations use the two interchangeably. Levels are often well defined: the UK government framework runs from associate content designer to head of content design, with responsibility widening from individual pieces of content to whole services and teams.
Why an organisation needs a content designer
Organisations without content designers tend to publish what they’re asked to publish. A department requests a page, someone writes it and the site gains one more thing to maintain, whether or not anyone needed it. A content designer changes the starting point. They ask what problem the content is meant to solve, look at the evidence and push back when the answer is a different format, a simpler process or no content at all. That challenge is the most valuable part of the job, and the part most easily lost when the role is treated as a writing service.
The need is clearest wherever people come to content to get something done: applying, paying, booking, checking whether they’re eligible or recovering when something goes wrong. Support calls about things the website should have explained are often the first sign. The role depends on joining work early, with access to user research and enough standing to influence the service as well as the words. Brought in at the end to tidy up the copy, even an excellent content designer becomes an expensive proofreader.
How AI changes the role
Content designers have moved quickly into AI work, partly because so much of it is language. In product teams they write the instructions that shape how assistants respond, design what happens when an assistant can’t help and test generated answers against what users need. In services and publishing they increasingly design for two kinds of reader: people, and the systems that retrieve, summarise and answer from their content. The UK government’s 2026 update to the content designer skills added content management and architecture as the one skill unique to the role, framed broadly enough to cover reuse anywhere from paper letters to AI interfaces.
The risk for the role lies in a misunderstanding: the idea that anyone with an assistant can now do content design, or that one designer with AI can do the work of several. Andrew Tipp argues that this mistakes what the job is, because research, judgement and the relationships needed to change a service don’t compress the way drafting does. A job description might now include designing for AI-generated or AI-retrieved content, evaluating responses against user needs and structuring content for reuse, alongside research, testing and accessibility.
Questions people ask
- What do the different levels of content designer do?
Junior content designers usually work on defined pieces within a team, with their work reviewed. Mid-level designers take responsibility for whole journeys or products and work directly with research and policy colleagues. Senior and lead designers set standards, review others’ work and shape services across teams, and a head of content design builds the profession within an organisation. Boundaries vary, so describe the scope of decisions rather than relying on the title.
- Where should content designers sit?
Usually in the teams building the products and services they work on, with a central lead or community that keeps standards consistent. Embedded designers know the service; a central lead stops each team inventing its own conventions.
- How many content designers do we need?
It depends on how many services or products are changing at once and how much content they involve. In an organisation with several product or service teams, embedding a content designer in each is a sensible starting point; a small charity might begin with one designer working across its most-used journeys. Watch for designers spread so thinly that they only ever review other people’s copy.
- What background makes a good content designer?
Journalism, editing, copywriting, policy and research roles all lead into it. What matters most is comfort with evidence: someone who will happily abandon a well-written draft because testing shows it isn’t working.
Learn more
- Content designer – the UK government’s description of six content designer levels, from associate to head of content design; one employer’s framework, but a detailed starting point for job descriptions.
- Updating the skills content designers need in government – an account by content design leads from MOJ, DWP, GDS and HMRC of how the role’s skills were rewritten, including the new skill in content management and architecture.
- The future of content design in an AI world – Andrew Tipp’s essay arguing that the real threat to content designers is the belief that fewer of them are needed, or that anyone with an assistant can do the job.