Re: Information Mapping

["Pro TechWriter" <pro -dot- techwriter -at- gmail -dot- com>]

Hmmm. Well, I use "good standard" documentation techniques and Information
Mapping. It's just another methodology, neither the best nor the worst out
there. And I do have experience with it, as well as experience rewriting
Infomapped documents created by non-writers.

Infomapping does seem to help those who don't have formal writing experience
gather their thoughts and put them on paper in a coherent way. I've seen a
couple of non-technical writers here provide me with really creditable
documentation that needed some editing, but that was it.

It surprises me that you believe that all documentation created with this
methodology is "unusable." I've worked for many large and small companies
that use it--I haven't seen that many complaints, but professional writers
were using it--not non-writers.

Infomapping does have drawbacks: the template can be fussy, the presentation
is busy, and the recommendations (in my opinion) for paper documentation and
online is a bit dated. But, it is a useful tool if you need to get a whole
company or department speaking the same language and using the same method
to begin to document their procedures.

Of course, most of the places I have worked (American Airlines, Motorola,
Xerox, and so on) have modified the method to fit their environment.

Just my $.02, but I do have experience using this, have been trained in it,
and understand that it has good and bad points--not just bad ones.

PT


On 11/1/06, Traci Pearson <pearsontechcomm -at- comcast -dot- net> wrote: