Re: Developing a schedule.

[TechComm Dood <techcommdood -at- gmail -dot- com>]

> So just a question that omes to mind: If you (just) test all the
> procedures that you've written, how do you know if you've written all
> the procedures.
> 
> Reviews by SMEs can tell you "Oh, you can do this, this, and this too."

And reviews by QA can tell you "Oh, no one would ever want to do it
that way." and "But when you do this you need to keep in mind..."

And reviews by Tech Support will tell you "If you write it like this
we're going to be slammed with calls. Give them the easiest way - this
way - and provide more info as needed for more advanced users."

It really helps to get a wide variety of reviewers because no one
person or role will hit all important issues in the document. In fact,
you'll never hit all issues, as someone will always have a beef about
something, but do broaden your review base to catch all the glaring
issues.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl

WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l 

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -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.