{"id":3428,"date":"2012-12-15T11:39:30","date_gmt":"2012-12-15T16:39:30","guid":{"rendered":"http:\/\/www.encoretechresources.com\/insights\/?p=3428"},"modified":"2013-01-08T17:00:30","modified_gmt":"2013-01-08T22:00:30","slug":"lean-technical-writing-comes-naturally","status":"publish","type":"post","link":"http:\/\/www.encoretechresources.com\/insights\/2012\/12\/15\/lean-technical-writing-comes-naturally\/","title":{"rendered":"Good Tech Writers Set Their Own Lean Limits"},"content":{"rendered":"

Writers need readers or their writing may not exist. Unless you’re a diarist or a personal blogger, you want assurance that someone will be reading your work. Technical writing \u00a0has a leg up in that regard. You won’t be writing unless you have a setting or a process to describe \u2013 a specific purpose is built into your output.<\/p>\n

\"\"<\/a>Okay. But what if you’re writing for a publisher with strict formatting requirements? Could that seriously cramp your style? Might a template or word limit deflect your motivation for even getting started? It certainly could, Jeffrey Way, editor of the Nettuts+ blog confirms.<\/a> \u00a0Potential publishers shouldn’t be setting limits on technical writers if they can possibly avoid them. (That’s assuming, of course, given writers are orderly and efficient in the first place. But what competent technical writer wouldn’t be?)<\/p>\n

For a while, Way had word count and formatting requirements for Nettuts+, but he dropped them.
\n
\n“What I didn’t take into consideration,” he writes, “was the number of potential writers that I inadvertently pushed away, by setting these requirements. Who honestly has the time to work within the confines of somebody else’s template? When time is a precious commodity (especially for those with existing full time jobs and families ), these confines serve to be nothing more than a deterrent.<\/p>\n

“These days, my only goal, when commissioning new content, is to make the writing process for the author as effortless and natural as possible.” And he lists the ways he goes about that, including “Don’t even think about word counts or image requirements…” Way’s assumption is that a competent writer knows what a given assignment will require to be effective, that and no more.<\/p>\n

Lean writing, focused on a process or setting, comes naturally for a good technical writer. He or she needs to be clear and direct, and knows it. If the writing gets longer, it’s because the process being described requires it, not because of flights of authorial fancy.<\/p>\n

Read more of what Way discovered about the technical writing process in his post, and stay focused yourself. Write on! \u2013 Doug Bedell<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

Writers need readers or their writing may not exist. Unless you’re a diarist or a personal blogger, you want assurance that someone will be reading your work. Technical writing \u00a0has a leg up in that regard. You won’t be writing unless you have a setting or a process to describe \u2013 a specific purpose is […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,3,5],"tags":[],"class_list":["post-3428","post","type-post","status-publish","format-standard","hentry","category-business","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