RE: encouraging learning by experimentation?

[Kim Roper <kim -dot- roper -at- pixelink -dot- com>]

Lois Patterson pointed out:
> 
> From what I understood, Hackos suggested using the
> technique in documentation as well. However, I
> obviously don't have a cite. Another thing she
> mentioned about user docs was not spelling out to the
> user how to do particular simple tasks, as this would
> encourage the user to figure it out on his own.
> 

Caveat:  Lois, I know you're paraphrasing Hackos, so I'm not taking issue
with you.

I still haven't finished numbering and writing Roper's Rules of Technical
Writing, but these ones come to mind:
  Rule 3:  Don't force 'em to think.
   Rule 3a:  Don't make 'em hunt for information they need *right now*.
It's a manual, not a mystery novel. 
  Rule 4:  Don't force 'em to slow down or stop before they get to where
they want to be.

Cheers ... Kim
kim.roper at pixelink.com
http://www.pixelink.com/



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out SnagIt - The Screen Capture Standard!
Download a free 30-day trial from http://www.techsmith.com/rdr/txt/twr
Find out what all the other tech writers, including Dan, already know!

Order RoboHelp X3 in December and receive $100 mail in rebate, FREE WebHelp
Merge Module and the new RoboPDF - add powerful PDF output functionality
to RoboHelp X3. Order online today at http://www.ehelp.com/techwr-l

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