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: Damage Control From:"Wittel, Teresa J." <WITTTJ -at- NCSLINK -dot- COM> Date:Thu, 21 Aug 1997 12:52:00 -0700
I have experienced this sort of problem before and usually the fix
involves what Sella was saying. Open communication channels everywhere;
re-negotiate the release date, remove obstacles, or re-define the
project scope. If that fails, we've simply poured (known) experienced
people into the fray, who tend to work until the wee hours of the
morn...
Not to say that is the best solution, but it is the only one I know.
However, I've usually worked in large team-oriented departments where
people "pitch in" to help resolve crises. Sorry, I don't have more
suggestions.
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
