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: Purpose Statement for Style Guide From:Stephen -dot- MacDonald -at- Aspect -dot- com To:TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM Date:Fri, 7 Jul 2000 08:01:54 -0400
> Our new management thinks that our Style Guide is a luxury and a waste of
> time. Can you provide me with some well-thought-out arguments as to why a
> tech. pubs. team would "need" to have one?
Are you saying they think the current one is a problem or they are opposed
to a style guide altogether? If it's the former, they might have a point.
If it's the latter...
IMO, the consistency and clarity resulting from a good style guide produce
lower documentation maintenance costs and fewer service calls. Those things
alone should be enough to justify it, but most places don't have the data to
I would certainly enlist the help of your service organization. Most folks
in that world have found over time that a good doc set helps them