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. 

What do You Really Think of Technical Writers? – Part I

17/12/2013

4 Comments

 
Over the past two weeks, I reached out to my friends and ex-colleagues (read: non-technical communicators) and asked them the question, “What do you really think of the technical writing tribe?” I prepared myself for a volley of complaints and mails filled with angst against my fellow practitioners in the fine art of technical communications.  I admit, I also secretly hoped that at least some of them would have some nice things to say.

Yes, there was the expected outpouring of emotion against our tribe but there was also appreciation. Thanks to all of you who responded (and thanks also to those who did not respond – I will bother you next time around too, without doubt). Yes, we technical writers can be real shameless at times – we refuse to take a hint.

I’ll cover the responses to that question in two blog posts – this one is devoted to the brickbats and the next one will cover the bouquets.
 
  • A normal human being and a normal technical writer can never be the same person. (Gulp!) 
  • There is very little justification to the term Technical in the title Technical Writer. Most of the times, it takes immense effort to help a technical writer understand the technical aspects of a product. (Sheepishly – True. But I have always thought that being non-technical is an advantage for us because that way, we can force all answers in black and white and present all facts in the same colors.) 
  • We have an attitude that we throw around. (Oops! Sorry. Do we really?) We behave like we are a boon to mankind. (Grinning broadly. Are we not? Even if in a teeny-weeny way?)
  • Technical communicators are aliens because of these reasons. They don’t ‘speck’ the product, don’t code it, don’t test it, don’t sell it, don't use it, yet, they are instrumental in the success of the product. (Ahem - thanks but no thanks. It is true that we do not ‘speck’ and we do not code. But we do use the product and test it – we log bugs too. And, to my mind, after product managers, ours is the only group who can demo a product in its entirety – that is selling the product, right? To my mind, all these functions make us instrumental in the success of the product.)
  • As a technical writer, when you are tasked with writing a user manual for a product the least you can do is use the product. If that is not possible because of the complexity, at least observe someone using it and ask questions. (And here I am, thinking people always make excuses not to meet us because we ask way too many questions!)
  • Technical writers are not involved enough with the product – they don’t take enough ownership of the product. (I daresay, this statement has elements of truth. We are rectifying this anomaly by getting involved in the product development cycle right at the starting line - see earlier post.) The irony of taking ownership is that some people seem to think of us as one more reason for a delayed product release (which is empowering). 
  • Technical writers tend to think that their job is done once their deliverables (such as online help or user guide) are done. But in fact, a technical communicator must be answerable for far more critical questions – how accessible is the information to a user and is the user getting the help where he needs it. (True. Which is the reason why our deliverables are no longer limited to online help and user guides. We review every word in the English language that is up there on the user interface (page titles, section headers, instruction text, labels, buttons, error messages, and confirmation messages). We consider ourselves to be the first users of the product and point out where help is needed and how we can provide that help (embedded help, in line help, pop-ups). 
  • Most people do not have the same respect for technical communicators as they do for product engineering teams. This is largely because technical communicators do not understand the product inside-out. (True. But our challenge is not just understanding the product but understanding the developers as well.) 
  • All teams (read: all product engineering teams) face technical challenges, but the organization expects them to overcome these challenges. But technical writers are given plenty of leeway on this front. (True. And with a reason. If we were that technically savvy, we’d be coding. As writers, we are decoding! Jokes apart. This statement is true and is significant. I guess, it would be an asset for a technical writer to have a decent amount of technical know-how – but it can never be the main skill. The main skill for a technical writer is still his or her ability to communicate well and write well.)     

As I mull over writing the next part of this blog – one thing stands out – the list of compliments is shorter!

Urmilla Chandran
The author is co-founder and Director, Content Development at Steta
4 Comments
Rajendra Kankani
17/12/2013 04:28:19 pm

I think the list of compliments and complaints is fair enough. Also, the justification added by you are apt and would help the non-technical writers tribe understand your side of world and give due respect despite their complains...

Well done - keep blogging!!!

Thanks,
Raj

Reply
Urmilla Chandran
23/12/2013 03:39:29 pm

Thanks, Raj. It was an interesting exercise to carry out, as you can imagine. It also brought forth quite a few interesting perspectives. It helps to sit back and reflect on one's career and role in an organization, I suppose.

Reply
Ashish
21/12/2013 11:45:57 pm

This was definitely an interesting piece. The stuff that Technical writers do is unique. No one else can do the same. One aspect that's extremely value adding is that they can actually provide training / orientation on the product features to end users, besides the product specialist. On the personal side, they add a dash of panache to the development team. The literary stylists who dare to add flair to the despaired developmental activities.

Reply
Urmilla Chandran
22/12/2013 03:10:49 pm

Thanks for giving me more material for the second part of this blog post, Ashish! I especially liked the 'despaired developmental activities' bit.

Reply



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.