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: The last minute crunch From:"Jim Shaeffer" <jims -at- spsi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 28 Aug 2003 15:04:24 -0400
In general, it helps to make your workload visible.
Being part of a bug tracking system is one way to do this.
Also, being required to enter their requests into such a
system cuts way down on the number of requests that people
make. That was my experience, anyway.
If formal bug tracking is not in your future, maintain a
written list, paper or on-screen, of your tasks and who they
are for. When a head pops in asking for something, point to
the list and ask the _requester_ where it goes in priority.
And return to TECHWR-L any time you need support and
sympathy. Most of us go through the Last Minute Crunch time
and time again. (Every bottleneck you remove from a system
just tends to expose other bottlenecks.)