{"id":3923,"date":"2012-04-24T09:47:16","date_gmt":"2012-04-23T23:47:16","guid":{"rendered":"http:\/\/wordconstructions.com.au\/blog\/?p=3923"},"modified":"2012-04-17T17:50:22","modified_gmt":"2012-04-17T07:50:22","slug":"getting-procedures-used","status":"publish","type":"post","link":"https:\/\/www.wordconstructions.com.au\/blog\/2012\/04\/getting-procedures-used\/","title":{"rendered":"Getting procedures used"},"content":{"rendered":"
\"Procedure<\/a>

Short, practical procedures work<\/p><\/div>\n

If you have gone to the effort of creating some procedures<\/a>, you want to have your team make use of them.<\/p>\n

Let’s face it, many of us have tried putting together an Ikea unit before reading the instructions – often to use them later. But we don’t want that happening to the procedures we spend time on writing to benefit our businesses.<\/p>\n

Here are four tips for encouraging use of your procedures:<\/p>\n

    \n
  1. when presenting them (for instance, if emailing it out to your team), sell the benefits.
    \nWould you respond better to ‘procedure you must use’ or ‘record sales data quickly’?<\/li>\n
  2. lay out each procedure clearly and neatly
    \nif it looks easy to read and follow, people are much more likely to use procedures \u00a0so use the basics of good procedures such as     lists rather than paragraphs<\/a>, decent size fonts and short instructions (‘hit submit’ not ‘use your mouse to click on the submit button’)<\/li>\n
  3. make the procedures easy to find
    \nif you have a shared computer area (intranet or a shared folder somewhere) or a physical shelf or cupboard, put the procedures there so everyone can always access to most recent version. For specific equipment, keep the procedures nearby – I don’t want to have to visit the main office to use the machinery in the workshop. Then make sure     procedures are named clearly<\/a> so it’s easy to find the relevant procedure when it is needed.<\/li>\n
  4. keep procedures up to date
    \nimagine following a procedure that has an old password or refers to an old version of software (especially a major change so steps have changed) – it’s very frustrating. Let people get frustrated with your procedures and they’re less likely to refer to it again. Most updates are quick but if it is a big change and will take time, note that on the existing procedure so at least people know to expect changes and that a new version is coming.<\/li>\n<\/ol>\n

    What makes you use any procedures you find helpful?<\/p>\n","protected":false},"excerpt":{"rendered":"

    If you have gone to the effort of creating some procedures, you want to have your team make use of them. Let’s face it, many of us have tried putting together an Ikea unit before reading the instructions – often to use them later. But we don’t want that happening to the procedures we spend […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1425],"tags":[1398,700,1492,867],"class_list":["post-3923","post","type-post","status-publish","format-standard","hentry","category-business-communications","tag-benefits","tag-procedures","tag-used","tag-useful"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t