Live data from Hacker News

Ask HN: How do you run better meetings?

news.ycombinator.com

41–50 of 74 posts

Re: Ask HN: How do you run better meetings?

#41
If you have people in your meeting who do not meaningfully contribute or learn something valuable that could not have been learned from a shared document, you have wasted their time.

So, ask:

Did everyone in the meeting contribute or learn something they couldn't learn by reading?

If the answer is 'no', there were too many people in the meeting or it should not have happened at all.

I've been in so many hour long meetings with 6-8 developers plus project manager, supervisor, and maybe one related person and at least 6 of the devs say nothing. That's 6 hours of dev time lit on fire each time.

The best meetings tend to be ones where stakeholders can share information and come to a decision that pushes a project forward or where there is valuable training or a useful presentation.

Also, if your meeting ever includes the phrase "well, we've got 20 minutes left so let's take some time to discuss ", it was a terrible horrible no good bad meeting.

Re: Ask HN: How do you run better meetings?

#42
Correction: the pandemic exposed communication and workflow issues that you are trying to solve by scheduling tribal knowledge.

1. Are you having a meeting because somebody is looking for information?

Do not have a meeting. Write shit down. There is e-mail and Slack and MS Teams and Google Docs and Sharepoint and Confluence and a billion ways to write shit down that does not require a meeting. Always make an attempt to gather information before you have a meeting, because you might get to the meeting and find out you have go to find out information somewhere else anyway.

Document where people should write shit down and where to go find information. Force people to write shit down by making it a requirement to do something. Make the process of finding or writing shit painless, easy, useful, and transparent (no hidden folders, secret channels, locked down access, obscure systems, etc). This is more difficult than it sounds, but the benefits are huge.

2. Are you having a meeting to decide something?

Before the meeting, if you think you're going to run over the meeting time, make the meeting longer, or realize that your meeting's scope is too big, or that you haven't gathered the information needed to make the decision. Also write down what you're going to talk about / decide, who is required to attend (& why), what/where the supporting information is, what the potential decision choices are. During the meeting, write down feedback. At the end of the meeting, write up what was decided. End the meeting as soon as you achieve the meeting's objective. Reply to all the attendees with the meeting notes (or a link to the meeting notes). Write all this down on a page titled "Meeting Checklist".

Tell your coworkers to include the Meeting Checklist in the meeting request. Make an e-mail filter to send all meeting requests without the checklist to the trash. Ask your boss to back you up on this.

People will bitch and complain about this because they'd rather interrupt 20 people for an hour than do a bunch of annoying preparation. Tell them that they have 2 alternatives: 1) don't have a meeting and figure it out offline, or 2) if it's an emergency, they can schedule a meeting without the checklist, if they include "EMERGENCY" in the subject of the meeting.

3. Do people just need an outlet for social interaction?

"social hours" / "office hours" can be a good way for people to talk without a meeting. Schedule these at either the beginning or end of the day (or both). This way people don't have to chit-chat in meetings because they know they can do it another time.

4. Do you still have too many meetings?

Schedule meeting-free days. I suggest two per week, because people break these and schedule meetings anyway. Block off your calendar all day.

Fight zoom fatigue. Require all meetings end 5 minutes early for every 30 minutes. So, 25 minutes for a 30 min meeting, 50 minutes for an hour meeting. Start the clock at the beginning of the meeting, don't wait 5 minutes for people to join. (Mention this in the meeting invite)

Have your whole team agree to block off their lunch time. Meeting flex time is nice, but not when it prevents people from eating and resting. This can be on an individual basis or group basis, but everybody's calendar should have a 1 hour block sometime during the day.

Have your team decide on a maximum number of meeting hours per day. Once your calendar has hit the max, start rejecting meetings, or cancel less important meetings. If your whole day is meetings, you better be a manager with 30 direct reports or something.

Re: Ask HN: How do you run better meetings?

#43

I definitely feel the growth of meetings has been a bit insane since WFH started. Here's what I do: 1) separate technical meetings from process/operations meetings and clearly spell out the difference 2) Write in a narrative format what it is you're trying to accomplish and distribute this ahead of time. Doesn't have to be the often lauded "Amazon 6-pager", but if you can't explain what it is you're trying to accompl…

1) is a great advise that I think I can make use of, same for 2). For 5) I feel it is hard. Often there are expectations that you join meetings just in case a higher-up manager needs a piece of information or I am afraid to loose out on critical information. Do you, in your organization, have an active meeting culture with feedback for meetings? It feels to me that in my organization too often when a conflict, next s…

The general theme of my advice is that communicating in a clear, precise, and reproducible manner (reproducible meaning where someone can back-brief what you just said and get it right) is one of the most important things to learn/know how to do if you work in tech - or any industry, really, but Tech in particular. I didn't come from a technical background, unless you count math, and that has been the go-to advice I give people because it does two things: 1) it builds up your own confidence in what you're saying as well as others' confidence in you, and 2) you will actually end up learning more about the subject as you strive to be evermore accurate in what you're saying.

If English is not your first language, then this advice is doubly important because it will help you improve.

Edit: sorry, I didn't actually answer your question.

>Do you, in your organization, have an active meeting culture with feedback for meetings?

Yes, but I'm a little more senior now and I think focusing on the feedback mechanism itself is missing the forest for the trees. Communication is always King, wherever you go. It seems like, from your description of the situation, you have a great opportunity to improve the communication within your organization overall, if people are still reverting to "just schedule a meeting".

Re: Ask HN: How do you run better meetings?

#44

