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.
>Robert -
>These are all good points, and I have used many of them in the past.
>However, at some companies, it doesn't matter how hard Tech Pubs wants
>to stand its ground - when the top dog in your division issues an edict
>that Tech Pubs *will* give a certain project top priority, it's hard to
>argue without jeopardizing your job. Sometimes these edicts come down
>from on high and there's not much you can do other than say "Yes, Sir!"
>(cheerfully, of course!). ;~D
No, of course you agree. But you instantly move on to resource allocation.
"I can't increase the priority without assigning more resources to it. All
my resources are assigned. Who gets bumped?" Then repeat this statement
over and over while they try to wiggle out, with the occasional, "And go
sign up the other departments to spend extra time supporting us, because a
compressed development cycle is very dependent on quick response from the
SME's."
And if that doesn't work, send out a memo announcing that, due to the level
of overload and the uncontrolled nature of the problems it causes, you're
putting together a quality reduction plan to put the process back into
control, and would like everyone's feedback.
-- Robert
--
Robert Plamondon * High-Tech Technical Writing
36475 Norton Creek Road * Blodgett OR 97326
541-453-5841 * Fax: 541-453-4139 mailto:robert -at- plamondon -dot- com * http://www.pioneer.net/~robertp
