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.
This is an interesting discussion. I would appear that views on
note-taking are as varied as everything else in the communication
I am a Senior Technical Writer (program coordinator) for the Operating
Agent (OA) of the Energy Technology Data Exchange, a consortium of 19
countries who compile the Energy Database. Annually, the Executive
Committee, one member from each country, holds a policy and planning
meeting. Part of the responsibility of the OA is taking notes and
producing minutes for the meeting.
At our just concluded meeting in Sweden, new staff members who thought
note-taking would be a breeze were surprised at the difficulty level.
The Minutes we produce are usually 35 to 40 pages in final form. I
don't view this as a secretarial task. It actually requires high
level communication skills in effective listening, mental flexibility,
and being able to translate the information into a form easily
understood by an international audience.
Now, if anyone in the East Tennessee area is familiar with any
training in note-taking that our staff can attend, please let me know.
Program Coordinator, Operating Agent Staff
Energy Technology Data Exchange
(susanne -dot- dupes -at- ccmail -dot- osti -dot- gov)
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-