What it is
An assessment of text difficulty using readability formulas (such as Flesch-Kincaid) and manual review, checking that content matches the audience’s reading level.
When to use it
During Prototype and Implement, whenever content must be understood by a broad or lower-literacy audience, as is common in government services.
Why (value)
Clear, appropriately leveled text reduces errors and support costs and makes services usable by more people.
How to run it
- Set a target reading level for the audience.
- Run text through readability formulas.
- Manually review for jargon, sentence length, and structure.
- Flag passages above the target.
- Rewrite and re-measure.
Inputs and outputs
- Inputs: The content, a target reading level, readability tools.
- Outputs: Readability scores and flagged, revised passages.
Time and effort
Low. Scores are instant; rewriting takes the time.
Evidence and limitations
Readability scores are an inference from surface features like word and sentence length; they do not guarantee comprehension, which needs direct-user testing. See Evidence and limitations.
Tips and pitfalls
- Treat scores as a signal, not a verdict.
- Pair formulas with human judgment.
- Confirm comprehension with real readers for critical content.
Variations
Flesch-Kincaid, Gunning Fog, SMOG, and manual plain-language review.
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
- Plain-language editing — Rewrite content so people can read, understand, and act on it the first time.
- Copy review — Review interface text for clarity, accuracy, voice, and consistency before it ships.
- Content-first design — Design around real content instead of filling a layout with lorem ipsum.
