{"id":5127,"date":"2016-07-18T16:01:21","date_gmt":"2016-07-18T21:01:21","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=5127"},"modified":"2016-07-18T16:14:13","modified_gmt":"2016-07-18T21:14:13","slug":"curiosity-a-reminder-of-ever-present-opportunity","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2016\/07\/18\/curiosity-a-reminder-of-ever-present-opportunity\/","title":{"rendered":"Curiosity: A Reminder Of Ever-Present Opportunity"},"content":{"rendered":"

\"W84ORcf\"<\/a>Here’s a timeless technical writing post that we’ve kept in our folder and, in a summer lull, consider highly appropriate to share on a blog that aims to promote excellence in technical writing.<\/p>\n

Sharon Burton posted it<\/a> in June, 2014 under the heading, “The most important trait of a technical writer.” What do you think that would be?<\/p>\n

Let Sharon answer: “I can teach someone to write. I can give them the Good Writing Guidelines, I can set up a structure that they need to follow to create topics. I can teach the basics of any tool we choose. I can teach them about audience and what the audience needs and how that impacts us.<\/p>\n

“What I can\u2019t teach is the curiosity to ask questions, to poke at the product, to constantly ask \u201cWhat if\u2026?\u201d<\/p>\n

There it is, “Curiosity to ask questions…” Why be curious when you’re writing about something that already exists, a process or product that requires a procedure? Because nothing is ever fully finished, complete, beyond evolving a little or a lot, beyond posing a risk of misuse or misunderstanding. <\/p>\n

These latter categories are a technical writer’s great opportunity \u2013 to promote evolution and to ehhance safety and utility. “Nothing is ever fully finished” \u2013 therein lies great opportunity or, at the least, relief from carefully practiced, workaday routine.<\/p>\n

Every topic or procedure a technical writer approaches ought to be treated as a learning opportunity with a paramount aim \u2013 freshness, newness, a better way of proceeding.<\/p>\n

“If you’re curious,” Sharon advises, “you’ll learn more about your tools. You’ll ask more about your audience. You’ll think to ask important questions about the product you’re documenting. You’re thinking about everything as you do it, to understand more deeply everything you work with.”<\/p>\n

Yes, technical writing is a form of exploration. You need to know the territory before you can bind it for others to follow safely and efficiently. So don’t ever leave unanswered a question that you or others raise \u2013 that might keep you from discovering something additionally important, something that needs to be included for completeness.<\/p>\n

We’re glad we held on to Sharon Burton’s ever-pertinent reflections to this summer day when not much is, or seems to be, happening. \u2013 Doug Bedell <\/em> <\/p>\n","protected":false},"excerpt":{"rendered":"

Here’s a timeless technical writing post that we’ve kept in our folder and, in a summer lull, consider highly appropriate to share on a blog that aims to promote excellence in technical writing. Sharon Burton posted it in June, 2014 under the heading, “The most important trait of a technical writer.” What do you think […]<\/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-5127","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