- \n
- Scheduling huddles at a convenient time for everyone is difficult (or often impossible).<\/strong> This is especially the case for larger teams that are distributed across several different time zones. <\/li>\n\n\n\n
- They can take too much time. <\/strong>Morning huddles should last less than 15 minutes, yet they often turn into 30-minute sessions where team members actively discuss how to solve a certain problem. (This isn\u2019t the right place to do so, and it should be shelved for after <\/em>the meeting.)<\/li>\n\n\n\n
- They disrupt your workflow. <\/strong>Synchronous meetings require you to stop what you\u2019re doing and switch gears. This can be frustrating and bad for productivity, especially if you just got into a flow state and are making meaningful progress on a task.<\/li>\n\n\n\n
- They force team members to sit through irrelevant updates. <\/strong>If some team members discuss updates that don\u2019t concern everyone, others will inevitably get frustrated and tune out. This undermines the whole point of morning huddles \u2014 to quickly get everyone aligned.<\/li>\n<\/ul>\n\n\n\n
As a remote team that\u2019s been doing daily huddles<\/a> since 2009, we\u2019ve experienced these issues first-hand<\/a>. <\/p>\n\n\n\n
This led us to embrace asynchronous huddles as a way to quickly keep teams aligned, without being disruptive to work.<\/p>\n\n\n\n
To help with the task we created Geekbot \u2014 a free<\/strong> tool for Slack and MS Teams that has helped companies like GitHub (see case study)<\/em><\/a>, Shopify (see case study)<\/em><\/a>, and Zapier (see case study)<\/em><\/a> replace video-call huddles with an asynchronous format that\u2019s faster and less disruptive.<\/p>\n\n\n\n
In this post, we\u2019ll show you how to run effective morning huddles in Slack or MS Teams with Geekbot, while avoiding the problems we mentioned above.<\/p>\n\n\n\n
Note:<\/em><\/strong> Click here<\/em><\/a> to create a free Geekbot account. Our tool is free for teams with up to 10 active participants.<\/em><\/p>\n\n\n\n
<\/div>\n\n\n\nThe Basics of Running Asynchronous Morning Huddle Meetings with Geekbot<\/h2>\n\n\n\n
<\/div>\n\n\n\nGeekbot offers pre-made templates for daily standups<\/a>, retrospectives<\/a>, and many other types of meetings.<\/p>\n\n\n\n
![\"\"](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2023\/06\/new-templates-page-1024x671.png\")
![\"\"](\"data:image\/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==\")
![\"\"](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2023\/06\/custom-workflow-manage-questions.png-1-1024x571.jpg\")
![\"Standard](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2022\/05\/11-Best-Software-Tools-for-Remote-Teams-for-All-Use-Cases-5-1024x902.png\")
![\"See](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2022\/05\/11-Best-Software-Tools-for-Remote-Teams-for-All-Use-Cases-6-967x1024.png\")
![\"Slack](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2022\/07\/Slack-report-reaction-1024x626.png\")
![\"Frequency](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2019\/01\/Untitled-18-1024x479.png\")
![\"Choose](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2019\/01\/Untitled-19-1024x312.png\")
![\"Set](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2022\/01\/image17-1-1024x256.png\")
![\"Standup](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2021\/10\/How-to-Effectively-Use-Our-Microsoft-Teams-Retrospective-App-10-1024x723.png\")
![\"Select](\"https:\/\/geekbot.com\/blog\/wp-content\/uploads\/2022\/08\/image2.png\")
- They can take too much time. <\/strong>Morning huddles should last less than 15 minutes, yet they often turn into 30-minute sessions where team members actively discuss how to solve a certain problem. (This isn\u2019t the right place to do so, and it should be shelved for after <\/em>the meeting.)<\/li>\n\n\n\n