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.
I ran into a similar situation at my last company with a few overzealous product managers. I had tried sending out "reviewer checklists" with my docs at first, but the product managers basically ignored these and commented on everything, whether it was in their review scope or not. To deal with the problem, I ended up doing a variation on what John and Eric suggested: treated their "suggestions" like a "bug" and implemented a very simple "doc bug" tracking database in Access.
As part of my bug tracking process, I asked my reviewers to assign a "priority" to each
change:
P1 = Inaccurate content
P2 = Missing content
P3 = grammatical error/typo
P4 = "style" problem or other cosmetic issue
Having them assign the priority themselves forces them to think "How important is this change, really?" Almost immediately, the product managers re-focused their reviews on P1 and
P2 issues.
In your case, you might want to add something between P2 and P3 for content re-org. If you're getting a lot of requests for restructuring the docs, you might want to talk to management about planning some time into your schedule for a large scale doc re-org. If you don't have the resources to do this, then you need to diplomatically communicate that to QA. If you can show management that you've consistently gotten a lot of re-org oriented requests, they'll be more likely to make that a priority, especially if any of these requests come from customers.
My other suggestion is to document your style decisions in a style guide, if you haven't already done so. Whenever someone questions my use of "email vs. e-mail," I can back up my decisions with a style guide.
HTH,
Michelle
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 and receive a $100 mail-in rebate, plus FREE
RoboScreenCapture, WebHelp Merge Module and iMarkupSoftware, for a total
giveaway value of $473! Order here: http://www.ehelp.com/techwr-l
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
