Live data from Hacker News

How to take meeting notes

barehands.substack.com

111–120 of 130 posts

Re: How to take meeting notes

#112
post #26

Is substack the new medium? I saw a link to it for the first time a couple weeks back (at least the first time I registered the name) and now it seems to be everywhere. Yes I'm aware of the phenomenon that makes you notice things more after you notice them once. Not that.

Funny I asked the exact same thing yesterday :D

Re: How to take meeting notes

#113
I used to write notes for my own reference and people would come back to me asking for the notes. Few years back, I started sketching more than write full sentences or phrases. People like that more. I really like it too and I have been meaning to improve my sketching skills.

My long-time business partner, co-founder suggested me to read Dan Roam's book[1]. The books are awesome. I hope that I can, one day, draw/sketch half as good as my daughter.

1. https://www.danroam.com

Re: How to take meeting notes

#114
post #7

A long time ago, my boss at the time taught me a valuable lesson: every meeting needs an official record(/log/minutes/whatever) documenting all noteworthy decisions (D), tasks (T, with deadline and responsible person), and information communicated (I), with that record being sent to all participants by end-of-day. The reasoning being simple: If anything of consequence was discussed in the meeting, then the official r…

The semantic tagging is nice, I might start incorporating that into my notes.

On the overall topic of meeting notes, I picked this up as a new skill in the past year and it's been immensely valuable for myself and the people I meet with.

Specifically, I learned how to take realtime notes during the meeting while also listening and paying attention. It took practice but was achievable.

One key to success here is to explicitly ask for a helper to take notes while I speak. I've found this helps make the note taking seem like a whole team effort.

Colleagues have noticed and valued the notes and they do seem to lead to better meetings.

Re: How to take meeting notes

#115
post #95
post #28

Earlier quoted context omitted.

For the second and third paragraph: how do you validate that you really remember these things correctly and not just think you remembered them? For the script remembering: you cant do it. That is basically a profession called acting which takes a few years of training (biggest problem if you try is to do the gestures before the phrasing out, so usually what you do looks and feels unatural). Good advice I got was you…

Validation sometimes comes from external feedback, like "oh yeah, now I remember that but how did you remember that?". Other times it's just trusting I'm not making stuff up based on previous successful recollections. I wouldn't say I have an especially good memory tho. I guess maybe it's pretty good for days after something but most details trickle away after that unless I specifically focus on remembering them. I'm…

Just one more thing: for me the Loci method doesnt work, i somehow cannot remember places low grained (is there a coffee mug on the table or not and did I want to place some speech item at the mug). So for presentations i make sure the hints are all on the slides.

Re: How to take meeting notes

#116

> You can delight the people you meet with by sending a detailed note with everything you covered on a meeting (very few people do that) Be careful with your approach with disseminating meeting notes, despite what this article claims, they are not always well received. I've been promoted, in part, for providing this kind of structure to meetings but have also found myself embroiled in a political battles with gas-lig…

Can you elaborate on this with an instance? How did you deal with them?

Re: How to take meeting notes

#117

> You can delight the people you meet with by sending a detailed note with everything you covered on a meeting (very few people do that) Be careful with your approach with disseminating meeting notes, despite what this article claims, they are not always well received. I've been promoted, in part, for providing this kind of structure to meetings but have also found myself embroiled in a political battles with gas-lig…

Can you elaborate on this with an instance? How did you deal with them?

I left the company, both times. Once I established that they were gas-lighting everybody and nobody cared, time to move on from that toxicity.

Re: How to take meeting notes

#118
post #7

A long time ago, my boss at the time taught me a valuable lesson: every meeting needs an official record(/log/minutes/whatever) documenting all noteworthy decisions (D), tasks (T, with deadline and responsible person), and information communicated (I), with that record being sent to all participants by end-of-day. The reasoning being simple: If anything of consequence was discussed in the meeting, then the official r…

Some related advice on meetings, stolen from Getting Things Done: every point discussed in a meeting should result in one or more agreed and recorded next actions. This helps keep things clear, focused, and concrete.

Re: How to take meeting notes

