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: Information Mapping From:Sarah Mahoney <smahoney -at- U -dot- WASHINGTON -dot- EDU> Date:Tue, 31 Aug 1993 07:48:39 -0700
I work for the Development Division (fundraising) here at the University
of Washington, Seattle. Our Vice President has implemented Information
Mapping as the standard for all our documentation, memos, etc...
I attended the seminar on writing policies and procedures using the
mapping method and it was very good. We have found it to be very useful
for writing, and it has helped to standardize the writing format for our
entire division. I would highly recommend it for user documentation.
-Sarah Mahoney
-Technical Communicator
-Alumni/Donor Information Systems
-Univ. of Wash., Seattle
On Mon, 30 Aug 1993, Michael Hacker wrote:
> Subject: Time:3:44 PM
> OFFICE MEMO Information Mapping Date:8/17/93
> Does anyone have experience with the Information Mapping Method? I'm looking
> for objective opinions on this method for developing structured user
> documentation. I've read promotional literature on Information Mapping and
I've
> seen documentation produced using this method; however, I'm looking for
> additional input. (I'm relatively new to this news group, so accept my
> apologies if this subject has already been debated.)
