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:Documentation Standards? From:mclaughlin -at- HOU -dot- SPERRY-SUN -dot- COM Date:Wed, 10 May 1995 16:00:05 CST
I'm trying to learn more about developing standards for a small
documentation department (three writers). We put out hundreds of pages
per month. We have worked for a while with unspoken standards, but we
sometimes end up with several related procedures that use different
words to explain the same task.
Is this breed of inconsistency confusing to the user, even if a very
basic action is being described? For example, is it okay to tell
someone to "enter the value onto Screen 35" in one set of instructions
and then tell them to "type the value onto Screen 35" in another set?
Has anyone out there dealt with these issues?
Has anyone developed a set of standards from scratch? If so, how did
you go about it?
Should this be a democratic event, or should one person lay down the
How much leeway should an individual writer have when it comes to
Any suggestions would be greatly appreciated.
Danna McLaughlin (These are my opinions, not my employer's)