{"id":5027,"date":"2016-06-03T08:32:52","date_gmt":"2016-06-03T13:32:52","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=5027"},"modified":"2016-06-03T08:36:16","modified_gmt":"2016-06-03T13:36:16","slug":"clarity-counts-for-everyone","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/06\/03\/clarity-counts-for-everyone\/","title":{"rendered":"Clarity Counts for Everyone"},"content":{"rendered":"

\"images\"<\/a>What\u2019s a technical writer\u2019s purpose?<\/p>\n

Sarah Maddox on her blog Ffeathers<\/a> gives that timeless question (at least since the first technical document wafted through a transom) a fresh spin by quoting Joao Fernandes, whom she heard speak at a conference:<\/p>\n

\u201cHelp build products that need no documentation.\u201d<\/p>\n

Yes, Sarah notes, \u201cOur users don\u2019t want to read the docs. They want to use the product.\u201d<\/p>\n

Accordingly, technical writers should be on both the design and delivery ends of projects and equipment. If you\u2019re not, ask why not.<\/p>\n

A technical writer, Joao is further quoted, should be the \u201cCEO of the docs.” How\u2019s that for a sense of purpose? Without clear documentation, an organization can\u2019t function. So you\u2019re virtually in control of your organization. And your CEO will appreciate it if you function clearly and concisely. (He or she may need some help with that, too.)<\/p>\n

The best documentation, Fernandes added at the Docs NA 2016 conference, may be \u201cvery little.\u201d Strong organizations begin with clarity in designing their own mission and goals before serving users. <\/p>\n

You\u2019ve known it right along: Technical writing is, or should be, a highly strategic function. Act on that recognition every chance you get, clearly and deliberately. Hopefully, you\u2019ll be thanked for it. \u2013 Doug Bedell<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

What\u2019s a technical writer\u2019s purpose? Sarah Maddox on her blog Ffeathers gives that timeless question (at least since the first technical document wafted through a transom) a fresh spin by quoting Joao Fernandes, whom she heard speak at a conference: \u201cHelp build products that need no documentation.\u201d Yes, Sarah notes, \u201cOur users don\u2019t want to […]<\/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-5027","post","type-post","status-publish","format-standard","hentry","category-communication","category-technology","category-the-writing-life"],"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