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.
On Sun, Jan 12, 2003 at 09:19:10PM -0700, kcronin -at- daleen -dot- com wrote:
> I live and die by deadlines at my gig. I view deadlines as being etched in
> stone. Admittedly sometimes they get re-etched, but not by me - that's
> just the project itself floating. But wherever they set them, I never miss
> them. Period. I expect the same of my team members.
>
> BUT...
>
> In order to never miss them, I adjust the scope of my efforts and my final
> expectations to be in proportion to the time allotted.
>
> Want it done in three weeks? You got it. Give me six weeks and it will be
> even better, but I'll give you SOMETHING in three.
Ah. I adopt a different working model, which is one reason why I have trouble
making deadlines: The manuscript will be done when I'm satisfied with it, and
not before.
That requires, of course, editors who are willing to drink Maalox and
explain to *their* superiors why I'm not done yet. And my prinicple
isn't completely absolute, in the sense that I'll *try* to make my
deadlines and sometimes end up throwing out material in order not to
make the manuscript even later than it already is.
Also, "when I'm satisfied" is a somewhat relative term. I despise my own
writing, so I'm never really "satisfied" with it. Mmaybe that would be
better phrased as "when my dissatisfaction has diminished to the point
that I'm willing to release the manuscript."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
---
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.
