What is content design, really?

If you work in tech and you've heard the term "content design," there's a good chance you've also heard it used to mean wildly different things. That's not an accident. Content design is a discipline still defining itself — and depending on where you encounter it, it can look like UX writing, content strategy, information architecture, or something else entirely.

I lead content design at SAP, where the discipline is new. As I've started building it out, one of the most common questions I get is: what does content design actually look like outside of our walls? This article is my attempt to answer that — to paint a picture of how the discipline has evolved in the broader industry, where it sits, and what it really means to practice it as a UX design discipline.

The naming problem

Let's start with the elephant in the room: nobody agrees on what to call us. Content designer. UX writer. Content strategist. Conversation designer. Microcopy writer. Content engineer. Context designer. Product writer. The list goes on — and those are just the titles in active use at real companies right now.

This isn't just a branding problem. It reflects the fact that content design draws from many traditions and has been shaped by different organizational needs. Some companies hired "UX writers" because they needed someone to write interface copy. Others hired "content strategists" because they needed someone to think about the bigger picture. The work often overlaps, but the framing changes depending on who's hiring, what they think they need, and what the industry was calling the role that year.

For clarity in this article, I'll use "content design" as the umbrella term — not because it's the only valid one, but because it best captures the scope of what this discipline has become.

Where it came from

Content design didn't spring up fully formed. It grew out of the convergence of several established fields: information architecture, human-computer interaction, usability, technical communication, content strategy, journalism, writing for the web, and content marketing, among others.

Each of these disciplines contributed something essential. Information architecture brought structural thinking about how content should be organized and found. Usability and HCI brought evidence-based methods and a focus on how people actually interact with interfaces. Technical communication brought rigor around clarity, precision, and audience awareness. Journalism contributed narrative skill and economy of language. Content strategy introduced the idea that content needs governance, planning, and lifecycle management — not just good writing.

Content design synthesizes all of these into a practice that lives squarely within UX. It's not just about writing well. It's about understanding human behavior, product systems, and communication as interconnected design problems.

What it is now

Today, content design has its own ecosystem. There are dedicated conferences like Button and Growing in Content. There are foundational books — Sarah Winters' Content Design, Torrey Podmajersky's Strategic Writing for UX, Kinneret Yifrah's Microcopy: The Complete Guide. There are podcasts, courses, and thriving professional communities.

This maturation matters because it signals that content design is no longer a function that companies tack on as an afterthought. It's a discipline with established methods, a growing body of knowledge, and practitioners who have spent careers refining how it's done.

Where content design sits in an organization

One of the things that varies most from company to company is where content designers actually sit in the org chart. There are a few common models.

In the team of one model, a single content designer covers an entire product or portfolio. This person is often spread thin but has a wide view of the experience. They tend to become generalists by necessity.

In the centralized model, content designers report to a content design manager within the design organization, but are assigned to work on specific products alongside other designers. This gives content design its own leadership and career path while still embedding the work in product teams.

In the embedded model, content designers report directly to a product team's design manager, sitting alongside other designers and researchers. They're fully integrated into a single team, which deepens product knowledge but can leave them without a content design peer community.

The federated model combines elements of both: content designers are embedded in product teams but also belong to a central content design practice. This core team handles things like standards, shared tools, career development, and cross-product consistency, while individual content designers stay close to their product work.

Each model has trade-offs, and many organizations evolve through several of them as they grow. But in all of these structures, the ideal design pod — the smallest effective unit of design — typically includes a designer, a content designer, and a researcher working as peers.

But what do content designers actually do?

Here's where the biggest misconception lives. Many people assume content designers are writers who sit downstream of the design process, polishing UI text after the "real" design decisions have been made. That's UX writing — and it's a legitimate and important part of the work — but it's not the full picture.

Content designers solve UX problems through strategic communication and language. They use data and evidence to give users what they need, when they need it, and in a way they expect.

That distinction matters. It means content design is a problem-solving discipline, not a production discipline. And it operates by a set of principles that put it firmly in the design family.

Start with the problem, not the content.

A content designer's first question isn't "what should this say?" It's "what problem are we solving?" Just like an interaction designer wouldn't start laying out screens before understanding the user's task, a content designer doesn't start writing before understanding what's standing in the user's way. The content — its format, its structure, whether it exists at all — should be a response to a clearly defined problem.

Use content as a design material, not a layer.

In many organizations, content is treated as a finishing step: designs are created with placeholder text, and then someone is asked to "fill in the words." Content design flips this. Language, structure, and information hierarchy are design materials — just as fundamental as layout, color, and interaction patterns. When content is woven into the design process from the start, the resulting experience is more coherent and more usable.

Seek to solve with design before content.

This one surprises people. Yes, content designers sometimes advocate for less content. If a user is confused by a flow, the answer may not be better explanatory text — it may be a simpler flow that doesn't need explanation. A good content designer looks at the whole interaction and asks whether the design itself could eliminate the need for words. The best content is often no content at all.

Use design methods to inform design decisions.

Content designers don't rely on instinct or personal preference. They use the same methods other designers use: user research, usability testing, A/B testing, competitive analysis, heuristic reviews, audits, and data analysis. Content choices — what to say, how to say it, where to say it — are design decisions, and they deserve the same rigor as any other.

Apply systems thinking across the whole experience.

Content doesn't exist in isolation. A label in one part of the product has to make sense alongside labels everywhere else. An error message has to work within the larger pattern of how the product communicates errors. Content designers think in systems — building and maintaining patterns, terminology frameworks, and voice guidelines that scale across products and teams. This systems perspective is what separates content design from writing: it's not about crafting individual strings of text, it's about designing a coherent language system for an entire experience.

Why it matters

If you've been doing UX writing — crafting clear, useful interface text — you're already doing valuable work. But content design asks you to zoom out. It asks you to question whether the right content is appearing at the right time, whether the information architecture supports the user's mental model, whether the product's language is consistent and systematic, and whether a design problem might be better solved by rethinking the experience rather than adding more words.

Content design is a UX design discipline. The material is language. The methods are design methods. And the goal — like all good design — is to make complex things simple for the people who use them.