The Future of Tech Writing In America

Subject: The Future of Tech Writing In America
From: "William Sherman" <bsherman77 -at- embarqmail -dot- com>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Sat, 19 May 2012 16:16:30 -0400

I started a project recently that may have a glimpse of what many of us will
be facing in the future.

A large entertainment company outsources their infrastructure and data
support to a vendor. They have probably done this for years, I don't know.
Just recently, the contract for this support went to an Indian company and
so the vendor brought over a large team to do the transition work and
prepare to take everything, or as much as if feasible, to India to provide
support. However, they have had some snag on documentation, so they began a
hunt for a somewhat local technical writer to get all the documentation in
order in a two month timeframe. After that time, with it all done and
accepted, the documentation will also go to India for all updates and
maintenance.

My guess is that they had a problem trying to get an American spin on the
docs so that they fit into the American way of speaking and such. I'm
guessing that is why I have the initial shot at this, and once it is set in
an American tone, they can probably maintain it over there.

It is kind of ironic I'm on this since about 7 years ago, I was working at a
company that was trying to have roughly one fourth of the documentation
handled by a team in India. The rework and learning curve was such that
after 3 years, we called it quits as it was cheaper to do it in one or two
passes in the US than 6 to 10 passes in India. Now I'm on the other side of
the process.



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Follow-Ups:

References:
What does this code stand for?: From: John Posada
Re: What does this code stand for?: From: Phil Snow Leopard
Re: What does this code stand for?: From: John Posada
RE: What does this code stand for?: From: Combs, Richard

Previous by Author: Re: tech writing recruiters
Next by Author: RE: Easy photo knockout (masking)
Previous by Thread: RE: What does this code stand for?
Next by Thread: Re: The Future of Tech Writing In America


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads