RE: Help on Procedure Writing

[Tom Murrell <trmurrell -at- yahoo -dot- com>]

--- John Fleming <johntwrl -at- hotmail -dot- com> wrote (in part):
> 
> As a personal observation of procedure writing, when writing a procedure, 
> make sure you include all the relevant information needed by a person to 
> complete the task.  You will need to emphaisize the what rather than the 
> why.

John's advice is really good. To which I would add one other small, little
thing. Don't accept a procedure from someone else and simply put it in your
document. TEST IT. In my experience, the biggest problem with procedures is
that no one ever actually tried to do it.

Do the procedure, and you'll find out what's missing that a user will need.

=====
Tom Murrell
Lead Technical Writer
Alliance Data Systems
Columbus, Ohio
mailto:tmurrell -at- columbus -dot- rr -dot- com
Personal Web Page - http://home.columbus.rr.com/murrell/index.html
Page Last Updated 07/15/01

__________________________________________________
Do You Yahoo!?
Buy the perfect holiday gifts at Yahoo! Shopping.
http://shopping.yahoo.com

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