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.
We've had a lot of style guide questions lately,
--- Rebecca <rebeccam -at- envworld -dot- com> wrote:
> 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?
Well, the most obvious reason is consistency. With
everyone in the company reading (literally) from the
same page, everything should come out "looking" pretty
much the same. This is especially important if
different people work on different parts of the same
manual. Without a style guide, it's entirely possible
that chapter 1 could talk about "E-mail" while chapter
6 discusses "email."
While many of the elements of "style" are understated
and probably won't register on the average jo/sephine,
the user will generally have a feeling something is
wrong if things change subtly from one point to the
Customers also will appreciate everything having the
same "feel" that results from consistent use of
headers, footers, bullets, et cetera. After reviewing
just one of your books, they learn to trust you
because they know they won't have to relearn the
interface to get to the material.
It also makes the editor's job easier, looks
professional, and is an industry standard.
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/