RE: Business Analyst vs. Tech Writer

Subject: RE: Business Analyst vs. Tech Writer
From: "James Barrow" <vrfour -at- verizon -dot- net>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 13 Mar 2007 05:20:45 -0700

>Nauman [mailto:naumansohail -at- gmail -dot- com]
<mailto:%5bmailto:naumansohail -at- gmail -dot- com%5d> said:

>>Karen [mailto:ekarenski-techwrl -at- yahoo -dot- com] wrote:

>>>Jim [mailto:vrfour -at- verizon -dot- net <mailto:vrfour -at- verizon -dot- net> ] wrote:
>>>

>>>How often are tech writers responsible for driving the requirements
gathering *and* documentation? How often are we tasked >>>with designing
formal software systems analysis and design methodologies? How often must we
understand underlying >>>business drivers and organization imperatives so
that we ask the right questions to ensure the complete discovery of product
>>>features and requirements?
>>

>>I think it's more important to stress your past accomplishments in the job
than the job title. I use the "Technical >>Writer/Business Analyst" title on
my resume.
>

>Now that my role kept moving from technical writing to information
development to business analysis. As stone of time kept >rolling on and on,
I felt life being a business analyst is more interesting rather just
documenting user manuals etc.



I see all of this as only good news for tech writers. And, along that same
line of thinking, bad news for Business Analysts. Since money is the bottom
line in business, wouldn't a company be more willing to give a tech writer
BA roles and responsibilities rather than hiring another resource? To be
honest, this is what's happening now with my current employer. They need
someone to finish gathering the requirements for a few projects, but the
budget/head-count doesn't allow for this until May. A light bulb
illuminated above my bosses head when he added [needed business reqs] +
[tech writer who could gather reqs] and came up with extra money for the
summer softball team ;^)



It seems to me that most Business Analyst roles and responsibilities are
something that most tech writers could learn/do to make them an almost
indispensable resource.



- Jim





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

Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual: http://www.helpandmanual.com

---
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-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

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


References:
Re: Business Analyst vs. Tech Writer: From: Nauman

Previous by Author: Business Analyst vs. Tech Writer
Next by Author: RE: Pet Peeves
Previous by Thread: Re: Business Analyst vs. Tech Writer
Next by Thread: RE: e-publishing a catalogue


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


Sponsored Ads