The Elements of (Gov 2.0) Style
I’m all for the “clarity in government” objective of PLAIN (Plain Language Action and Information Network), the folks who maintain plainlanguage.gov.
I fully understand and support the need for PLAIN’s lofty goal of “Improving Communication from the Federal Government to the Public,” but don’t quite understand the need to create an entire Website to achieve this.
While I may be simplifying this effort, it seems to me a better approach would be to make Strunk and White’s classic The Elements of Style required reading for all federal government employees.
I’m a big believer that great writing is fundamental to successful Websites (see Why Gov 2.0 means the U.S. Government must centralize its Web operations).
On June 1, 1998, President Bill Clinton issued a memorandum on Plain Language in Government Writing as part of its reinventing government efforts.
The directive states:
- By October 1, 1998, use plain language in all new documents, other than regulations, that explain how to obtain a benefit or service or how to comply with a requirement you administer or enforce. For example, these documents may include letters, forms, notices, and instructions. By January 1, 2002, all such documents created prior to October 1, 1998, must also be in plain language.
- By January 1, 1999, use plain language in all proposed and final rulemaking documents published in the Federal Register, unless you proposed the rule before that date. You should consider rewriting existing regulations in plain language when you have the opportunity and resources to do so.
PLAIN defines plain language as:
Plain language (also called Plain English) is communication your audience can understand the first time they read or hear it. Language that is plain to one set of readers may not be plain to others. Written material is in plain language if your audience can:
* Find what they need;
* Understand what they find; and
* Use what they find to meet their needs.
There are many writing techniques that can help you achieve this goal. Among the most common are:
* Logical organization with the reader in mind
* “You” and other pronouns
* Active voice
* Short sentences
* Common, everyday words
* Easy-to-read design features
No one technique defines plain language. Rather, plain language is defined by resultsâ€”it is easy to read, understand, and use.
- Is the federal government living up to the mandate?
- If no, what can we do about it?
Every day I get to engage with entrepreneurs, public sector innovators and journalists on re-imagining and re-energizing how government works, what it means to be “civic,” and this year has been an incredible one for many friends and colleagues.
I’m always inspired talking and working with entrepreneurs trying to solve big civic problems, especially those who realize much of the challenge lies within modernizing and empowering internal government operations, so it was great to finally meet with Govtech Fund Founder and Managing Partner Ron Bouganim this week.
The 18F Delivery team released a “Partnership Playbook” that aims to help federal agencies understand what to expect when working with 18F, and the gem within is play number two, “We work with an empowered product owner.”
Citizens simply glaze over when they are confronted by a sea of large numbers with many zeros. These figures need to be relatable to the person reading the data. Otherwise, open data is just more data that dies on the vine.
The U.S. Department of Veterans Affairs released a beta version of Vets.gov, and it’s the future of federal government digital development.
The Welsh Government released a report of its findings on how local government in Wales can better leverage digital technologies and realize significant savings while still providing quality, scalable citizen services.
A California bipartisan oversight committee, the Little Hoover Commission, has issued recommendations on how the state can bring a more customer-centric government to residents and visitors.
Seneca Systems CEO Chris Maddox shares the inspiration behind the new constituent relationship management system, Romulus.
“No ugly, old IT” jumped out at me when I first reviewed DataSF’s strategic plan, “Data in San Francisco: Meeting supply, spurring demand,” and it still sticks, mostly because someone inside government was so bold as to make this a priority and openly communicate it and also because this should be a mantra for everyone building civic technology.
Enabling internal government tech shops to quickly stand up applications in a secure testing environment is fundamental to quick prototyping, and 18F’s new Cloud.gov is a major step in realizing ultimate IT flexibility.