Good Tech Writers Set Their Own Lean Limits
Posted on December 15, 2012
Filed Under Business, Technology, The Writing Life | Leave a Comment
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 has a leg up in that regard. You won’t be writing unless you have a setting or a process to describe – a specific purpose is built into your output.
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. Potential 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?)
For a while, Way had word count and formatting requirements for Nettuts+, but he dropped them.
“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.
“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.
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.
Read more of what Way discovered about the technical writing process in his post, and stay focused yourself. Write on! – Doug Bedell
Comments
Leave a Comment
If you would like to make a comment, please fill out the form below.
Recently
- Presentations With Forethought
- Technical Writing’s Lineage – Surely It’s Deeper than Digital
- At the Holidays, Twitting Amazon
- Successful Cookie Baking – From Mom, an Acknowledged Expert
- Slides for a Tech Writer’s Craft
- Digital or Not, Be Clear
- Being Watchful About Digital Designs…
- When Proposals Don’t Click, Keep Making Them Anyway
- Like a Good Gardener, Help an Enterprise Keep Itself Current
- We’re Leaders All, And Need to Think That Way
Categories
Archives
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
Blogroll