{"id":5073,"date":"2016-06-23T09:49:12","date_gmt":"2016-06-23T14:49:12","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=5073"},"modified":"2016-06-23T09:49:12","modified_gmt":"2016-06-23T14:49:12","slug":"technical-writers-need-to-be-communicators-first","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/06\/23\/technical-writers-need-to-be-communicators-first\/","title":{"rendered":"Technical Writers Need to Be Communicators First"},"content":{"rendered":"

\"maze-1328372-m\"<\/a>Craig Haiss has poured 15+ years of technical writing into a highly experienced post<\/a> on his HelpScribe blog. Other writers, whether as experienced or not, will likely appreciate Craig’s reflections on the road he’s travelled.<\/p>\n

He’s grouped and highlighted his past production into such categories as “User manuals,”Training guides” and “White papers.” The references aren’t necessarily to actual documents but how to produce them, under such headings as “Know your audience” and “Know what distinguishes you from your competition.” <\/p>\n

Competition? Most likely. “Chances are,” Craig advises, “your sales pitch won’t be the first to come across the desk of your potential client. So, why should you get the sale?”<\/p>\n

The advice that follows is designed to highlight your professionalism. Understand what that involves, at least as a refresher from a highly experienced colleague. Craig provides input on everything from White Papers to Disaster Recovery Plans and Communication Plans.<\/p>\n

What does a technical writer need a Communication Plan for? Plenty, if he or she wants to make a profitable imprint on the field. “Gather existing notes on communication policies,” Craig urges. “Often these will be organized and distributed in an inconsistent manner. Writing a communication plan gives you a chance to consolidate them and make the easily accessible.”<\/p>\n

Yes, organizational communication is too often circuitous, casually attempted and, therefore, not as successful as it ought to be. Rather than expect you to read on here,
\nwe direct you to Craig Haiss’ resourceful post. Before a technical writer functions as a writer, he or she needs to be an effective organizational communicator. That’s where clients and assignments hail from.<\/p>\n

Remember: Communicating isn’t necessarily the same as writing. It creates an effective environment for writing. First one, then the other.\u2013 Doug Bedell<\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"

Craig Haiss has poured 15+ years of technical writing into a highly experienced post on his HelpScribe blog. Other writers, whether as experienced or not, will likely appreciate Craig’s reflections on the road he’s travelled. He’s grouped and highlighted his past production into such categories as “User manuals,”Training guides” and “White papers.” The references aren’t […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-5073","post","type-post","status-publish","format-standard","hentry","category-communication"],"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