Content isn’t copy, it’s how users succeed or fail

At Path we have always taken a content-first approach, as part of our UX design process.  

The gap between “content” and content design

There’s a fundamental difference between:

• writing content
• and designing content

Writing focuses on what to say. Content design focuses on:

• what users are trying to do
• what they need to know to do it
• how information is structured and presented
• whether it actually works in practice

It’s the difference between:

“Does this sound good?”
and
“Can a user complete their task?”
 

Where most digital projects go wrong

In many projects, the process looks like this:

1. Define pages and navigation
2. Design layouts
3. Build templates
4. Add content

By the time content appears, the important decisions are already locked in.

This leads to familiar problems:

• users can’t find what they need
• information is structured around the organisation, not the user
• content is rewritten repeatedly, but never really improves
   

What proper content design looks like

Content design is an integral part of UX.

It starts early and runs through the entire process.

1. Start with user needs

Understand:

• what users are trying to do
• what information they need at each step
• the language they use

This comes from research, not assumptions.

2. Structure information around tasks

Before writing anything, define:

• clear user journeys
• logical groupings of content
• simple, predictable structures

Good structure reduces cognitive load before a single word is written.

3. Design and write together

Content and interface should be designed as one system:

• headings guide decisions
• labels shape navigation
• microcopy supports actions

This is where clarity is created.

4. Test with real users

This is where many teams fall short.

Content should be tested just like any other part of UX:

• can users understand it?
• can they complete key tasks?
• where do they hesitate or misinterpret?

If you’re not testing content, you’re guessing.

Why this matters

When content is properly designed:

• users complete tasks faster
• errors and confusion drop
• support queries decrease
• services become more accessible

These are not content outcomes.
They are service outcomes.

Why few organisations get this right

Content design requires:

• involving content early
• challenging internal structures
• making decisions based on user evidence

That’s uncomfortable.

It’s easier to:

• focus on visuals
• rely on stakeholder opinions
• treat content as a final step

But that approach creates avoidable problems, and costs more to fix later.

A different approach

At Path, we treat content as part of user experience from the start.

• designing content and structure together
• grounding decisions in user research
• testing content before development begins

Content is how users experience your service

Users don’t experience your organisation through wireframes or design systems, they experience it through:

• the words they read
• the choices they’re given
• how clearly they can understand what to do next

If that doesn’t work, nothing else matters.

If you’re redesigning a website or service

Ask one simple question early:

“Are we designing content, or just adding it later?”

The answer will shape the outcome more than any visual design decision.

Talk to us

If you want to design content that helps people complete real tasks, not just fill pages, we’d be happy to talk. hello@path.ie