TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Placement of Question and Answer Sections in a User Guide
Subject:Re: Placement of Question and Answer Sections in a User Guide From:"Jo Baer" <jbaer -at- tcfbank -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 20 Mar 2002 12:55:04 -0600
My philosophy for pretty much any procedure, policy, etc., is to put the
information where the user needs it. This may mean you have a chunk of
information followed by questions and answers, another chunk of information
followed by questions and answers, and so on.
Think back to some of the better textbooks and training materials you've seen.
Often they treat a digestible chunk of information, possibly give a one- or
two-sentence summary, then follow it with questions and answers (or just
questions if you're supposed to provide the answers).
If your goal is to avoid making the user think, I think some variation on this
strategy is a good approach. After all, thinking about where the Q & A is, and
whether to use it, is going to be as foreign to some users as thinking through
the material they have just read.
Jo, whose philosophies have yet to make her rich, or even famous
--
Jo Baer
Senior Technical Writer
TCF National Bank
Minneapolis, Minnesota
jbaer -at- -dot- tcfbank -dot- com
The mome rath isn't born that could outgrabe me.
Nicol Williamson
"Douglas S. Bailey (AL)" wrote:
> I'm creating a software user guide, and am planning to include a list of
> commonly asked questions, though not necessarily as an official FAQ. Do you
> think it would make sense to include it at the front of the document,
> immediately after the (quite small) installation section? Or is the more
> traditional method (to include it at the back, perhaps as an Appendix)
> better?
>
> I'm trying to help the user avoid having to think, since that generally is
> how they prefer to operate. (No offense intended.) IMO when a user decides
> he needs help with something, he generally has a question he wants answered.
> I think it might be easer for the user to find the Q&A section if it's right
> up front. Of course, the answers will refer the user to the appropriate
> sections deeper in the user guide for more information.
>
> Is there a glaring flaw in my strategy that I'm overlooking?
>
> --Doug
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
---
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.