RE: Best Practice for reviewing documents

[Tony Markos <ajmarkos -at- yahoo -dot- com>]

Best practice for reviewing documents: Don't rely on
document reviews.  

TWs asking for (text based) document reviews is like
the development staff asking for reviews on design
documents: you may get some feedback/corrections - but
it is only going to be on relatively minor things.  

Your fundamental organization may be messed up, or
your understanding may have large logicial holes in
it, but asking for a document review is never going to
bring such to light.

To get important feedback, you need to use devices
specifically designed for end-user review/walthroughs.
 And only certain analysis devices fit the bill.

Tony Markos

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author 
content and configure Help in MS Word or any HTML editor. No 
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005

---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.