![]() |
Start a plain language initiative in your organization:
|
|
Step 6Writing is personal. It’s important to respect this when you are revising a draft prepared by a subject-matter expert, whether an engineer, an office manager, or a personnel manager. People become attached to the terminology they use routinely in their profession and may become defensive when you suggest simpler language or shorter explanations. They know that what they have written is correct and think that if you revise it, you will change its meaning.
Example:
I recently finished a project to overhaul a set of responses my agency sends when workers file complaints against their employers for not paying wages. As it turned out, I had recently rewritten a high-level letter composed by the woman who was to be the key member of my new team. She’d been justifiably hurt by my complete rewrite, mostly because no one in management had actually explained to her what was wrong with her earlier drafts, which they kept sending back to her. When we began working together, she was clearly exasperated with the agency’s “plain language thing.” But once she realized I respected her expertise in wage law and was willing to work one-on-one with her to develop her skill, she became a solid writing partner. She soon realized that she needed only to write the way she spoke to workers on the phone each day, using ordinary language. In the end, she developed a flair for composing simple “translations” of the “government style” materials we were overhauling. |
Articles and other resources for plain language
|
|