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: Like long hours? From:Andrew Plato <gilliankitty -at- yahoo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 7 Aug 2002 07:17:25 -0700 (PDT)
--- Bill Swallow <wswallow -at- nycap -dot- rr -dot- com> wrote:
> ::: Planning projects isn't really an aspect of this discussion
> ::: Bill.
> Oh it most certainly is. In many cases the reason why people end up
> working overtime is to finish a project that was horribly planned. I've
> met few project leads who plan a project and don't peg every resource at
> 100%. The 100% assumes overtime right off the bat, and the next project
> is usually based on the timliness of the previous, so if it was
> completed reasonably on-time with resources at 20 hours overtime a week,
> then the cycle only gets worse from there.
> ::: We're talking about employment and expectations on the job.
> Which has nothing to do with the way projects are planned, right?
Well it does, but not as a function of employment. You take a job to fill a need.
That need is to write documents. You fulfill that need by developing projects and
completing them. You complete them by managing them properly. So as you can see,
the management of projects is a few layers removed from employment issues.
You also seem to be assuming here that some other faceless tyrant is managing
these projects and not giving you any say whatsoever in the process. This may be
the case in some places, but more often than not, writers are simply given a list
of docs that need to be done and some deadlines.
It is also the nature of documentation to have natural crunch zones. Since it is
often the case that some aspects of a document cannot be completed until a
product is fully designed and tested, its natural to have a lot of "catch up" in
the latter parts of a project. Something that still seems to boggle even the best
Do You Yahoo!?
Yahoo! Health - Feel better, live better http://health.yahoo.com
Save up to 50% with RoboHelp Deluxe. Get 2 great products for 1 low price!
You'll get RoboHelp Office PLUS RoboDemo, the software demonstration tool
that everyone's been talking about. Check it out and save! http://www.ehelp.com/techwr-l
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.