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

Subject: Re: Usability: Tutorial *chapter* or *manual*
From: Michael Clark <mclark -at- MTU -dot- EDU>
Date: Mon, 7 Apr 1997 20:03:02 -0400

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

My 1.5 cents, after tax:

Users often only need the tutorial for a relatively small part (the
beginning) of their experience with the software. After that, a
tutorial only serves as xx pages of dead, heavy weight every time the
user reaches for reference material.

So unless you expect the "tutoring" to be ongoing, I'd separate them.

Mike

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: Salary Requirements
Next by Author: Re: Usability: Tutorial *chapter* or *manual*
Previous by Thread: Usability: Tutorial *chapter* or *manual*
Next by Thread: Re: Usability: Tutorial *chapter* or *manual*


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

Sponsored Ads


Sponsored Ads