I've been thinking a lot about meetings recently. So many of us are stuck with unproductive meetings day in and day out. So I wrote a post about it on Medium today and shared my best tips on how to make meetings productive.
You can find the post here!
- A meeting isn't always needed. Asynchronous communication can replace a lot of meetings.
- Meetings should have a deadman switch and should be short by default.
- Always have a solid agenda! Don't aimlessly conduct meetings.
- Fewer people = better meetings!
- Get team members to engage more. Make sure quieter members also contribute to discussions.
- Always have someone take meeting notes and share them afterward. People should know what actionable items have been decided!
Got any hacks of your own?
I'm curious and always looking to make communication with my team more productive! Share your best advice with me. You can do it in the comments or on this Twitter thread.
Utkarsh Talwar@youuteeeWe radically redefined how we do meetings at @SkynoxTech and wrote about it.
The One and Only Guide to Make Meetings Un-suck by @Sarthology link.medium.com/4VIZhtZna8
A thread on how we made our meetings more productive...12:46 PM - 16 Jul 2020
Here's a cheatsheet for better meetings.
Anyway, share your thoughts! Cheers!
Top comments (7)
Early on at Google, there was an engineering decision to use “Python where we can, C++ where we must.”
I would transfer the same principle to meetings "Slack where we can, on-site where we must". Goes well with your #1.
Although this idea isn't productive, it can help with team engagement. One of my previous TL's got us to do this, so we could get to know each other better.
Basically you get one member of the team to make a presentation on something (Where they are from, a hobby, what they work on, anything really). We sometimes even added quizzes - although that was to keep us awake during night shift.
I find this to be a good one - only use meeting time for decision-making. Information-gathering should always be done before the meeting.
Hi @sarthology , point 6 is perhaps the most important part of the process, and I find it‘s the one most often neglected.
I was talking to two friends this morning about a workflow I have for capturing the meeting as a narrative, which is:
So, the “link to the note for the agenda, and add a description to the link that explains some essential context” is specific to the product I've built, the Under Cloud, but a similar if less useful workflow could be made from notes with the appropriate titles, or folder structure.
I always feel something like "Pun of the day" before every meeting would make the teammates more cheerful and engaged too.
A friend of mine developed a project called tooqan
I used it for some time and it provided some good vision but the problem is that you need everyone to use to get more value out of it
This has some great points, thank you!