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.
On Wed, May 13, 2009 at 12:08 PM, That Darned Writer
<j_grey -at- writeangles -dot- com> wrote:
> Have you provided your team with guidelines on creating documentation bugs?
That's part of what I'm trying to write today.
I'm somewhat new at this job (been here about 6 months) and I've
inherited some less than helpful issues, some of which have been
floating around in the system for so long that the people who entered
them are no longer with the company. So far my team has been
fabulously helpful. *loves my team* But while it seems like
development and QA have a good handle on how to use issue tracking,
it's the folks in the field (sales engineers, support) who have the
most valuable input (actual *customer* contact) and the most trouble
writing good issues. I'm trying to figure out how best to coach them
towards providing me with useful input. Especially since we just
hired a few new sales folk, and I anticipate feedback as they read
through the docs to get up to speed on the product.
It's not that I'm new to using issue tracking (been using bug tracking
systems for 9 years now). This is just the first time that I've been
in a position (lone writer) to tell the rest of the company how I'd
like them to use it for doc issues.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
