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:(Fwd) Too many tables in documentation From:Bernice Kieffer <bernice_kieffer -at- MENTORG -dot- COM> Date:Thu, 30 Jan 1997 09:43:03 PST
--- Forwarded mail from Heidi Margenau <Heidi_Margenau/USG -at- USGROUP -dot- COM>
If you have looked through "all types of different documentation related to our
field, and no one seems to be running into this problem", I would hazard to
guess that they have taken a more process oriented approach to the
documentation. You might try using the same type of approach. Rather then just
listing all the fields and the action associated with them, write a procedure
to tell the user how best to fill in each screen with the appropriate
information required. This way you can include a screen shot for orientation
and eliminate the need for all the tables.
Technical Writer/Training Developer
bernice_kieffer -at- mentorg -dot- com