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:Internal study From:Kristen Lorenz <klor -at- INTFACE -dot- COM> Date:Fri, 10 Oct 1997 15:13:18 -0400
For my grad school research project I am conducting a review of our
documentation. Since our resources are few, I am going to begin by doing
an internal review. After which I can build on to it and spearhead an
external review of our users.
Communication is a BIG problem here, and as a result, our documentation
process is rushed, incorrect, and often the last thing on anyone's mind.
Anyway - I am going to be talking to departments (engineering, tech.
support, quality control) to help me understand their jobs, frustrations
with documentation, concerns (if any, for that matter), in hopes of
forming better relationships and methods of working with them to
receive/review product information early in the cycle - before it hits
I'm doing 4 things:
* preliminary survey (did this today)
* editing session (not sure what will be reviewed yet - may be a
comparison of old layout to the new one)
* evaluation of internal review
Anyone else ever done something like this? Any advice, comments would