Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A Is it overkill to follow style-guides for technical writing?

I think you are confusing a style guide with a manual of style. The Chicago Manual of Style will help, but is more of a reference book of best practices, rather than a set of policies and procedur...

posted 12y ago by Keter‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:16:53Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/6464
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by user avatar Keter‭ · 2019-12-08T02:16:53Z (almost 5 years ago)
I think you are confusing a style guide with a manual of style. The Chicago Manual of Style will help, but is more of a reference book of best practices, rather than a set of policies and procedures to guide document development processes for your particular business use.

It seems a **style guide** is what you are hoping to create and implement company-wide, something that standardizes things like sections in a report or user guide, typefaces used, logo and trademark usage, software to be used to create documentation, and template design standards. Do a web search for "technical style guide" and you will find examples.

Creating the style guide will not be your biggest task, however. Getting management to implement it as a requirement will be the greatest challenge, and if you don't have that, you will waste your work and annoy yourself and your coworkers. The key to getting management buy-in is to get them to understand that consistent documentation is part of consistent branding and messaging - your documentation is a part of the marketing effort.

Once you have management behind your effort, bring in your colleagues and work as a team to create a style guide tailored to your company culture and work flows. Include key members of engineering, customer service, and marketing teams in this effort as well, so that you get engineering on the same page with scheduling documentation lead times, learn about what in the documentation is confusing or frustrating customers from the people who have to deal with them regularly, and ensure that the terms you are using in the documentation are the same ones the marketing department uses, also that you are targeting the right audience by understanding the actual customer base and their real world use of the products.

Some style guides also cover document distribution processes and retention policies. These can be also be dealt with in separate procedures, as best fit your business use.

#1: Imported from external source by user avatar System‭ · 2012-10-10T21:26:10Z (about 12 years ago)
Original score: 7