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: RE: Reviewiing Process with 12 Engineers at Once
Subject:RE: RE: Reviewiing Process with 12 Engineers at Once From:"GeneK" <gene -at- genek -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:13 Jun 2003 13:59:58 PDT
I'll second that,but also suggest that you establish a
time limit for discussions on any disagreements that arise
between the engineers, after which they get an action item
to resolve the issue offline (always assign the AI to the
person who wants to change the existing info in the doc if
you can, if not, take it yourself and schedule another mtg
just for them); if you let 2 or 3 people hold the rest of
your dozen hostage while they duke it out, the process will
be doomed.
Gene Kim-Eng
------- Original Message -------
On
Fri, 13 Jun 2003 12:26:28 -0600 Bill Burns?wrote:
So, it's doable, but have the engineers review BEFORE the meeting, not during. Resolve disagreements duiring the meeting, and collect markups. Don't try to enter the changes at the same time because you'll undoubtedly come up with follow-up questions.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
