Good article! I think another way a team meeting could be useful to the team could also offer the team an opportunity to share an observation/feedback/pain point about a process and invite discussion in a way that saves an additional meeting.
Also, from my experience, when my team introduced Friday team meeting, I introduced an idea to have a Kudos aspect. People like to feel appreciated for what they do, so team meetings could be a way to verbally recognize someone who did a good deed for the team or upleveled others around them
I think there are several ways you can make Kudos feel less awkward.
1. Demonstrate example of giving kudos/appreciation to people who upleveled the team or did a good deed youd like to commend. Kudos for the behavior is important (but definitely ask your report if theyre cool with you sharing the kudos publicly is important to not burn bridges). When sharing kudos, I find its really helpful to highlight the IMPACT of the good deed or decision rather than just saying "keep it up Bob".
2. Leveraging your company's employee recognition portal and encouraging your team to do the same goes a long way especially if some feel more comfortable sharing written appreciation
3. Feel free to ask for more context on a given kudos so that when you need to write feedback about the report, you are kept in the loop and tell their story as it happened
Running weekly meetings is an interesting job. I say interesting because it can feel demotivating if it feels like a waste of time but if done right it can do wonders.
I have had weekly meetings where we brainstorm topics, discuss incidents, mundane stuff, etc.
I found the incidents and brainstorming ones can unblock folks and raise awareness. It is work to build a team culture that values it. You have game it a bit for folks to be excited. I have stories on this one for another time.
Hi Anton, thanks for being vulnerable enough to share you were afraid. I was afraid too. It's been a year and a half, and sometimes I think about cancelling because I'm not sure what update to share with my team.
One thing that's helped is having a shared document with the agenda. I can update it throughout the week so I'm not panicking last min. Also, other team members can add stuff to so it's not all on me.
* Announcements/Discussion topics: These are things I want to share or discuss with my team. It’s also open to everyone, so if they have an idea they can add it too. If I don’t have topics, I’ll share that with the team and just go around the room.
* Around the room: each person shares a win, challenge, and their key deliverable by the next team meeting.
I’ve been using this cadence and duration for a year and a half. However, I notice that important things come up on the off weeks that I would love to share or discuss with the team.
When that happens, I send an email or IM to everyone and discuss it using that medium, but it’s not as collaborative as the team meeting.
So, I’m thinking about increasing my team meeting cadence to weekly so we can debate on issues more often and ensure everyone is aligned with the direction.
It's insightful to consider the evolution of team meetings and the challenges faced in initiating them.
Considering team dynamics, incorporating interactive elements like team-building activities or short icebreakers can foster a positive atmosphere during meetings.
It not only breaks the boredom but also strengthens team bonds, enhancing overall collaboration and communication.
These are good ideas, and I also believe that teams should regularly meet.
If there is nothing else to speak about and no game to be played, I recommend ending the meeting early. No need to spend the allocated time if you finish early.
That's a good point. I feel that a 30-minute length is better than 60 minutes for that purpose - it feels strange to end a 60 minute meeting after 15-20 (although I agree it should still happen if there is nothing to talk about).
I haven't heard such a complaint, but I feel that 1-hour meetings are intimidating. You know what they say, a task will fill up the time allocated to it - and I feel the same about meetings. When it's 30 minutes, you'll be much better at focusing on the important parts.
I have a suggestion.
From the perspective of the developer, I really find it annoying when there is something on the calendar that gets delayed/cancelled constantly.
It makes me feel annoyed and like my time and energy don't matter.
All and all, great article! :)
So what’s the suggestion? 😅
To not let these things drag on. If something doesn't work on the calendar 2-3 times, it should be removed
Good article! I think another way a team meeting could be useful to the team could also offer the team an opportunity to share an observation/feedback/pain point about a process and invite discussion in a way that saves an additional meeting.
Also, from my experience, when my team introduced Friday team meeting, I introduced an idea to have a Kudos aspect. People like to feel appreciated for what they do, so team meetings could be a way to verbally recognize someone who did a good deed for the team or upleveled others around them
Thanks for the feedback Karthik, those are great additions.
Regarding the kudos - how did you do it so it won't be awkward for people?
I think there are several ways you can make Kudos feel less awkward.
1. Demonstrate example of giving kudos/appreciation to people who upleveled the team or did a good deed youd like to commend. Kudos for the behavior is important (but definitely ask your report if theyre cool with you sharing the kudos publicly is important to not burn bridges). When sharing kudos, I find its really helpful to highlight the IMPACT of the good deed or decision rather than just saying "keep it up Bob".
2. Leveraging your company's employee recognition portal and encouraging your team to do the same goes a long way especially if some feel more comfortable sharing written appreciation
3. Feel free to ask for more context on a given kudos so that when you need to write feedback about the report, you are kept in the loop and tell their story as it happened
4.
Thank you! We don't have an employee recognition portal, but that sounds like a good idea :)
Running weekly meetings is an interesting job. I say interesting because it can feel demotivating if it feels like a waste of time but if done right it can do wonders.
I have had weekly meetings where we brainstorm topics, discuss incidents, mundane stuff, etc.
I found the incidents and brainstorming ones can unblock folks and raise awareness. It is work to build a team culture that values it. You have game it a bit for folks to be excited. I have stories on this one for another time.
Would love to hear those stories :)
For me, the most beneficial ones are with the external guests.
Hi Anton, thanks for being vulnerable enough to share you were afraid. I was afraid too. It's been a year and a half, and sometimes I think about cancelling because I'm not sure what update to share with my team.
One thing that's helped is having a shared document with the agenda. I can update it throughout the week so I'm not panicking last min. Also, other team members can add stuff to so it's not all on me.
What’s your cadence and length of those meetings?
I’ve tried the document and it worked for 6-7 months, but then I skipped it for a few weeks and lost the habit :/
My team meetings are bi-weekly and for 60 mins.
Agenda is:
* Announcements/Discussion topics: These are things I want to share or discuss with my team. It’s also open to everyone, so if they have an idea they can add it too. If I don’t have topics, I’ll share that with the team and just go around the room.
* Around the room: each person shares a win, challenge, and their key deliverable by the next team meeting.
I’ve been using this cadence and duration for a year and a half. However, I notice that important things come up on the off weeks that I would love to share or discuss with the team.
When that happens, I send an email or IM to everyone and discuss it using that medium, but it’s not as collaborative as the team meeting.
So, I’m thinking about increasing my team meeting cadence to weekly so we can debate on issues more often and ensure everyone is aligned with the direction.
Thanks for sharing! Did you get any feedback on those meetings from your team members?
It's insightful to consider the evolution of team meetings and the challenges faced in initiating them.
Considering team dynamics, incorporating interactive elements like team-building activities or short icebreakers can foster a positive atmosphere during meetings.
It not only breaks the boredom but also strengthens team bonds, enhancing overall collaboration and communication.
These are good ideas, and I also believe that teams should regularly meet.
If there is nothing else to speak about and no game to be played, I recommend ending the meeting early. No need to spend the allocated time if you finish early.
That's a good point. I feel that a 30-minute length is better than 60 minutes for that purpose - it feels strange to end a 60 minute meeting after 15-20 (although I agree it should still happen if there is nothing to talk about).
Interesting. I would have no problem with ending early if team trust is high. Could this be a cultural thing?
I guess it's mainly in my head :)
I haven't heard such a complaint, but I feel that 1-hour meetings are intimidating. You know what they say, a task will fill up the time allocated to it - and I feel the same about meetings. When it's 30 minutes, you'll be much better at focusing on the important parts.
That’s true🙂 if in doubt, go for the shorter duration.