Plain Language Guide Series

Test for understanding

Learn how to test that your content is easily understandable.
Four people working through a checklist

Overview

Testing your content should be an integral part of your writing and planning process — not just something you just do after the fact. It’s especially important to test our assumptions in government, because we’re often writing for thousands or even millions of people.

Testing your writing to make sure it’s clear to users can save you time in answering questions later.

Whether you’re writing for websites, brochures, videos, social media, public affairs, or other materials, we recommend these same techniques to test individual pages or smaller chunks of content.

When to test

Start as soon as you have enough material to test. Don’t wait until your website has been coded or your document is complete. 

Test as early as you can in the project, whether you’re creating something new or making revisions. Test, make corrections based on feedback, and test again. Plan to test at least twice. This process of testing, revising, and re-testing is called “iteration.” Iteration is part of what makes usability testing so effective.

Tests to consider

You can use several techniques to help you improve your website content so that the final version will be successful:

  • Paraphrase testing: individual interviews, best for short web pages, short documents, and to test the questions on a survey.
  • Usability testing: individual interviews, best for longer documents and web sites where finding the right information is important; also best for forms.
  • Controlled comparative studies: large scale studies where you don’t meet the people but you collect statistics on responses; use paraphrase testing and usability testing on a smaller scale first.

Focus groups are discussions in which you learn about users’ attitudes and expectations more than about whether they can find and understand information. Therefore, they are more relevant to understanding your audience before you write than to testing.