Run less or no meetings. If you have to run meetings, consider the option to temporarily institute an approval process by senior management whereby the thesis for any meeting (proposed agenda, attendees, etc.) is first proposed in private. Then senior management has the opportunity to ask questions and give feedback. This alone will force those convening to think twice. If necessary, quantify the cost of the meeting…

I like the general idea of having less meetings. I try to cut time down for meetings I am responsible for. However, there are ~10 hours of meetings each week that I need to join either because: 1. There is an expectation by management that I should be there in case they have a question (often they do not). 2. I join to make sure I do not miss the critical pieces of information that I need. That is often five minutes…

deal with inefficient meeting culture

Use an auto-transcription service. If presence is required, try to get a real time system going and flag keywords. That way you can alternate task your way to the important bits without dedicated mental bandwidth. The nice thing about this is you just need the system audio feed, muted, as the input which by definition works with all conferencing platforms.

Re: Ask HN: How do you run better meetings?

#45
* Prepare a thorough agenda in a shared/cloud editor before scheduling the meeting

* Send out the meeting invite 3-7 days ahead of time, including full reasoning for the meeting, and a link to the agenda in a shared editor

* Only hold the meeting if you weren't able to work it out async in the time leading up to the scheduled meeting

Sometimes avoiding a meeting is incentive enough to coordinate the work async ahead of time. But if the meeting still happens, you’ll have a well prepared thought out agenda, and all participants will have had time to prepare as well. So your meeting becomes a matter of working through any remaining unresolved topics/details from the shared agenda.

Re: Ask HN: How do you run better meetings?

#46

Run less or no meetings. If you have to run meetings, consider the option to temporarily institute an approval process by senior management whereby the thesis for any meeting (proposed agenda, attendees, etc.) is first proposed in private. Then senior management has the opportunity to ask questions and give feedback. This alone will force those convening to think twice. If necessary, quantify the cost of the meeting…

This is nuts. Having management approve meetings? How about "learn to communicate: decline unnecessary meetings and figure out how to reconcile disagreements".

Isn't it the same thing? The approvals are to verify that the meeting is necessary.

I'd assume that other communication is done semi-formally, e.g. a slack group or call. Updates are asynchronous, someone does an update and the the whole group knows. Anything where you have to block out 2 hours of everyone's time should be approved.

Re: Ask HN: How do you run better meetings?

#47
Keep meetings small and quick. Only include the leads if possible. Send an agenda a few hours before a meeting helps too. If something important blocks a meeting, cancel and schedule a new one instead of dragging it into a multi hour nightmare. Try to reach actionable points that can be directly copied as a JIRA ticlet. Send a post meeting summary as soon as possible with these actionable points. And don't forget to cc relevant people.

Re: Ask HN: How do you run better meetings?

#48

Run less or no meetings. If you have to run meetings, consider the option to temporarily institute an approval process by senior management whereby the thesis for any meeting (proposed agenda, attendees, etc.) is first proposed in private. Then senior management has the opportunity to ask questions and give feedback. This alone will force those convening to think twice. If necessary, quantify the cost of the meeting…

I like the general idea of having less meetings. I try to cut time down for meetings I am responsible for. However, there are ~10 hours of meetings each week that I need to join either because: 1. There is an expectation by management that I should be there in case they have a question (often they do not). 2. I join to make sure I do not miss the critical pieces of information that I need. That is often five minutes…

> However, there are ~10 hours of meetings each week that I need to join either because: 1. There is an expectation by management that I should be there in case they have a question (often they do not).

We dealt with this in the zoom era by having some people present but not paying attention. They would join the meeting but then turn the sound off and do their own thing. If we needed their input on something, then we would ping them on slack and they would come in and provide their input. In GCal, marking people as "optionally" attending meant that they were free to not pay attention.

> 2. I join to make sure I do not miss the critical pieces of information that I need. That is often five minutes out of sixty minutes.

We made a rule that every meeting had to have an agenda list posted to slack before the meeting and a summary posted to slack after the meeting. The meeting convener was responsible for making sure this happened but could delegate this responsibility to someone else. Often, this was a good onboarding task for new members joining the team.

Re: Ask HN: How do you run better meetings?

#49
What worked the best in my experience is to have an agenda. Having an agenda with time-slots for each bullet point makes it easier for everyone to get their voices heard instead of having a lone ranger talking nonstop about their favorite subject for 1h non-stop.

In short: - Have an agenda with time-slots - The meeting organizer is the one in charge of sticking the meeting to the agenda. When someone goes off-topic steer the conversation back to the topic. Be strict and ruthless about this (In a nice way ofc :) ) - Avoid the small-talk that can be done before or after the meeting, not everyone in a meeting wants to know about how many goals you're kid score this last Saturday. - Take notes for each bullet-point in the agenda, actions points could be make a jira-task for this, contact John Doe about budget changes etc. - After the meeting share the meeting notes with everyone, tag people in the notes so they get re-informed of their tasks after the meeting.

That usually does the trick for me, this template can ofc not be applied to all kinds of meetings, read-the-room.

Re: Ask HN: How do you run better meetings?

#50

Earlier quoted context omitted.

I like the general idea of having less meetings. I try to cut time down for meetings I am responsible for. However, there are ~10 hours of meetings each week that I need to join either because: 1. There is an expectation by management that I should be there in case they have a question (often they do not). 2. I join to make sure I do not miss the critical pieces of information that I need. That is often five minutes…

deal with inefficient meeting culture Use an auto-transcription service. If presence is required, try to get a real time system going and flag keywords. That way you can alternate task your way to the important bits without dedicated mental bandwidth. The nice thing about this is you just need the system audio feed, muted, as the input which by definition works with all conferencing platforms.

can you provide some specific recommendations here?
Post reply on HN