This document provides guidance on writing in plain language. It discusses the key principles of plain language:
1) Being brief by avoiding unnecessary words.
2) Being simple by using everyday language.
3) Being organized with a clear structure.
4) Being friendly by using a respectful, helpful tone.
5) Being action-oriented by telling the reader what to do.
The document provides examples of "before and after" rewrites that apply these principles to make communications more clear and concise for the reader. It also discusses some basic design principles for visual clarity.
11. Plain language is organized.
“Out of clutter, find simplicity.”
- Albert Einstein
“Order is the shape upon which beauty depends.”
- Pearl S. Buck
12. Plain language is organized.
Before
Dear Valued Customer,
Originator's Last Name: Rogers Nelson
Originator's First Name: Prince
Date Received: 2004-02-16
Call Type: MAC
Call Sub-Type: Sanctioning
Call Category: Aliant
Call Status: Open
Your request will be completed no later than: 2004-03-08
Call Description:
Your request has been assigned Customer Care Queue number 00191495. Please
refer to this number when making inquiries. In most cases, a Request Completion
Target Date is assigned immediately at the opening of the ticket. If no date
appears above, please contact us via a reply to this message.
17. Plain language is action-oriented.
Before Failure to send a prompt and timely response to this
notice may result in discontinuation of a recipient’s
benefits under this program.
After If you do not reply to us by May 18, we may have to
put your benefits on hold. Along with the address at the
top of this message, you can reach us right away by
phone or email:
416-555-3555
michelle.black@simplyread.ca
#18: If you cannot use simpler words, then define new ones
#19: My brainstorm:raise the barabove and beyondget traction on _________ramp upaction thisworld-classsynergy/synergisticallylow-hanging fruitwin-winproactiveinitiativeRandom Mission Statement Generator: http://www.netinsight.co.uk/portfolio/mission/missgen.asp (or can google)Also mention article about jargon
#20: Along with it being fatiguing, and making it harder for us to act on what we read, we may not feel that our time and expertise is being respected.
#21: “notice I didn’t say ‘actionable’” e-mailsE-mail Practice with reading e-mail has evolved with the technology. People have become more accustomed to it overall, and now use blackberries, phones and other portable devices to read it. But while we are more used to managing e-mail, we have also become more discriminating in how we read it – many e-mail readers are unforgiving about how they sort through the information they receive. ‘Txtng’People used to using numbers for lettersThey are also used to reading incorrect punctuationIt’s less likely that they are perceiving sender differently because of errorsBlackberries, iPhonesMore scrolling is needed; only first few lines are on auto-displayAttachments are next-to-impossible to read quicklyPeople are replying without access to original info (don’t read thread or are remote from files in office)
#23: This is a PPT that does not consider the reader’s time or the tool being used to communicate…this looks more like something lifted from a report than like a presentation.
#25: Use a readable type size (at least 12 points).Use left justification (also called ‘ragged right’)Keep the number of different fonts or typefaces to a minimum.Make sure there is lots of ‘white space.’Use headings, images and space between paragraphs to visually break up your information.(in full justification – change the justification of the presentation to show how the view/readability changes)Now we will look at some examples of clear, attractive designs, along with some others where it could be improved…
#26: (in full justification – change the justification of the presentation to show how the view/readability changes)What you want:- Heads and subheads- ‘Chunking’Now we will look at some examples of clear, attractive designs, along with some others where it could be improved…