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: Style Guide or Style Edict? From:DWeber <dweber -at- ISDLINK1 -dot- HISD -dot- HARRIS -dot- COM> Date:Fri, 17 Jan 1997 08:52:22 EST
The program I graduated from strongly emphasized the use of style
guides as a basis for consistency. I tend to agree with this,
especially when you have multiple writers working on the same project.
The problem I've run into when companies don't conform to a style
guide...is that there are many inconsistencies in voice, format, and
overall presentation. I write commercial software manuals as well as
government manuals.....and I find it frustrating when there is a lot
of "clean up" work at the end....trying to get everyone's work to look
My company doesn't have one for commercial documents (government
documents usually come with an RFP with detailed comments on how the
document should look) I have been trying for some time now to
convince the other writers that we would save a lot to time if we did
things right the first time.