From editorial to content design:
Insights from senior content designers

One of the people I spoke with said: “Content decisions in product teams are downstream of strategy.”

For the most part, I had been thinking about editorial and product content as adjacent crafts. They are. But the comparison hides what makes them different.

Editorial work is already shaped by purpose, audience and constraint. No serious editor writes in a vacuum. The difference in product is the chain.

In product, language sits at the end of a longer line of decisions: a business opportunity, a product objective, a user need, a measured behaviour, a hypothesis, a constraint. By the time language enters the conversation, most of the meaningful choices have already been made, or are being made in parallel by the people the writer needs to be in the room with.

That changes the questions the writer is asking.

Editorial work asks: Is this clear? Is this coherent? Does this communicate?

Product writing adds: Does this reduce uncertainty? Does this help someone complete a task? Does this earn trust? Does this contribute to the outcome the team is trying to produce?

The concern for people is the same, but the decision environment is different. The writer needs to be in the room earlier, closer to where the decisions get made.

One question I led with in every call was: where does editorial experience actually carry into UX? The answer was encouraging.

Audience awareness, precision, structure, judgment, the ability to compress complexity without losing meaning — none of that is redundant. Editorial gives you principles for making decisions. What changes is what gets built on top.

Clarity becomes connected to behaviour: not whether the sentence is clean, but whether it moves someone forward.

Structure becomes systemic: how language fits into a flow, a journey, a system of patterns that other people will inherit.

Judgment becomes evidentiary: tied to research, A/B tests, observable outcomes, not just to taste.

Audience becomes empirical: shaped by user research instead of by intuition and persona work.

Publishing becomes product thinking: language as part of a longer-lived asset, not as a finished artefact.

One of the people I spoke with framed his answer around the name of the discipline itself. Content design is an intentional combination of content and design. Writing is the tool the content designer uses the same way shapes and colour are tools for a visual designer. Andy Welfle’s book Writing Is Designing has become a useful formulation of that idea for that reason. Writing is not adjacent to design. It is design, expressed in language.

That framing also shaped how he answered my more practical question: if you were hiring for a content design role, would you weight a strong writing background or a strong UX background?

His answer was unhesitating. You will not often find a content designer who has spent equal time as a writer and as a UX professional. The most experienced practitioners he had worked with came from long careers in writing: editing, journalism, teaching English, and at some point redirected those hard-earned skills into the emerging field of UX.

A solid editorial foundation, he said, is an addition to that skill set, not a detraction from it.

One mentor framed content design as working across information architecture, communication objectives, usability and business context all at the same time. That formulation stayed with me. It positions language as part of a system rather than as a craft in isolation.

The work becomes more valuable as it moves closer to decisions.

I asked everyone some version of: how do people break into content design today?

The answers were not prescriptive. They sounded more like observations from people inside a profession still figuring itself out.

The historical pathway is familiar. Most senior practitioners I spoke with came from adjacent disciplines: journalism, editorial, marketing, technical writing, communications. They came in when the work was being invented. Sarah Winters and her team at the UK Government Digital Service essentially named “content design” as a discipline in the early 2010s by sitting in meetings explaining what they were doing and why. Torrey Podmajersky’s Strategic Writing for UX gave the field a frame and a vocabulary a few years later. Microsoft, Google, Shopify and others matured internal practices around what had previously been ad-hoc copy work.

That was the build-out phase. The current moment is less settled.

Layoffs across tech have hit content roles. AI is changing the bottom layer of execution. Boundaries between content design, product design and product management are blurring in ways that have not fully resolved. Several of the people I spoke with described uncertainty about how the discipline will define itself five years from now.

But nobody described it as shrinking, while almost everyone described it as becoming more strategic.

The implication was not that writing matters less. It was that execution is becoming commoditised and judgment matters more. The bottom of the pyramid is being automated while the top is being asked to do more.

That distinction changes what competence looks like.

When I asked what skills to build now, the answers pointed well past writing craft.

They named design thinking, UX writing principles, content strategy, information architecture, research, facilitation, testing, product strategy, metrics, AI workflows and content systems.

The deeper pattern was learning how products work, how decisions get made, how language connects to outcomes.

One skill that stood out is influence: the ability to explain a decision, defend a tradeoff or hold a position in a stakeholder meeting.

I felt good about that one. Ten-plus years in editorial and content means I have already spent my fair share of meetings defending a headline or a cut in front of people with strong opinions. The room may be wider in UX, but the skill carries.

Another insight was to study people in the field and observe the way they think and express themselves publicly. What problems they return to. What tradeoffs they describe. What assumptions shape their decisions. Less about studying portfolios, which show the output of someone’s thinking, and more about the conversations they are having, that point to the thinking itself.

Another was to develop a personal point of view on where the discipline is heading. Paying attention to how the field is shifting, forming your own judgment about which capabilities seem durable and building accordingly.

What is clear is that writing for digital products is not static or learnable only in its current form. If you want to pursue a career in UX, you need to understand where the work came from, observe where it is moving, and let that shape what you choose to build.

This doubles as a description of the work itself.

What do employers value as proof of competence then?

The answers were practical. Portfolio. Internships. Visible projects. Evidence of thinking. Evidence of outcomes.

Certifications came up, but nobody treated credentials as decisive. Degrees in journalism, linguistics or communications are still considered useful backgrounds.

Several mentors recommended building conceptual projects that demonstrate decisions, constraints, process, rationale and hypotheses, rather than relying on final polished portfolio screens. Some recommended including AI-related work because it signals that you are engaging with how the practice itself is changing.

When I asked about the business side of the role, the conversation moved away from craft and towards position: where content sits inside the organisation and how early it enters the process.

One question I raised in several conversations is whether content designers are expected to be embedded more deeply in the product development process, working inside the tools and environments where the product is being built, rather than handing off copy from a distance. The best practitioners have always pushed for that proximity. What is shifting is that it is becoming an expectation rather than an exception.

The reason proximity matters is not just practical. One person put it this way: “Everyone believes they are protecting the user experience.”

That is true. And it is the source of most of the friction.

Designers care. PMs care. Researchers care. Stakeholders care. Everyone interacts with language and forms opinions about it. Writing expertise is unusually easy to underestimate because everyone has some.

The advice was not to defend the discipline in the abstract. It was to make your decisions visible.

Show process. Show rationale. Show research. Show experiments. Show outcomes. Partner with designers and managers. Get into the broader conversations. Bring evidence. Defend positions and offer revisions.

Influence is not persuading other people that your perspective matters more than theirs. It is helping them see how stronger decisions emerge.

I went into these conversations trying to understand how editorial experience translates into UX writing, but I came away with a different insight: editorial judgement is part of product decision-making.

That feels closer to the actual opportunity. Not moving from one discipline into another but expanding, from shaping the message to shaping the decisions that determine the message.

If the people I spoke with are directionally right, that is also where the discipline itself is going. If production is becoming abundant, judgement remains scarce. AI can write a thousand variants of a button label, but it cannot decide which one belongs there, why or what it implies about the product.

That decision is the work.