RE: Tech Writers taking minutes

Subject: RE: Tech Writers taking minutes
From: "Jonathan West" <jwest -at- mvps -dot- org>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 1 Jul 2002 19:26:45 +0100


When I'm secretary to a standards committee, I have to take the minutes.
Every chairman has his own preferences regarding the level of detail that
should be in the minutes, but generally all require the following:

- Date, time & place of the meeting
- A list of those attending
- A list of all documents tabled, with a statement regarding their disposal
(e.g. agreed, revised, rejected, withdrawn)
- A record of all decisions taken
- A record of any votes
- Where appropriate, a record of the reasons behind the decision (important
if the decision went one way or another on the basis of facts that are not
yet 100% certain and might need to be reviewed)
- A record of any major dissenting opinions
- A record of all actions assigned
- Anything else considered particularly important by the chairman or another
committee member, if a request is made during the meeting for it to be
minuted.

The minutes generally do not have to be a verbatim record of everything
said, they are more of a summary. More than once, when the discussion
started going round in circles, I have included in the minutes "A long and
involved technical discussion followed, from which no firm conclusions
emerged." I've never had any complaint about that phrase, partly because it
was an accurate summary of the discussion, and partly because by the time
the minutes came to be read and approved, nobody could remember what they
had said in the first place!

On several occasions, when a contentious issue seems to be coming to
agreement, I have read out the form of words that I plan to put in the
minutes, to ensure that everyone can agree to it. I don't want the question
getting re-opened next meeting in the guise of a dispute over the minutes.

I regard the taking of effective minutes to be a significant TW skill. You
have to summarize effectively, take notes quickly and under pressure, and
distribute a document that will be reviewed by the participants who are all
by definition experts on the subject of the document - they were there at
the meeting! To do that, you really need either to have quite a bit of
knowledge of the subject under discussion, or be able to pick up the
essential points very quickly.


Regards
Jonathan West



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Save $600: Create great-looking Help files and software demos with
RoboHelp Deluxe. Get RoboHelp and RoboDemo - our new demo software - for one
low price. OR Save $100 on RoboHelp Office in June with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l

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.


References:
Re: Tech Writers taking minutes: From: Meg Halter

Previous by Author: Standard for Documenting XML - especially Repetition Rules?
Next by Author: RE: version name
Previous by Thread: Re: Tech Writers taking minutes
Next by Thread: RE: [Fwd: Re: Thanks re Quark v. FrameMaker -- and one more question ...]


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads