Stakeholder insights

Key quotes

“Everybody in the federal government should know about plainlanguage.gov.”

“We don’t want it to be totally different from everything else, but we do want it to be different enough from DigitalGov to not feel like GSA.”

“99% of the time, [training] requests are from people who are writers by necessity.”

“There’s always an underlying irritant like the sand in the oyster shell that has led them to find whatever help they can.”

“We need a large amount of fresh site content.”

Needs

• Replace database for training requests
• Serve federal agencies in their communication goals
• Clarify training availability and requirements

Expectations

• Deliver clear, concise, useful, relevant, and up-to-date content
• Define plain language and how to use it
• Outline the requirements of the law
• Help users write, rewrite, and test their content

Potential outcomes

• Expand our reach and amplify our message
• Increase the number of active training and website volunteers
  • Reach out to top writers in government
  • Develop advanced-level classes or exercises
• Encourage members to advocate for change
• Improve government communications and better inform the public
• Improve resources section
  • Update and add checklists or one-pagers
  • Include more links to and from DigitalGov for tutorials, articles, videos, etc.

Design Workshop and Stakeholder Insights (PDF)