{"id":4831,"date":"2016-02-16T16:56:48","date_gmt":"2016-02-16T21:56:48","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=4831"},"modified":"2016-02-16T16:56:48","modified_gmt":"2016-02-16T21:56:48","slug":"technical-writing-is-like-other-writing-done-well","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/02\/16\/technical-writing-is-like-other-writing-done-well\/","title":{"rendered":"Technical Writing Is Like Other Writing Done Well"},"content":{"rendered":"

What is<\/em> this craft of technical writing that we’re engaged in? And why should we be fussing with a question like this? Instead of defining our activity, why don’t we just settle down and do<\/em> it?<\/p>\n

\"images\"<\/a>Well, you’re right, we could just get on with it. But definitions, even for words or activities we know well (don’t we?), are useful. They bring clarity and may remind us of aspects of a task that we’ve overlooked or would rather not be reminded of.<\/p>\n

TechWhirl responds<\/a> to this question with a simple, three-word phrase. (See, if you get serious about something, you can simplify it.) Technical writing is “simplifying the complex.” Yes, that’s simple enough, but is it truly enough? When you head over to Oxford Dictionaries Online, four definitions are provided<\/a> for the word technical<\/em> alone.<\/p>\n

TechWhirl notes that the U.S. Bureau of Labor Statistics “defines technical writers as those who ‘…put technical information into easily understandable language.'” That’s simple and direct enough, especially for a government agency.<\/p>\n

Yet maybe we should note TechWhirl’s long-form definition: “Good technical writing results in relevant, useful and accurate information geared to specifically targeted audiences in order to enable a set of actions on the part of the audience in pursuit of a defined goal.”<\/p>\n

That whopper hinges on instructional audiences and their goals \u2013 presumably, accomplishing a critical task efficiently and safely. To act efficiently and safely, you need instructions that are clearly written and presented, along with being accurate. <\/p>\n

Simple enough, right? Yes, but first, you need to be a master of the process in question to write about it authoritatively and efficiently. Not just the process, but, equally important, the context in which it’s being applied. (We keep thinking back to our years spent working in nuclear power plants.) <\/p>\n

TechWhirl discusses a number of other elements, but they’re mainly on the order of fine-tuning. The essence of the matter is that a good technical writer needs to be authoritative and focused on his reader in pursuit of a common goal \u2013 accomplishing a task efficiently and safely. That, incidentally, is how Hemingway might have described his writing as well. It’s all a matter of context and being effectively other-focused.<\/p>\n

(The graphic above is from a LinkedIn SlideShare presentation<\/a> by Muhammad Ilyas.) <\/em>\u2013 Doug Bedell<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

What is this craft of technical writing that we’re engaged in? And why should we be fussing with a question like this? Instead of defining our activity, why don’t we just settle down and do it? Well, you’re right, we could just get on with it. But definitions, even for words or activities we know […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,3,5],"tags":[],"class_list":["post-4831","post","type-post","status-publish","format-standard","hentry","category-communication","category-technology","category-the-writing-life"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4831"}],"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=4831"}],"version-history":[{"count":12,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4831\/revisions"}],"predecessor-version":[{"id":4844,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/posts\/4831\/revisions\/4844"}],"wp:attachment":[{"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/media?parent=4831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/categories?post=4831"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.encoretechresources.com\/insights\/wp-json\/wp\/v2\/tags?post=4831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}