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.
Bob Handlin wrote about Information Mapping, and a concern that:
>My initial impression is that it helps prevent bad writing by
>making everybody mediocre, and makes great writing more
>difficult by being restrictive.
I haven't taken the Info Mapping courses yet, but I'm signed up
to do so. I'm gonna guess that it's like any other technique: once you get
out of class and start to apply the lessons,
it's up to you to decide what to follow and what to disregard.
If an Info Mapping method is too restrictive, write your manual
in the way that works best.
Hey, if you come up with enough variations, and it works well
enough, you could start your -own- method and teach all the rest
of us how it works!
Rick Lippincott
rjlippincott -at- delphi -dot- com
