Re: Measuring TW Performance (was Documentation Estimates)

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

Measuring the performance of an individual writer is a different
kettle of fish compared to the top-level discussion that has been
going on about demonstrating the value of having the writer
(perhaps we have all been going off on a tangent?).  For one
thing, the writer's objectives are predefined and the "value to
organization" of the writer's position is not under discussion
while the ability of the writer to satisfy objectives is.

I establish a default set of objectives for writers to work toward
on each project, namely:

1.  Establish a document plan and schedule that define the
    content and completion required by the product manager
    and get them signed off by that manager.

2.  While rearching and writing the document, provide regular
    status updates, and any time circumstances require it, update
    the plan and schedule to reflect actual conditions and get the
    updates signed off.

3.  Complete the document according to the plan and schedule.

Then I track how well the writer meets these goals, the number
of document projects successfully completed and their level
of complexity to arrive at a rating for the individual.

Gene Kim-Eng



----- Original Message ----- 
From: <stevefjong -at- comcast -dot- net>