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.
I have enjoyed the discussion of Info Mapping/Chunking etc. Development
methodologies such as Info Mapping add much value to the documentation
process. Recently, I was asked to develop procedures for system
administrators to configure a particular protocol on a Windows NT server.
procedures had to be developed using Info Mapping methodology.
Generally, I agree with Info Mapping's requirement of seven items in the
short- term memory. However, in the case of Windows NT, I had to throw
idea right out the window (no pun intended). Because Windows NT is a GUI
based network OS, each time I introduced a new window, I had to explain
every entry it contained (customer requirement).
Some windows had up to 12 entries. Between this problem and the fact that
I had to add special notes all the time ( to remind the system
administrator that if
you did item D, make sure items A, B, and C were complete), I felt that
subject matter made Info Mapping difficult.
INFO MAPPING EVALUATION: If you consider all the required tasks in this
step, I would say I went over the RULE OF SEVEN by two or three. Mr Horn
would not be happy! Of course, Mr. Horn was not paying the bills on this
ptm123 -at- aol -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-