Reading Books vs. Asking Questions

Subject: Reading Books vs. Asking Questions
From: "Chris Knight" <cknight -at- attcanada -dot- ca>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 27 Feb 2002 14:06:41 -0800

In the course of his post on "Tired of Giving Free Advice", which I found
quite agreeable, Ed Manley wrote:
<<
"I absolutely have to multitask, have to make the most of every opportunity
to learn something new. I must be able to get to the heart of the issue
rapidly, and reading books is rarely the way to learn quickly. Asking
questions is. Consequently, I am not one bit hesitant to ask the author of
an article for information.
>>

All us writers would do well to remember that "reading books is rarely the
way to learn quickly. Asking questions is ". As I recall, there was research
done to support this contention--interviewing people about their sources of
information--I wish I could remember or reference this research.

Of course, our organizations can't actually talk with everyone who may have
questions, so we still need books. It seems to me, however, that we should
systematically look for ways to make our writing *resemble* or *support* a
question-and-answer approach.

A rigorous task orientation helps, since it allows the reader to search for
the desired information (a form of asking questions) within a set of tasks.
Making writing procedural, as far as possible, helps for the same reason.
Good navigation (headings, running headers and footers) helps to support
readers searches.
A thorough, task-oriented, fully inverted, index is critical; this allows
readers to locate information using keywords of their own choice--another
form of answering a question.
I do not agree with using actual questions (i.e. the FAQ approach) as THE
structure for information (too amorphous and sprawling), but adding a FAQ
section to an already well-structured document can be helpful.
Including any questions that are actually asked of customer-support
personnel is a no-brainer, but I also like to see if such questions indicate
that the document needs to be improved. If a customer question indicates we
have failed to get a high-level concept across, I'll add a conceptual
overview. Often, customer questions indicate difficulty *finding* the
information, in which case I look for gaps and re-examine the document
organization.

Anyone have other thoughts on this?

Chris
_____________________________________
Christopher Knight, Technical Communication Architect
http://members.attcanada.ca/~cknight/
E-mail: cknight -at- attcanada -dot- ca
Phone: 604 877 0074


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Now's a great time to buy RoboHelp! You'll get SnagIt screen capture
software and a $200 onsite training voucher FREE when you buy RoboHelp
Office or RoboHelp Enterprise. Hurry, this offer expires February 28, 2002. www.ehelp.com/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

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


Follow-Ups:

Previous by Author: Review Process
Next by Author: RE: How is the job market in your area?
Previous by Thread: Review Process
Next by Thread: Re: Reading Books vs. Asking Questions


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

Sponsored Ads


Sponsored Ads