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.
Subject:Re: Defining your role From:Janet Renze <jrenze -at- CGN -dot- ORG> Date:Tue, 3 Dec 1996 17:39:59 -0600
danger alert!! I agree with David Castro:
---->Also, if the company doesn't know why they hired you, how should you know
why they hired you?
now, this request could be because your manager thinks you are
best qualified to enlighted the team on your strengths and abilities,
but are the programmers being asked to do the same? how about
other team members??
there are lots of good sources on what tech writers can and/or should
do (have you skimmed the recent STC Intercom newsletters? i seem to
remember a 2-pager on this topic)--feel free to cite away to back up
your beliefs. but you must feel comfortable with how these explanations
and documents and presentation(s) will affect your work afterward.
in other words, will you be given lip service or taken at face value
and given the responsibilities you want?
at my company, I tried many, many ways to enlighten the various
software teams on the positive role of tech comm in a software
project. every programmer is clammoring for documentation and
structured processes, but the management is oblivious. needless to
say, the company is going nowhere fast, but I am ;)
best wishes and please keep the group posted on your progress!!
jrenze -at- cgn -dot- org