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.
You'll notice it says you did something very few people do. That is,
most other people find an info mapping layout improves their ability to
find and process information. The amount of white space, the separating
out, the captions, all contribute to this. Chunking the information and
lots of tables and lists do too.
If the format made no difference to you, that's terrific. But most of
your readers will probably find it easier to get what they need quickly
when it's not buried big, dense paragraphs (like the user manual I just
finished re-writing, and reformatting! eeesh.)
And that, in my opinion, is what's so great about Information Mapping. I
also use a 2-column table in Word: 1.9" and 3.99 (with a .5" gutter and
a comfortable outside margin for two-sided printing).
On the other hand, I wouldn't spend all that money on the seminar! I
was given this format to use many many assignments ago, by someone who
HAD gone for the formal training. It's so sensible, and so in line with
everything I know about good technical writing, I use it for almost
everything. (The revised-reformatted manual has been very well
received, incidentally.)
Maggie Secara
John Posada wrote:
> Hi, guys...
>
> I checked out their site and they have a little test to show how
> effective information mapping is. I took the test...following is a
> piece of the results:
>
> --------------
>
> Congratulations!
>
> You did something that few people do... You found the requested
> information in the typical document as fast or slightly faster
> than in the "Mapped" document.
>
> --------------
>
> So...what's so great about Information Mapping? :-)
>
>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.0.1457.3">
</HEAD>
<BODY>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2>You'll notice it says you did =
something very few people do. That is, most other people find an info =
mapping layout improves their ability to find and process information. =
The amount of white space, the separating out, the captions, all =
contribute to this. Chunking the information and lots of tables and =
lists do too. </FONT></P>
<BR>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2>If the format made no difference to =
you, that's terrific. But most of your readers will probably find it =
easier to get what they need quickly when it's not buried big, dense =
paragraphs (like the user manual I just finished re-writing, and =
reformatting! eeesh.)</FONT></P>
<BR>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2>And that, in my opinion, is what's =
so great about Information Mapping. I also use a 2-column table in =
Word: 1.9" and 3.99 (with a .5" gutter and a comfortable =
outside margin for two-sided printing). </FONT></P>
<BR>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2>On the other hand, I wouldn't spend =
all that money on the seminar! I was given this format to use =
many many assignments ago, by someone who HAD gone for the formal =
training. It's so sensible, and so in line with everything I know about =
good technical writing, I use it for almost everything. (The =
revised-reformatted manual has been very well received, =
incidentally.)</FONT></P>
<BR>
<P><FONT COLOR=3D"#0000FF" SIZE=3D2>Maggie Secara</FONT>
<BR>
<BR>
<BR><FONT SIZE=3D1 FACE=3D"Tahoma">John Posada wrote:</FONT>
<BR>
<BR>
<UL><P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Hi, =
guys...</FONT>
<BR>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">I checked out their =
site and they have a little test to show how effective information =
mapping is. I took the test...following is a piece of the =
results:</FONT></P>
<BR>
<P><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">--------------</FONT>
<BR>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">Congratulations!</FONT>
<BR>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial"> =
You did something that few people do... You found the requested =
information in the typical document as fast or slightly =
faster</FONT></P>
<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial"> =
than in the "Mapped" document.</FONT>
<BR>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 =
FACE=3D"Arial">--------------</FONT>
<BR>
<BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">So...what's so =
great about Information Mapping? :-)</FONT>
<BR>
<BR>
</P>
</UL>
</BODY>
</HTML>
------ =_NextPart_001_01BE4459.6FDEE7D0--
