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.
Responding to Michael Collier <michacol -at- UPGRADE -dot- COM> on the subject of note
The project managers have found it to be a good thing that tech writers
sit in on software analysis and design sessions--and take notes.....
I started by audio taping and transcribing, and then video taping, in
order to accurately capture the white board stuff. The problem, of
course, with transcribing......
Is what they really -want- a transcription? I've been the "scribe" in
design sessions before, and produced a document from the session,
highlighting decisions made, current state of the data model, and unresolved
issues. I usually attach a "decision narrative" for each decision in a
separate section, explaining what alternatives the group considered, and the
issues raised, but it's more of a summary of who said what, (with a note
attached asking anyone who feels grossly misrepresented to contact me for a
revision; no one ever has) rather than an actual transcript. Given the
"ramble factor" in most meetings, this format is far more useful, because it
permits a reader to get straight to the heart of the matter, rather than
wade through pages of dialog that may or may not be relevant.
This high level of organization, summary, and deciding what is important and
what isn't needs to be done by somebody other than a transcriptionist, and
definitely makes use of good technical writing skills. It's also a very
powerful position. Because you control the "Unresolved Issues" section that
serves as the basis of the next meeting, you can make sure that the issues
you think are important (or were addressed superficially) get on the agenda
and get dealt with. You can also keep people from wiggling out of a problem
with some sort of vague platitude or pat answer by saying "Wait a minute,
what exactly did we decide there? I need it for the notes...." thereby
shouting "The Emperor is naked" without actually embarrassing anyone.
I take notes by hand during the session, often marking sections related to
the same topic as I go, and then sit down and pull the whole thing together
in a word processor in the space of a couple hours.
ENGSTROMDD -at- phibred -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-