Quote:
Originally Posted by DNSB
At work we once rolled out an new piece of software with an online manual. The first time you opened the program, you were presented with the manual and required to read all 16 pages with a checkbox at the bottom of the last page to confirm that you had read the manual. The average user read the manual in under 10 seconds and then whinged at the help desk about items covered in the manual. The canned responses were basically, "This is covered on the <insert page number> of the manual. Please take more than the <insert recorded length of time> to re-read the manual."
|
Ahah LOL. Exactly what I mean by peoples don't like reading manuals.
Peoples want the things start to work as soon as possible, understand and fix it later.
To extend my thought, their is
one thing that the user will always read: is the Instalation Manual, aka the minimal steps required for the things to work.
In this short time, you can subliminaly infuse some additional knowledge to the user but be caution to not be too much or verbose beyond the minimum required. That why in most part it will resume to a "You can change this later here".
At this end, the "Welcome wizzard" is quite great to that, even if it would probably be possible to add one or two pieces of information in the last page (but no more page).