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.
>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."
Right! A friend of mine worked for a company once where the Pubs manager
tried this approach and was told, "You *can* (increase the priority w/o
assigning more resources) and you will! It's your job to figure out
how!" Needless to say, the writers put in more than a few 60-70 hour
weeks over the next couple of months. They did manage to get the high
priority project *and* their own projects completed on time, but 3 of 5
writers left the company shortly thereafter, as did the Pubs manager.
>And if that doesn't work, send out a memo announcing that... you're
>putting together a quality reduction plan...
