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.
Human as Resource ( was Re: FW: more #$ -at- %#^&$# secretary stuff...)
Subject:Human as Resource ( was Re: FW: more #$ -at- %#^&$# secretary stuff...) From:JIMCHEVAL <JIMCHEVAL -at- AOL -dot- COM> Date:Tue, 12 May 1998 18:15:51 EDT
In a message dated 98-05-12 17:59:52 EDT, traceym -at- APPLIEDMAPPING -dot- COM writes:
<< My boss stopped me and said it =
wasn't a good use of my resources, get the secretary to do it. >>
And this DOESN'T just happen with 'secretarial' tasks.
A lot of us in the technical world are, I think, naturally helpful. And have
to learn to be less so.
My first week as a programmer, one of the salesmen came through, introduced
himself, was real friendly. A short while later, he asked if I couldn't do
some small thing for him (long forgotten).
This gave rise to one of my first corporate tutorials.
My boss immediately told me that:
A. The salesman should have gone through him before using one of his
resources
B. If I started doing little things to be helpful, they would suddenly, as if
by magic, become my responsibility.
It's human nature to help, and it took me a while to absorb these lessons.
But they're pretty fundamental in an environment where employees are also
referred to as 'resources' and departments charge back services amongst
themselves.