How to Stop Wasting Time in Daily Standups: A Manager’s Guide

Daily standups are a cornerstone of agile development, designed to foster communication and keep teams aligned. However, for many engineering managers, they've become a source of frustration, often extending beyond the mythical "15-minute rule" and eating into valuable development time. If your team's daily syncs feel more like a time sink than a productivity booster, it's time to rethink your approach.

The True Cost of Synchronous Meetings

While the intention behind daily standups is good, their synchronous nature often introduces hidden costs. The most significant is context switching. An average developer can lose 30 minutes to context switching for every meeting they attend. Multiply that by a team of 5-10 developers, and you're looking at hours of lost productivity daily, not just the meeting duration itself.

Beyond context switching, synchronous standups can:

• Disrupt deep work periods, especially for developers in different time zones.
• Lead to irrelevant discussions that only pertain to a few team members.
• Become a reporting exercise for managers rather than a collaborative problem-solving session.
• Pressure introverted team members, leading to less comprehensive updates.

Ideally, daily syncs should take less than 15 minutes total for the whole team. If you're consistently exceeding this, it's a clear signal for change.

5 Steps to Implementing Asynchronous Standups

Shifting to an asynchronous standup model can dramatically improve your team's efficiency and focus. Here’s how to do it:

1. Define Clear Standup Questions: Stick to the core "What did you do yesterday?", "What will you do today?", and "Are there any blockers?" questions. Avoid scope creep.
2. Set a Consistent Reporting Time: Establish a window for team members to submit their updates. This ensures everyone has time to provide thoughtful responses without interrupting their flow.
3. Choose the Right Communication Channel: A dedicated chat channel (like Google Chat) is ideal for collecting and sharing updates. It keeps communication centralized and accessible.
4. Encourage Concise, Actionable Updates: Train your team to provide brief, to-the-point updates. Blockers should be clearly highlighted, and non-critical discussions should be moved offline.
5. Review and Follow Up Effectively: As a manager, your role shifts from facilitating a live meeting to reviewing reports and proactively addressing blockers or facilitating discussions that arise from the updates.

How Standupify Automates Asynchronous Standups in Google Chat

Standupify is designed to streamline this transition, turning your daily standups into an efficient, asynchronous process within Google Chat. Here’s how it helps engineering managers:

• Automated Check-ins: Standupify prompts your team members for their daily updates at a scheduled time directly in Google Chat. No more chasing down individuals or interrupting their work. You can customize your check-in settings to fit your team's schedule.
• Customizable Questions & Jira Integration: Configure your standup questions to align with your team's needs. Standupify can even pull relevant Jira tasks automatically, allowing team members to quickly reference their work without leaving Google Chat. Learn how to customize daily standup questions and configure Jira JQL.
• Centralized Daily Reports: All team responses are collected and compiled into a single, easy-to-read daily report. This report can be posted to a designated Google Chat space, providing a transparent overview of progress and blockers for the entire team.
• Manager Dashboard & Insights: Instead of listening to individual updates, you can quickly scan the Daily Report Dashboard to identify blockers, track progress, and understand team sentiment. This frees up your time for strategic thinking and problem-solving.
• Reduced Context Switching: By allowing team members to submit updates on their own schedule, Standupify eliminates the need for a synchronous meeting, drastically reducing context switching and allowing developers to maintain their focus.

Getting started is simple. If you haven't already, install the Standupify Google Chat bot and begin configuring your first asynchronous team check-in.

Conclusion

Embracing asynchronous standups is a powerful step towards a more productive and less interruptive work environment for your engineering team. By leveraging tools like Standupify, you can transform a once-dreaded daily ritual into an efficient mechanism for communication and progress tracking, ultimately giving your team more time to do what they do best: build great software.

Frequently asked questions

What are the main benefits of asynchronous standups for an engineering manager?

Asynchronous standups help managers save time by eliminating live meetings, reduce context switching for their team, provide a clear written record of progress and blockers, and allow for more thoughtful updates from team members.

How does Standupify help reduce context switching for my team?

Standupify allows team members to submit their updates at a time that suits their workflow, rather than forcing them into a synchronous meeting. This means they can complete their standup without interrupting deep work, significantly reducing the cognitive load of context switching.

Can Standupify integrate with Jira for my team's updates?

Yes, Standupify offers robust Jira integration. It can automatically pull relevant tasks and issues into the daily check-in, allowing team members to easily reference their work when providing updates, streamlining the reporting process.

How do I ensure my team actually provides updates if there's no live meeting?

Standupify sends automated reminders in Google Chat, prompting team members to submit their updates. Managers can also review the Daily Report Dashboard to quickly see who has submitted their report and follow up as needed, ensuring accountability.

What if a team member has a critical blocker that needs immediate attention?

While asynchronous standups reduce the need for live meetings, critical blockers should still be escalated immediately. Team members should be encouraged to flag urgent issues in their Standupify update and also reach out directly to the relevant individuals or channels for immediate resolution.