#119
As a former civil servant I've been lumbered with the meeting secretary role on countless occasions. The following thoughts may-or-may-not help others.

1. Train your chairperson.

The meeting chair is usually an important person. Everyone will be there to influence that person's thoughts - as well as fight their own corner against professional and personal enemies. The secretary is usually someone a lot further down the pecking order. Which means training your chairperson is gonna be a fraught affair. However, if you can demonstrate to your chair that listening to your advice will lead to happier meetings then they may be happier to learn. I call this the "Dark Art of upwards management".

The keys to a successful meeting - they vary. But a pretty fundamental key is "what is this meeting about", alongside "what does the chair want to get out of this meeting". Work these out (by any means possible), then ask the chair if your assumptions are right before the meeting starts. Most chairpeople will (in my experience) indulge your questions in a patronising sort of way the first few times, especially if you can follow up on likely arguments that may block successful outcomes. After a while intelligent chairs will be asking you for a summary of the meeting before it starts. Chairs do not like to have their time wasted. Be the person who helps the chair save their time.

2. Take notes during the meeting.

Never rely on memory recall after the meeting! Your memory will lie to you, especially about the boring bits which turn out to be really important for some of the participants. And use oldskool pen and paper: typing is essentially one dimensional, whereas a pad of paper has three dimensions and pens can draw arrows, bubbles, and (during the boring bits) relevant doodles as well as record word/idea summaries. It should be enough to capture key phrases (which will trigger memories later) - if you need a full record of everything said during the meeting, use a voice recording device.

Also, advice for face-blind folks like me. Draw a map of where everybody is sitting at the very start of the meeting, and insist that everyone introduces themselves (for the record) before the bickering starts. Then you can give people numbers or pithy descriptions ("bluedress", "uglytache") to help capture who said what.

Nowadays online meetings can be recorded. Personally I think it makes the whole thing a lot less fun. Someone still has to summarise the meeting for the files, or action points, etc.

3. Write up a first draft of the meeting summary straight after the meeting.

Do not put this job off! Tackle it while the anger at being forced to do the work is still hot in your veins. It does not have to be perfect; it just needs to be in the required format. Fuller notes is best - it's always easier to cut words later than to add them. Pull action points from the notes into a separate document. The action points are the only thing anyone's interested in. But your chair will thank you later if you have a fuller record: being able to say during a subsequent meeting that something has already been decided - and being able to point to the record of that - will save your chairperson the pain of deja-vu ... and give them a reason to like you even more than they already did.

Final thoughts ... my ideal meeting lasts no more than ten minutes. If I need to meet someone (eg: client) on a regular basis I will do as much work beforehand as needed to make the meeting as speedy and pleasant for everyone attending. Know what every meeting is for; what I want to get out of the meeting. Know what others want to get out of the meeting before they know themselves. If you know someone will attend the meeting because they really like making everyone listen to their (never-ending!) voice ... lose their invite. If the matter of a meeting creeps way beyond its original scope, or you can see that you have nothing further to contribute, stand up and walk out.

Re: How to take meeting notes

#120
post #95

Earlier quoted context omitted.

Validation sometimes comes from external feedback, like "oh yeah, now I remember that but how did you remember that?". Other times it's just trusting I'm not making stuff up based on previous successful recollections. I wouldn't say I have an especially good memory tho. I guess maybe it's pretty good for days after something but most details trickle away after that unless I specifically focus on remembering them. I'm…

Just one more thing: for me the Loci method doesnt work, i somehow cannot remember places low grained (is there a coffee mug on the table or not and did I want to place some speech item at the mug). So for presentations i make sure the hints are all on the slides.

Yeah, I wonder if I'll have the same outcome.

As for slide hints, in this talk there's only about 5 minutes of slides and 40 minutes of live demos where I'm sharing my screen. Basically running and talking about a bunch of different things on the terminal while hopping between the terminal, code editor and browser. It would be very unnatural to try and read extensive notes while doing this. My plan was to put a single page of bullets off to the side on a 2nd monitor and glance at that, but I'm afraid it won't have enough detail.

Post reply on HN