Compare and Contrast different Doc Groups

All

I’ve been given a challenge, and would greatly appreciate your advice, assistance, suggestions, and/or commiseration.

During a series of conversations with my boss (a remarkably rational, non-tech writer VP), he asked a number of questions, all of which boil down to the following.

“What’s the measure of a world-class Tech Pubs department?”

He went on to say that he felt we were doing a very credible job, especially in light of the expanding requirements/static resources with which we live, but impressions don’t count for much (especially in an engineering environment).

We work in a software company, as part of the engineering team. Along with Tech Pub and other things, he is also responsible for the QA function. He rattled off some QA-type statistics (code coverage, testing automation, trends in bugs found/fixed) as good examples of how a QA team in Company X might be compared to a QA team in Company Y.

I did not put the dreaded term “metrics” in the subject line – I’m not looking for way to track our progress against internal goals, nor our improvement (or otherwise) compared to our past performance. What I would like to be able to do is compare our performance against that of another, mythical, world-class software doc team.

I’m sure I’m not the first person that’s been so tasked, and wiggled out of tracking keystrokes per minute, typos per furlong, or doc bugs per release.

So – anyone have any ideas?

Thanks a million

John Rosberg

Measure of a World Class Tech Pubs department

My suggestion would be what is the effect of the documentation produced on the company, the competition, and the market.

A classic case would be the use of extensive documentation in the networking world from companies like Novell and Cisco, which is reused to produce comprehensive training materials. The accreditation program for technicians becomes an industry standard so customers buying their products hire pre-trained staff. Pre-trained staff make their products look good and reduce their support and increase customer satisfaction. So great documentation can be a cornerstone of market success.

I've also come across the effect of great support documentation in the professional mobile radio world from Motorola, which is used to train and assess the dealers. Being a market leader Motorola will only accredit qualified dealers. Customers get good service from accredited dealers so return to buy more products from them.

The difficult part is investing time and money to do this if your firm isn't a leader and doesn't have funding for it.

Define the Reasons for Pub Dept first

I am researching a completely different idea when I ran across you question. An article I just read might get your neurons firing. Found it on this website which is great resource:
http://tc.eserver.org/

This is the link to the article:

http://www.bizmanualz.com/information/2007/11/12/why-do-you-need-to-write-procedures.html

Why do we write procedures? is the name of the article. Not sure of the author. Without knowing your circumstance, I thought that the 4 reasons why we have them to begin with was powerful.
1. Compliance
2. Operational Needs
3. Manage Risks
4. Continuous Improvement

I hope this helps. I might have not understood your intent.

Maybe you should start with the elements - why do we have pub in the first place, and then brainstorm on ways to measure the why's? If you come up with any - please share with me - jenifa_us@yahoo.com
I might be able to use a few in my proposal to my manager.