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 am interested to find out various ways a tech writer's workload
> >is measured and what metrics are used to allocate their resources.
Diane wrote:
> Metrics: Is a document needed? Was it completed on time? Are there more
> documents needed? Then get back to work...
I'm pretty much in line with Diane. The metrics I've seen have been fairly
binary:
Is the work getting done?
If yes, good. Get back to work.
If no, first push current staff even harder, then try pushing back
deadlines, and finally - as a last resort - start thinking about hiring
another writer.
Not advocating this, just reporting what I've seen.
Keith Cronin
is a lifeline the opposite of a deadline?
---
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.
