RE: FW: Extreme Technical Writing (was RE: Flexibility and changing r equirements)

["Earl Cooley" <shiva -at- io -dot- com>]

> Obviously these steps are only a very high level overview, but 
> the iterative nature is obvious.  There is an extremely high 
> level of communication between our programmers and our writers, 
> to the point that the writers serve as test users during 
> development.  In fact, that writers at my company get to know the 
> systems so intimately that they are the ones responsible for 
> handling support calls after rollout. 

Oh, no, not phone support again! I like testing just fine, 
but one of my key rationalizations for entering the technical 
writing field was the thought that by controlling the quality 
of the documentation, I could anticipate user support needs 
so that whoever does do phone support has a much less stressful 
job than otherwise might have been the case. I think of (at 
least this branch of) technical writing as a force multiplier 
for user support. 

--
 e=sc^3 (shiva -at- io -dot- com) Earl Cooley III

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
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.