{"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 ‘Catch-Up’ Practiced Here"},"content":{"rendered":"

\"images\"<\/a>Yes, technical writing can be a stressful trade. “No one likes being told what to do,” Anne Gentle writes on JustWriteClic.com<\/a>. Well, yes and no. Employees subject to the dictate of technical procedures may realize that it’s they’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

So tech writers need to develop a mindset in which they are both public relations people (in the best sense of “relational”) and rule-makers in terms of explaining how safely and efficiently to get things done in challenging settings. <\/p>\n

That’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

“When a bit of code changes that makes a difference in the docs,” Anne writes, “that’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.” Code or any other pertinent change in a safety, procedural or security change in a workplace setting, we’d add.<\/p>\n

Don’t wait to be helpful (we’d hesitate to say “directive”) \u2013 get the new word out as promptly as possible. <\/p>\n

Striking while the “digital” iron is hot is what’s involved here. When people feel they’re being informed in a timely manner, they’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

No one in a workplace or at a website that needs technical writers in the first place should want to instill encourage playing “catch-up”. That’s what Anne Gentle has inspired us to advise. \u2013 Doug Bedell
\n<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Yes, technical writing can be a stressful trade. “No one likes being told what to do,” Anne Gentle writes on JustWriteClic.com. Well, yes and no. Employees subject to the dictate of technical procedures may realize that it’s they’re job to pay them heed, but may also be subject to other pressures to get their tasks […]<\/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":[],"aioseo_head":"\n\t\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