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.
Most "highly trained professionals" are sadly disorganized. Left to their
own devices, the day after a meeting they will have no clear recollection
of what, if anything, was decided. Thus, it's generally a Good Thing for
them to receive a concise statement of what happened at the meeting,
provided that anyone is capable of putting one together.
I've known several directors and vice presidents who always knocked out
a set of meeting minutes immediately after each of their meetings, to
make sure everyone was knew what was going on, and what was expected of
them. While technical writing is a lofty calling, I don't think it's
THAT much loftier than being an executive.
I always take notes at meetings. Sometimes I publish them, either
by prearrangement, or because I'm trying to make a point. The only
reason I never volunteer to publish the minutes was that I am honing
my meeting-avoidance skills, and don't want to be obligated to attend
any meeting that isn't well worth my time.
-- Robert
--
Robert Plamondon, President/Managing Editor, High-Tech Technical Writing, Inc.
36475 Norton Creek Road * Blodgett * Oregon * 97326
robert -at- plamondon -dot- com * (541) 453-5841 * Fax: (541) 453-4139
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-