TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: TWs and BAs From:Elna Tymes <etymes -at- LTS -dot- COM> Date:Wed, 1 Apr 1998 10:39:07 -0800
Catie Easley wrote:
> The BA feels he should be doing 90%+ of the writing of the
> concept, requirements, and analysis documents. That leaves me writing
> user guides -- not nearly as challenging. I'm not sure I want to be a
> BA, but I want to have some ownership of the documents being produced.
Hooooo boy! You've just stepped in the mess that a lot of us are more
and more likely to encounter in these days of moving to ERP solutions.
We have found that, as writers with a lot of business experience, we
are in demand to help with business analysis and then writing the
documents that go with the analysis. However, we've already been
'qualified' by our clients as having the necessary business training and
experience. Most tech writers don't have that training and experience,
and are competing for credibility with "business analysts" who do have
that kind of background.
My take is that the situation is going to vary from company to company,
depending on what kinds of credentials are most valuable at the time.
