Steta Publishers
  • Home
  • About
  • Work
  • Twitbits
  • Blog
Steta Publishers was a writing and brand language consultancy that ran from 2012 to 2016. We are no longer available for projects. Our founders now work here and here. 

Technical Writers Are No Longer An Afterthought - Part III

13/3/2013

0 Comments

 

“Did you inform Documentation about the changes we made?”

If you have been in the technical writing field, you would have often heard this sort of question from managers of technical teams. You don’t need to be a genius to notice that technical writers came as an afterthought. Everything had been discussed, decisions taken, and the feature or the ‘change’ to a feature had been implemented in the product. Now, all that was required was to inform the Documentation team. Normal? Yes. But that means you are stuck in the past.  

Today, technical writers and user interface designers are on par with the development teams when it comes to decision-making on the product. Right at the start of the product development process, a technical writer is quite likely to tell the technical teams what makes sense to an average user and what doesn’t – imagine this feedback coming in to product management after the product is out in the market! It is also quite possible that a technical writer suggests an easier workaround to a roadblock in product development.

Perhaps, the most important change in recent years is that Documentation or User Assistance is no longer an excuse for bad product design or misjudged product behavior.  Earlier, if bad product design or behavior slipped through the cracks, technical teams informed the technical writer to write about it in relevant sections in the appropriate guide.  But now, with technical writers becoming part of the process that designs the product in the first place, the chances for such slips have been minimized.  The important thing is to appreciate that everyone – product managers, developers, QA engineers, support engineers, documentation/user assistance experts, and usability designers – has an equal stake in product development. Everyone is accountable and everyone contributes to the thought process and to the development of the product. No one is merely informed and no one takes the higher ground.

Today, if you work as a technical writer with a company that’s in touch with the present, you are more likely to hear, “What about User Assistance? Have you taken their opinion?”

Urmilla Chandran
The author is co-founder and Director, Content Development at Steta  
0 Comments



Leave a Reply.

    Authors

    Steta's founders, Urmilla Chandran and Armeen Kapadia author this blog. 

    We love letting our thoughts (crazy, stupid or smart) out for some fresh air.


    Archives

    October 2016
    May 2016
    March 2016
    January 2016
    October 2015
    September 2015
    June 2015
    May 2015
    December 2014
    November 2014
    October 2014
    September 2014
    July 2014
    March 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


    Categories

    All
    Awards
    Blogging
    Books
    Bookstore
    Business Writing
    Classical
    Content
    Corporate
    Culture
    Design
    Dictionary
    Editing
    Grammar
    Help Authoring Tools
    Image
    Language
    Life
    Literature
    Media
    News
    Newspaper
    Personal
    Press
    Printing
    Problem
    Professional
    Punctuation
    Reading
    Retrospective
    Review
    Solution
    Story
    Technical Writing
    Technology
    Thesaurus
    Tools
    Typewriter
    Vocabulary
    Writers
    Writing


Home

Work
Blog
About


Copyright © Steta Publishers 2012–16. All rights reserved.