What it is
Editing content to be clear, concise, and understandable, using common words, short sentences, active voice, and logical structure, so users can find, understand, and use information easily. Central to accessibility and government content standards.
When to use it
During Prototype and Implement, on all user-facing content.
Why (value)
Comprehension is a prerequisite for usability; plain language reduces errors, support load, and exclusion, and is often legally required.
How to run it
- Identify the reader and their task.
- Cut jargon and unnecessary words.
- Use active voice and short sentences.
- Structure for scanning (headings, lists).
- Test comprehension with real users.
Inputs and outputs
- Inputs: Draft content and knowledge of the audience.
- Outputs: Clear, usable, accessible content.
Time and effort
Low. Editing effort.
Evidence and limitations
Editing improves clarity, but comprehension should be validated with users; readability formulas are proxies, not proof. See Evidence and limitations.
Tips and pitfalls
- Write for the reader’s task, not the org chart.
- Prefer common words and active voice.
- Test that people actually understand it.
Variations
Plainlanguage.gov guidelines, readability-driven editing.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Readability analysis — Measure how hard your text is to read and whether it suits your audience's reading level.
- Content-first design — Design around real content instead of filling a layout with lorem ipsum.
- Voice and tone guidelines — Define how the product sounds so content stays consistent and on-brand across contexts.
