{"id":5092,"date":"2016-07-08T15:59:13","date_gmt":"2016-07-08T20:59:13","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=5092"},"modified":"2016-07-09T08:40:04","modified_gmt":"2016-07-09T13:40:04","slug":"no-catch-up-practiced-here","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/07\/08\/no-catch-up-practiced-here\/","title":{"rendered":"No &#8216;Catch-Up&#8217; Practiced Here"},"content":{"rendered":"<p><a href=\"http:\/\/www.encoretechresources.com\/insights\/wp-content\/uploads\/images-7.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/www.encoretechresources.com\/insights\/wp-content\/uploads\/images-7-300x168.jpg\" alt=\"images\" width=\"300\" height=\"168\" class=\"alignnone size-medium wp-image-5100\" \/><\/a>Yes, technical writing can be a stressful trade. &#8220;No one likes being told what to do,&#8221; Anne Gentle <a href=\"http:\/\/justwriteclick.com\/2016\/06\/30\/influencing-community-documentation-contributions\/\">writes on JustWriteClic.com<\/a>. Well, yes and no. Employees subject to the dictate of technical procedures may realize that it&#8217;s they&#8217;re job to pay them heed, but may also be subject to other pressures to get their tasks done and put the rule book back in the drawer. <\/p>\n<p>So tech writers need to develop a mindset in which they are both public relations people (in the best sense of &#8220;relational&#8221;) and rule-makers in terms of explaining how safely and efficiently to get things done in challenging settings. <\/p>\n<p>That&#8217;s no narrow charter \u2013 being kind and promoting accountability at the same time. Timeliness is part of the answer. Colleagues will pay greater heed to information when it reaches them in a timely manner. For one thing, that makes it fresher all around.<\/p>\n<p>&#8220;When a bit of code changes that makes a difference in the docs,&#8221; Anne writes, &#8220;that&#8217;s a crucial moment for influencing a particular behavior. The behavior we want to see is writing documentation while the code is fresh in your mind.&#8221; Code or any other pertinent change in a safety, procedural or security change in a workplace setting, we&#8217;d add.<\/p>\n<p>Don&#8217;t wait to be helpful (we&#8217;d hesitate to say &#8220;directive&#8221;) \u2013 get the new word out as promptly as possible. <\/p>\n<p>Striking while the &#8220;digital&#8221; iron is hot is what&#8217;s involved here. When people feel they&#8217;re being informed in a timely manner, they&#8217;re likely to act in a more prudent, compliant manner. The alternate is risking having them act hastily, with material that feels like playing catch-up. <\/p>\n<p>No one in a workplace or at a website that needs technical writers in the first place should want to instill encourage playing &#8220;catch-up&#8221;. That&#8217;s what Anne Gentle has inspired us to advise. \u2013 <em>Doug Bedell<br \/>\n<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yes, technical writing can be a stressful trade. &#8220;No one likes being told what to do,&#8221; Anne Gentle writes on JustWriteClic.com. Well, yes and no. Employees subject to the dictate of technical procedures may realize that it&#8217;s they&#8217;re job to pay them heed, but may also be subject to other pressures to get their tasks [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5092","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/5092"}],"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=5092"}],"version-history":[{"count":31,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/5092\/revisions"}],"predecessor-version":[{"id":5124,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/5092\/revisions\/5124"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=5092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=5092"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=5092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}