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.
>John Gough <gough -at- AUSTIN -dot- ASC -dot- SLB -dot- COM> said:
>>
>> On the less cynical (or shall we say experienced) side of the
>> question, a good performer in technical writing is one that
>> produces good quality manuals quickly with a minimum of handholding
>> from management, other tech writers, and other members of the
>> technical team.
>
>Double ditto.
>
>I would add that a top performer has self-confidence and a professional
>attitude as well--going the extra mile to produce a quality publication on
>time and within budget. If the extra mile means working 60+ hours, then the
>top performer GETS THE JOB DONE RIGHT without being a whining clock
>watcher.
>
>In my experience (12 years tech writing and 3 years tech pub dept.
>management), top performers rarely work overtime, because they tend to be
>confident, organized writers and meticulous planners, experienced with the
>many contingencies in document writing and production. A top performer can
>have a project finished in the same amount of time the plodding writer
>takes figuring out how to get started.
>
I can't believe the over reaction to one comment about being a "top
performer" in a job requirement. Let people be "top performers" if they
want to, but remember that in a big organization, a "top performer" can't
always be one if they are let down by bad management decisions and
unresolved conflict. If a manager is willing to back up his/her people when
the chips are down, that's when a top performance really means something.
Teamwork needs trust, not just head to head competition between workers.
Job posters post away! Don't get distracted by critical input. The best
forums are critical forums and shouldn't be discouraged.
John H McPhillips - Sydney
******************************************************************************
Pen Tayler
Computer Training Officer
University of Western Sydney - Hawkesbury
Bourke Street, Richmond, NSW, 2753
****************************************************************************
**
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
