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.
Re: SMEs/QA don't have time to review the documentation
Subject:Re: SMEs/QA don't have time to review the documentation From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:"SB" <sylvia -dot- braunstein -at- gmail -dot- com>, "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 30 May 2008 07:21:10 -0700
Everybody here knows that we don't get to ship product
without its documentation (actually, we're in a federally
regulated industry where we're not even allowed to begin
development work on a product without first submitting its
proposed design and performance specs for government
approval and an official "project number"). Our documents
are project milestones, and if they are not met to schedule,
the project grinds to a halt and further development is
frozen until the milestone is met. So in the (highly unlikely)
event that someone starts doing something like this, a
memo that uses words like "day-to-day schedule slip" perks
the process up considerably, since our company president
is required to make a weekly progress report on all our
development projects to the company's board of directors.
Gene Kim-Eng
----- Original Message -----
From: "SB" <sylvia -dot- braunstein -at- gmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Friday, May 30, 2008 5:23 AM
Subject: SMEs/QA don't have time to review the documentation
>I would like to know how you are getting the material when doing the
> technical writing and how it should be done.
>Some of the teams have to be chased senseless. They never have
>the time for technical writing. They always dump the reviews on the
>same one or two people instead of splitting the chapters among a
>few people who end up really resenting this and end up not cooperating.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
