The following excerpt is from chapter two, which describes why so many policies and procedures fail. I have led hundreds of writing workshops. Before class I often study writing samples from those who will attend. Time after time I find the same dozen writing pitfalls that ruin policies and procedures. Just avoid this "deadly dozen," and your writing will easily outperform most of what other organizations grind out. The dozen pitfalls fit into three major Writing Style, Page Layout, and Organization. . . . Of all the "deadly dozen," the blending of policy, procedure, and task is one of the surest ways to produce a policy-procedure manual that defies reading. Often it's obvious the writer's own mind hasn't clearly distinguished policy, procedure, and task. As a result, the ideas spill onto the page like clothes from a tumble-dryer. Then the readers--if they try at all--must mentally sort out each piece and fit it into its proper place. The differences that set policy, procedure, and task apart are important differences. They matter because each kind of written direction works best in its own format. Unless you first "think them apart," you won't be able to present each of the three in its own most readable form. What are the differences? That's the subject of the next chapter.
I have to rewrite procedures at work, so this is a good time to learn how to do them right. I got this book today in a class taught by Larry Peabody' s son. The edition I have is the 3rd edition, copyrighted in 2009 and 2013.
My weakness is words. I write procedures in a narrative style. They're too wordy, too full of filler, and not easy to read. So, I need to change how I write for work. This book doesn't just tell me to do it, it tells me howto do it! I mean, structurally how to do it.
The book outlines common policy writing pitfalls, and tells writers how to avoid them. It provides good instruction about how to write useful and effective documents. The book provides many examples to illustrate points, and it's concise while still being full of information.
This is definitely a book that will change the way I write for business. I am so thankful to finally have something that tells me how to write more efficiently and effectively! And I think the trainees who have to read what I write will be thankful, too.
This is THE guide to writing procedures and tasks. I wish I had this in my programming days. For now, I can use this, after training, to make all procedures and imbedded tasks easy to follow and easy to read. Thank you Mr. Peabody!!