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.
> The question is -- why does this happen? One theory I've heard is that
> calling a meeting forces people to pay attention and respond, whereas
> just distributing copies of the document lets them set it aside and
> forget it.
The message I would be getting is that the SMEs you're describing don't
feel any obligation to tech writers. I assume they would respond to a
request from someone who they acknowledge as a 'driver' of their work,
like if a project stakeholder asked them to review it.
I'm not sure why a meeting would be any different, maybe they expect to
have stakeholders there to give their feedback as well.
FWIW, I've had 10-20 reviewers grab review copies off the LAN the day I
ask them to, take those copies home that night, read/mark them up, come
in the next day and type their comments into an email, stick their
markups in interoffice envelopes, and send them all to me before
lunchtime. When our process finally requires a meeting to smooth out any
remaining wrinkles, we do it in a conference call.
I can't say that they do this in response to my review cycle leadership
or inspirational drive to get things done. Actually, the reason they
participate so readily is that my reviewers represent two groups who
vigorously compete with each other, as a matter of survival. Group 1 is
Development--they create software that I document. Group 2 is Support.
Between them, there are two drastically different sets of information
requirements. They can't agree on what needs needs to be in the
documentation! They never miss a chance to rejoin the fray (review) and
continue their criticism of the way the other wants to do things.
Telecom joy, yep.
Ned Bedinger
doc -at- edwordsmith -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
