{"id":1789,"date":"2011-09-01T12:41:51","date_gmt":"2011-09-01T17:41:51","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=1789"},"modified":"2012-01-09T19:52:46","modified_gmt":"2012-01-10T00:52:46","slug":"writing-engaging-employee-handbooks","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2011\/09\/01\/writing-engaging-employee-handbooks\/","title":{"rendered":"Writing Engaging Employee Handbooks"},"content":{"rendered":"

Ever been asked to write an employee handbook? That’s a special challenge because you’re writing on behalf of an organization for the people whose enthusiasm, support and creativity are vital to its success. They don’t cotton to legalese or strictures. An effective handbook needs to be more than simply a recitation of rules.\u00a0 We’re talking, in effect, about technical writing with a human face.<\/p>\n

\"\"<\/a>In this context, we’ve come across a website \u2013 klariti.com \u2013 with a page on “How to Make Employee Handbooks More Human.”<\/a> It’s selling an employee handbook template, but it’s modestly priced ($9.99) and might be good to have on hand. Beyond that, though, Ivan Walsh, the writer, has some pertinent tips for putting an engaging handbook together.
\n
\nFirst off (and this is where many projects seem to begin these days), he suggests heading to Google, entering the term “employee handbook” and downloading samples that appeal to you. Sure enough, there are lots of entries for either generic or actual handbooks to consider,\u00a0 many for downloading in the form of PDF files.<\/p>\n

Walsh advises capturing the parts of the various manuals that you and your team find most interesting either in\u00a0 an old-fashioned file folder or on Evernote<\/a>, a free web filing app. Then pick two three as most pertinent to your own project.<\/p>\n

Approach the whole design, Walsh urges, in a personalized manner. You’re writing to be read and for your organization to be well-regarded, not merely coped with. “Share values not rules” is a Walsh stricture, because “Values are positive. Rules are (perceived as) negative. Open the document with an outline of what the company holds dear…” A statement of its vision and values would go nicely here.<\/p>\n

Include stories, Walsh continues. Call them anecdotes if you prefer, but provide examples of desired corporate\u00a0 conduct that everyone in the organization can relate to. Explaining why<\/em> you have these values in terms of customer or regulatory relationships is advisable.<\/p>\n

Next is a Walsh tip that you don’t often see in handbooks \u2013 include input from employees themselves. “Approach employees personally and ask them to share something that makes them enjoy working at the company. It doesn\u2019t have to be \u2018epic\u2019, just something that others can relate to.”<\/p>\n

Including employee experiences can provide immediate verification and validation of a company’s aims and preferred manner of doing business. The manual, says Walsh, becomes “a living document.”<\/p>\n

And, of course, he adds: Remember to include pictures. How many manuals that you recall would have been helped greatly by some photos to illustrate and enliven the work settings you’re promoting?<\/p>\n

Employee handbooks don’t need to be tedious recitals of rules and processes. They can be engaging invitations to function creatively and responsibly at work. That, indeed, ought to be your aim in envisioning the handbook you’ve been asked to produce. – Doug Bedell<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Ever been asked to write an employee handbook? That’s a special challenge because you’re writing on behalf of an organization for the people whose enthusiasm, support and creativity are vital to its success. They don’t cotton to legalese or strictures. An effective handbook needs to be more than simply a recitation of rules.\u00a0 We’re talking, […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,3,5],"tags":[],"class_list":["post-1789","post","type-post","status-publish","format-standard","hentry","category-business","category-technology","category-the-writing-life"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/1789"}],"collection":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/comments?post=1789"}],"version-history":[{"count":22,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/1789\/revisions"}],"predecessor-version":[{"id":2271,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/1789\/revisions\/2271"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=1789"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=1789"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=1789"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}