common problems for tech writers

[Kit Warfield <KitW -at- ASYMETRIX -dot- COM>]

Sorry to take up bandwidth with what apparently has passed before, but I
can't resist the opportunity to bark about what's tripped me up along the
way!

I've worked in the software biz for 12 years.  I've worked for four
different companies.  In every company, I've encountered:

1.  Lack of visual freeze
2.  Lack of specs, or outdated specs
3.  Schedules set and driven by engineering (or marketing) without input
from Documentation -- e.g. "here's our ship date, so how much time do you
need?"   Docs seem to always end up on the "critical path" according to the
master schedule, but I've _never_ seen us delay the actual ship date!    We
get to play the bad guys and say "we need more time" and watch everyone
holler about it, then, quietly, it's revealed that they, too, needed more
time.....

And, finally, I'm sure what follows is not a common situation at all, but I
want to tell you about my most challenging situation:

1.  The developers were in Europe
2.  I, the writer, was in Washington State (ergo, an 8-hour time difference)

3.  I had 90 days to write a 500-page manual
4.  The product was being developed for the PC, I was given a Mac to work
with.
5.  I was warned from the outset that "the senior developer doesn't suffer
fools -- don't bother asking him any simple questions because he'll just
growl at you"   (over the phone or e-mail, or fax)
6. The senior marketing person made radical, drastic changes to BLUELINES

And you know what?  I loved that company most of all!  The senior developer
and I hit it off, thankfully, and altho we worked round the clock for those
90 days, we got the manual & product out the door on time.  The company gave
me a $$ bonus AND a one-month trip to Europe!  And the manual won an
Excellence award at the next year's STC competition!

More than my $.02, but thanks for listening.

Cheers,
 --kw
kitw -at- asymetrix -dot- com