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: being seen From:SIANNON -at- VISUS -dot- JNJ -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 7 Dec 2001 13:42:42
>>He asked, "do all technical writers go out of their way to learn as much
>>about the technology as you do?"
>I was recently in a developer's meeting, and started answering questions
>that the lead developer was asking. He said, "How do you know this?" I
>answered, "It was in the document from the project manager last week."
He
>quickly replied, "I've got to quit deleting his email before I read it!"
I became amused when I realized that for our project, I have become the SME
for the system as a whole; the project manager came to me for the "frank,
analytical tour" when he first got transferred in (we scared off two other
managers before we got him). Because the system is so complex and heavily
interfaced, and the development team so small, the developers each have
their hands full with multiple complex components they are personally
nurturing. They can't always see the downstream interdependencies when one
aspect of the system is changed, and developer 1 and developer 2 are both
working on different projects within the über-project at the same time, so
they sometimes come to me to find out what each other is doing (there's
that gatekeeper role again).
I've also noticed, in hindsight, that my role as the detail-gestapo has
been utilized by my team to nudge other teams' developers (those on
interfacing systems) into addressing sticky topics and design issues that
try to break our system, without them taking offense or feeling
"threatened". Since I am not a developer, I am not seen as someone who'd
be demanding changes to their "baby" (which is the subconscious fear
usually underlying inter-system development feuds), and so I have the same
ability as the child who revealed the emperor's new clothes to ask pointed
questions that might normally trigger a defensive response (and here we
return to Geoff's point on constructively "playing dumb").
Granted, I *have* been actively _forbidden_ to ask *any* questions after
4:45pm on a Friday, following the last three times I brought up nasty,
snarly, conflict-ridden, potentially ugly issues at that time. (*slightly
embarrassed shrug* ...not _entirely_ my fault on the timing...it was the
only time I happened to find all my SMEs in their cubes at once...)
Shauna
----------------------------
...and to all a Cool Yule...
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.