Menu

Content

Plain Language Review

A practical UX content method for improving clarity, reducing complexity, and helping users understand what to do next.

How to run a plain language review to simplify content, improve comprehension, and reduce user errors.

4 min read

What it is

A plain language review is a UX method used to evaluate whether content is easy to read, understand, and act on for your audience.

It involves assessing text for simplicity, , structure, tone, and jargon.

The review can include headings, instructions, labels, and messaging across the product.

It focuses on making communication straightforward, concise, and accessible to as many users as possible.

The goal is to remove unnecessary complexity and ensure users can quickly grasp what they need to do.

Plain language improves usability by reducing the effort required to understand and act.

When to use it

Use this method when matters.

It is most useful when:

your content is complex or technical
users are struggling to complete tasks
you are designing forms, instructions, or messaging
you want to improve accessibility and comprehension
you are preparing content for a broad audience

It is less useful when:

content is already simple and tested
audience is highly specialised and expects technical detail
Plain language reviews are often used alongside UX writing and content audits.

Key takeaway

Use this method whenever comprehension affects task success or user confidence.

How to run it

Set up properly

Be clear on the content in scope, who it is for, and what standard you are working to. "Simpler" is not a standard, and without one the review becomes a matter of taste.

Use real user . Content that reads clearly at a desk can be impenetrable to somebody reading it on a phone, under time pressure, about money.

Run the method

A plain language review is evaluative and iterative. The aim is not shorter writing but writing that transfers less work to the reader.

  1. Read the content aloud. Anything you stumble over, or run out of breath in, will lose a reader too.
  2. Simplify sentences and remove jargon, replacing terms rather than glossing them. A defined piece of jargon is still jargon.
  3. Check headings, labels and instructions separately from body copy. People scan those and skip the rest, so they carry the meaning.
  4. Ensure in tone and terminology. The same thing called two names is a problem, not a style one.
  5. Validate with real users where you can. Authors are the worst possible judges of whether their own writing is clear.

Focus on understanding, not grammar. Perfectly correct prose can be entirely opaque, and formulas will happily approve of it.

Capture and make sense of it

The value comes from improved . After the review, document:

  • Content that was unclear, with the reason rather than a note that it reads badly
  • Proposed alternatives, written out rather than described
  • Changes prioritised by how many people meet that content and what it costs them
  • Anything that needs testing rather than rewriting on judgement

Use this to make content actionable and clear. Plain language is usually the cheapest improvement available to a product.

What to look for

Focus on:

Clarity: can users understand the meaning quickly
Brevity: is content concise without losing meaning
Jargon: are technical terms explained or removed
Structure: is content organised logically
Tone: is language consistent and appropriate

Where it goes wrong

Most issues come from:

If users have to reread, it’s too complex.

Correcting grammar while leaving the meaning as hard to extract as it was
Simplifying words and keeping the sentence structure that caused the problem
Defining jargon in place instead of replacing it
Using two names for the same thing across a journey
Signing off clarity on the writer's judgement rather than a reader's

What you get from it

Done properly, this method gives you:

Content that transfers less work to the reader
Better completion on the pages where getting it wrong costs somebody
Fewer support contacts caused by content rather than by the product
Consistent language that makes the next piece easier to write

Key takeaway

It helps users know what to do without guessing.

Get in touch

If this sounds like something you need, we can review and simplify your content so users understand it immediately and can act without confusion.

No guesswork. No assumptions. Just clear, effective communication.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is a plain language review in UX?

It is a method for evaluating and simplifying content to improve clarity and comprehension.

When should you use a plain language review?

Whenever content carries a consequence: applications, terms, error messages, anything explaining rights or money. Do it while the content is still in draft; rewriting for clarity after sign-off means going back through everyone who approved it.

What should you check?

Headings, instructions, labels, messaging, and tone.

Why does plain language matter more than good writing?

Because unclear content transfers work to the reader, and some readers cannot absorb it: people under stress, people reading in a second language, people listening to a screen reader. Plain language is usually the cheapest usability improvement available.

Does a plain language review improve UX?

Yes. Clear content reduces errors and increases usability.

Quick take

If users don’t understand your content, they won’t use it. Review for clarity.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer