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.
Subject:RE: Info mapping terminology From:Syed Ahmed <SAhmed -at- DKSYSTEMS -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 19 Mar 2002 09:34:07 -0600
Irene Wong asked:
>My question
>Does the Info Mapping theory say that one document can only have one
> type of
>information in it? Surely not.
As Michael and Stan have said, the answer is absolutely not. A thorough
document can, and probably should, contain as many of these "information
types" as necessary. Once you've determined your information types, and
have separated them accordingly, you can then place them into a single doc,
following the most logical and helpful outline to present the information.
You're thinking is correct, in that a helpful document will often times
contain the processes and procedures and facts, etc.
One reason I can see to place the varying information types into separate
documents is if you're creating smaller, specific chunks of information for
select audiences. For example, a "process" doc may only be used by the user
group, whereas the tech community may only need a "procedures" doc because
they're not really interested in the business rules that drive your product.
However, there is no legitimate reason why these several types can't be
compiled into one thorough doc. And this larger doc, if organized well, can
again be broken down into smaller chunks for audiences with more specific
needs. This reversed use of information chunking is one of the key
principles underlying the Information Mapping approach: If the information
you have at hand is organized and "chunked" into smaller, easier-to-digest
pieces, these categorized and labeled packets of information can be inserted
or removed without disrupting the flow of the original doc, as well as
provide the basis for newer, smaller docs. The actual process of "chunking"
can be time intensive and, at times excessive, but info types like
"procedures" and "process" "facts" should be fairly obvious.
HTH,
Syed
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
