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: Preparation for a phone screen interview From:jgarison -at- ide -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 10 Jan 2003 08:13:46 -0500
Susan, I agree 100%. I, too, pride myself on never missing a deadline in
almost 30 years on the job. It all comes down to doing the best you can with
the time allotted.
My approach is generally to get a little bit of everything documented by the
earliest possible deadline, with extra time and attention on the 'hardest'
stuff for people to 'get'. If I get more time, I use it appropriately,
filling in more depth in the places where it is needed most. If I get even
more time, I continue in that vein. Eventually, I either get it ALL done, or
we ship. But regardless, I am always ready with the best possible stuff in
shippable form on a potential release day.
I know what the stuff that needs to be explained is, and I have to get it
out on time. If I have a week, I produce the most appropriate stuff that I
can in that week. If I have a day, I do the best right stuff in a day. If I
have an hour, ditto.
And if I only have 5 minutes, I still do the best I can: "Check back later
for complete documentation."
John G
>>-----Original Message-----
>>From: Susan W. Gallagher [mailto:sgallagher5 -at- cox -dot- net]
>>
>>When you're writing documentation, you can edit and rewrite
>>and perfect and add features all you want until the day of
>>the deadline. Then you're done. If you document does not go
>>out the door, the product doesn't get sold, your paycheck
>>doesn't happen.
>>
>>Just like you save that unopened box of christmas lights
>>until next year, you save that enhancement until next rev.
>>You can run around like a chicken without a head all you
>>want. You can pull your 80-hour weeks -- I've done my
>>share. But when delivery day comes along, you deliver and
>>go on with life.
>>
>>In 20 years, I have never missed a deadline. I have played
>>Deadline Chicken with the devs lots of times. And I've told
>>management that they can't have what they want in the time
>>allotted lots of times. But when the schedule says the docs
>>go out the door, they go.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.