Re: Usability: Tutorial *chapter* or *manual*

Subject: Re: Usability: Tutorial *chapter* or *manual*
From: Dan Roberts <Dan_Roberts -at- IBI -dot- COM>
Date: Tue, 8 Apr 1997 10:09:04 EDT

I'd vote for a separate tutorial. 150 pages is quite enough for a
reader to keep in his head, esp when broken into several chapters. 150
pages of *one* chapter is too much for *me* to keep in my head. And,
IMHO, a manual of 350 pages is more than enough for a user guide, in
its own right.


______________________________ Reply Separator _________________________________
Subject: Usability: Tutorial *chapter* or *manual*
Author: Sue Heim <sue -at- ris -dot- risinc -dot- com> at tcpgate
Date: 4/8/97 10:00 AM


So, forget about the cost difference. If you had your choice, would
you prefer to have a 500 page manual that includes ONE WHOLE CHAPTER
on learning the program that is 150 pages long? Or would you prefer
to have a separate "Learning" booklet (likely saddle-stitched, btw)
and a separate user's guide?

TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html


Previous by Author: Re[2]: Web Server & Documents
Next by Author: Re[2]: Web Server & Documents
Previous by Thread: Usability: Tutorial *chapter* or *manual*
Next by Thread: Usability: Tutorial *chapter* or *manual* -Reply


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads