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.
Anthony Markatos wrote:
> Question for all listserv members:
> I am looking at a tech comm job listing that states that the future
> employee must be a "team player". What is meant by this? Specifics
> Digression: I have always been a firm believer in the old business
> saying, "Only two percent(2%) of all people [employees] are problem
> solvers, the rest are just along for the ride." My belief in such
> makes it very hard for me to envision a true "team" environment -
> where everyone assumes an equal portion of the more difficult tasks.
My belief is that they are looking for someone with the following
* Someone who doesn't have to be supervised all the time (e.g.
no babysitting required)
* Someone who can contribute ideas without getting over protective
of their own ideas
* Someone who is productive - e.g. can work lots of extra hours
* Someone who won't rock the boat (no compaining about processes
or policies please)
* Someone not afraid to try new things and jump in and do tasks
that are not necessarily in their job description
I think that about does it.
Problem is, if you add a team player to a team that doesn't really act
as a team, then you end up with one person trying to make up for the
deficiencies of the team. This person gets "used up" and is usually
hated by the team for "showing them up".
Just my .02. :D
write-it -at- home -dot- com