Pod Insights The Agile Daily Standup - AgileDad Which is the MOST Effective Agile Meeting? About this episode Which is the MOST Effective Agile Meeting? I remember working at a startup where every day began with meetings. Planning on Monday, follow-ups on Tuesday, status on Wednesday, dependencies on Thursday, and retros on Friday. The team spent more time justifying their work than doing it. That’s when I learned something I’ve never forgotten as a CTO: an unnecessary meeting is a silent tax on time and energy. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 I recently had a student ask me about, out of all the meetings, which meeting did I think was the most effective? So I sat here and I tore myself up a little bit, I'm sorry. It's gotta be the retrospective, because that's the place where you have continual improvement. That's the place where everybody can focus on doing better. But then I said, "No, I think it has to be the daily scrum, because that's where you get everybody on the same page. You start talking the same language. You want to make sure that if there are obstacles, that they're either being addressed, or that they're brought up in this meeting if absolutely necessary. And, you know, it's good to know what's going on. But then I said, "No, I said it's gotta be backlog refinement, because that's where you're getting everything prepared, so you can make sure your sprint planning meeting is most efficient." And I said, "Well, wait a minute.
0:57 Speaker 00 If that's a preparation for sprint planning, then it has to be sprint planning, because that's where, you know, you're really getting into the minutia of what the team's going to be doing and making sure you get that right, so the team can continue to make progress is important." And then I thought, "Oh, my goodness. What good is it to build something if nobody looks at it? It has to be the review." So I was sitting there going, "Oh, my goodness. That is the worst question ever from a student." And if you know, you know. We were doing one of the "ask anything" rounds that I do in my training all the time. And they were expecting an answer. They wanted an answer. So I had to sit and dig deep. So when I say I dug deep, I remember my early days of Agile, working at a startup where every day began with meetings, planning on Monday, follow-up on Tuesday,
1:42 Speaker 00 status report on Wednesday, dependencies on Thursday, retros on Friday. The team spent more time justifying their existence and justifying their work than they actually did doing it. This might sound a little political, but I really don't mean it to be that way. That's when I've learned something I've never forgotten as a CTO. An unnecessary meeting is a silent tax on time and energy. I'm gonna say that again. An unnecessary meeting is a silent tax on time and energy. So here's an example. I'm gonna call a developer Maria. Maria was one of our top developers, creative, focused, and committed. Yet every day she left meetings feeling visibly and physically frustrated.
2:26 Speaker 00 "I thought I could spend more time explaining what I do than actually doing it," she told me one morning. I observed her for a day. She attended six meetings. She didn't write a single line of code. The result: An entire sprint lost to context switching and interruptions because she never got to do her job.
2:45 Speaker 00 One morning, I received a calendar invite title: "Define Performance Strategy for Payment System." Eight people were invited. Before accepting, I asked in a team channel, "What is the specific goal of this meeting? What info do we need to decide?" Within an hour, one engineer shared logs and metrics. Another proposed an indexing fix. And the infrastructure team suggested a caching layer. What would have been a one-hour meeting turned into a 20-minute async thread. Everyone contributed with full context. No one was interrupted. The meeting was canceled before it even started. That's when it clicked. Many meetings aren't inevitable. They're just a reflexive response to uncertainty.
3:30 Speaker 00 But if you anticipate the goal, you might solve the meeting before it ever happens. It's the cost of a meeting isn't just related to calendar time. It's a cost of broken focus, lost context, and disrupted momentum. A 30-minute meeting with six people costs three hours of human attention. And if it doesn't end with a decision, that's a sunk cost.
3:55 Speaker 00 I want to say it was the mythical man month. I think it was Fred Brooks was the author of the mythical man month. Adding people and communication to a late project only makes it later. And in Peopleware, another book, DeMarco and Lester reminded us that real productivity comes from meetings, real productivity comes not from meetings, but from protecting deep uninterrupted work. So what do we need to do instead? Well, as a CAC leader, I've worked to create an environment where the work speaks for itself. Decisions are documented, not repeatedly discussed. Dashboards and KPIs replace status meetings. Standups are check-ins that are fast and not rituals, mostly for accountability focus.
4:40 Speaker 00 We value clear concise writing over vague alignment calls. These principles mirror many of the manifestos that I've seen out there from other agencies where they default to asynchronous document everything and trust the team to operate without constant supervision. It's not just efficient, it becomes respectful at that point. So if you're trying to show respect for the team, it doesn't mean that you're going to kill all your meetings. So a lot of people come, come at me now. Don't come at me sideways. A lot of people come at me sideways and say, so you're saying we should never meet? We should never have meetings? Of course not. Some meetings really matter to resolve a conflict, to build connection,
5:22 Speaker 00 to unblock an urgent decision. But those meetings are way more rare than the meetings we feel like we need to have every day. I just think the rest of the work, if you did this, could be replaced or automated or avoided entirely in meetings. You know, you don't need to have a meeting to get those things done. A good meeting can save a situation, but a bad meeting can kill a day. So you gotta, you gotta take that into consideration before you call a meeting. One of the biggest offenders I saw was a scrum master who every time the team would deviate even a little bit from the expectation during a daily scrum. Whoop, let's take it offline, take it offline, take it offline, we don't need to do it now, offline, offline, offline. You know, I'm just like, geez. Every single time he said,
6:06 Speaker 00 let's take it offline, what he didn't realize was he was creating another meeting. And the team was so frustrated, they were just like, I spend, you know, more than half my damn meetings. And they were right. So I think that the biggest job you can do as a leader is to protect your team from those wasteful meetings, to make sure they have just enough that they can to establish whatever you're trying to do, whatever your goal is, you want to establish a set of productivity that's unsurpassed, and you want to make sure the meeting has the rats, has a clear roster of only the people that need to be there, it has a good agenda, it's time boxed, and I think that if you do those things, those are the things that are going to help you be successful, not just in this meeting, but in all your meetings. So that's going to do it.
6:51 Speaker 00 So the most effective meeting is actually the one that never happens. I hope that you enjoyed this episode. If you have a topic you want us to discuss, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous Transform Team Trust In Five Seconds Next 5 Tiny Leadership Habits You Can Do in Under 5 Minutes for Massive Results Page updated November 7, 2026 · transcript and summary are machine-generated