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'm not completely convinced that these resources would be as thoroughly
useful as you might wish, even if you were to find them. In the dialogue
we've had on this list over the past few years, it doesn't seem like
there's a rigorous correlation between levels of job responsibility and
whatever officialdom calls us.
At our shop, for example, I'm a "product documentation specialist." It
wouldn't surprise me that somewhere else that's the admin who spends
most of life by the copy machine. In my case, it's technical editing and
technical writing and a modicum of project management (largely focused
around our operations manuals), and a whole panoply of odds and ends,
principally marketing in nature, such as preparing product newsletters
or PowerPoint presentations, or rendering the English from colleagues
across the pond into something most of us would recognize. Oh, yes, and
did I mention content and design responsibilities for the SharePoint
site? Then, of course, it's whatever else that needs doing and that the
boss advises me to do.
Jim
-----Original Message-----
From: techwr-l-bounces+jim -dot- pinkham=voith -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+jim -dot- pinkham=voith -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Nancy Allison
Sent: Friday, May 21, 2010 10:23 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: Levels of Job Responsibility
Oh, darn! Forgot to say -- I know we had this discussion recently.
What's different this time is, I'm asking for any resources,
publications, government standards you refer to, if you know of any.
In other words, I can go into my discussion saying
"This is generally called being a principal writer,"
or I can go in saying,
"This is generally called being a principal writer, and the Bureau of
Labor publication # whatever, or the Society for Technical Communication
publication titled whatever, explains it like this."
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as Jim -dot- Pinkham -at- voith -dot- com -dot-
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
