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: Challenging and oppressive SME situation From:Ann Mackenzie <TekDocWis -at- AOL -dot- COM> Date:Fri, 21 Aug 1998 10:02:58 EDT
In a message dated 98-08-20 20:27:25 EDT, Marilyn Baldwin wrote:
> Before you ever met with this SME, it would probably have
> been a good idea to have a brief meeting with your manager to see what HE
> knew about her, either by direct experience or word around the place. This
> isn't because you'd have suspected anything bad about her - but just
> because it's good for everyone if you know things like: what's her current
> workload, and where might my project fit into it, does she like to keep
> right on top of things or kind of hustle near the end of the timeframe for
> deliverables due, what exactly is required of her and what of me, etc.
What a good idea this is! It never occurred to me before, but *everyone*
likes
to be asked for advice, so a meeting like this with your boss provides an
opportunity for:
- you to show yourself as a competent, organized professional
- the manager to give "easy" advice (that is, "soft" issues) and feel like a
competent boss
- both of you to have a nonthreatening, easy-going meeting, so your manager
sees you in
a positive business situation
Writing status reports, either weekly or bimonthly, also is a good idea. They
make you
evaluate and list what you have accomplished and show that you are planning.
Mine
contain 3 major headings:
o Current Progress List accomplishments (include everything you spend time
on, such as
meetings, interviews, reviews, drafts, requests) for the past week or two.
o Expected Progress Your plan for your work during the next week or two
o Comments (or, Concerns) Its alright to write "nothing" most times, but
when there is a problem,
or something that needs addressing, here is the place to write about it
before becomes major.
Sometimes, potential problems can be stopped by an early warning, or
concern, in writing.
I have never had a manager who didn't appreciate concise status reports in
writing.
Thoughts to add to this very interesting, and informative thread. Thank you
to everyone else who
is participating, I'm learning a lot!
Cheers Annie
==========================
Ann Mackenzie: TekDocWis -at- aol -dot- com
TekDoc - Technical Documentation, Inc. in Milwaukee, WI, USA
Specializing in software, engineering, and policies & procedures.