Process Documentation

["Lorraine Kiewiet" <Lorraine -dot- Kiewiet -at- mullinconsulting -dot- com>]

Hi Wrlers,
By next Tuesday, I have to come up with some ideas for documenting a work process. (This is about how other departments at our company make requests for software enhancements, or report bugs, or other ad hoc requests. The process now is that they interrupt QA people and/or programmers and the squeakiest wheel gets the grease.) Our company is implementing an intranet tool that they will use to make the requests, with a back-end that we will use to see what's in the pipeline and manage it.
 
I'm not in QA and have very little experience documenting work processes (Help and install guides are my bag). Where do I start?  
 
Thanks!

Lorraine Kiewiet
Senior Technical Writer





^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l

Acrobat & FrameMaker Seminars: PDF Best Practices, FrameMaker-to-Acrobat
Advanced Techniques, FM Template Design, Single Sourcing with FrameMaker
in Brussels (Oct), and in Montreal & Dallas (Dec): http://www.microtype.com/1

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