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.
Just wanted to jump in on the topic of measuring writers' productivity. The
ultimate measurement of a writer's success (and programmers to, I guess) is how
wel it works for customers--that is sales, upgrades and/or retention (how many
are still using the product 6 months after purchasing it) and number of support
calls. I have heard that Microsoft charges the TW department for each call
Support takes. I don't know how well this works. On the other hand, my company
charges for support and it's a major source of revenue for our company, so
perhaps Support should pay us for each call they take. ;.)
If anyone has any other ideas about measuring productivity, I'd like to hear
them.
Mindy
mkale @ gps.com
"This writing business, pencils and whatnot--
overrated, if you ask me.
Silly stuff, nothing in it.
