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: The Tools Tech Writers Use From:Janet Valade <janetv -at- MAIL -dot- SYSTECH -dot- COM> Date:Fri, 31 Jul 1998 10:35:07 -0700
> Adrienne Ferguson wrote:
> >I am conducting some research on the tools technical writers use in
> <snip>
> >Why, for instance, does MS Word seem to be a standard tool despite its
> >limitations ? <snip>
>
There are a lot of factors to consider when making software decisions. In
most companies, Word is already used throughout the company. If the tech
writers feel they would be more effective using different software, they
probably need to provide an analysis to prove their case. This analysis
needs to include all the factors: cost of tool-of-choice, time spent
converting source documents provided by others in the company from Word to
tool-of-choice, time spent converting documents from tool-of-choice to Word
to provide them to other people in the company, time spent converting
existing, current documents to tool-of-choice (or cost of maintaining
different documents in different formats), etc. versus time savings in
creating the document in tool-of-choice instead of Word.
If the tech writers write everything themselves or with minimal input from
other documentation, they can probably use their own software that no one
else needs to know. But if they integrate documentation written by others
in the company, it is possible to lose more time converting your source
documentation from Word to your tool-of-choice than you would lose just
using Word. It depends on what your source documentation is like and what
your end document is. The limitations of Word are not a problem for all
documentation, only for some types.
Reality is, if there is a compelling reason for people throughout the
company to share docs, the choice is likely to be Word (and probably should
be). It is not within the realm of probability that the VP of engineering
is going to learn FrameMaker. Nor should she. The techwriter is part of the
company and software decisions are, ideally, made based on the needs of the
entire company, not just on what is best for any individual segment of the
company.
What if you are a contractor? Who is going to maintain that document that
you left them in your tool-of-choice?
You can't get on-line reviews if you are using software that your reviewers
don't know or have. Your reviews will always be done via paper copies.
Janet
----
Janet Valade,
Technical Writer, Systech Corporation, San Diego, CA mailto:janetv -at- systech -dot- com
----------------------------------------------------------------------------
--------------------------------------------------
For every complex situation, there is a solution that is simple, neat, and
wrong.
