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.
Has anyone surveyed high-tech industries in their region to find their
attitudes toward and needs for technical writers?
We'd like to survey our local high-tech industries to see
* what they use technical writers for
* what their documentation needs are
and, without asking directly
* what their opinions of and attitudes toward technical writers are
Several of us in the Eastern Ontario chapter of STC are considering doing
so. Before we do, we'd like to know if anyone else has done so. If so, we
would be most grateful if you would allow us to base our questions on the
ones you used. This would mean we could compare our results with
yours--which could also be useful to you if you were interested in sharing
results.
Also, we'd like to get management responses, either by
* asking vice-presidents or project managers directly, or
* asking documentation managers what their supervisors' attitudes are
Has anyone else done this?
Does anyone have any suggestions as to what to include as questions?
- Carl Stieren
Senior Information Developer
Simware, Inc. / Ottawa, Ontario
Member, Eastern Ontario Chapter, STC
Member, SIGDOC
P.S. We suspect we may find some out-of-date ideas of what a technical
writer does and what documentation can do. We don't know how large a
fraction of industries will echo these misconceptions, though.
The next step will be to build a program to correct these misconceptions, if
any exist.
- Carl
// The opinions expressed herein are mine and not those of Simware, Inc. //