Pod Insights The Agile Daily Standup - AgileDad Hold Your Team Accountable Without Being a Helicopter Manager About this episode Do you feel like you have to hover over your team? Leading a team is sometimes a work for a herding dog. You need to gather, herd, and protect your team. On top, you need to monitor almost every detail of their work, and frequently intervene in tasks or decisions because otherwise, the needle does not move. Exhausting. When the lack of accountability creeps into your team, someone has to do it. Sadly, people quickly get used to it and let leaders make decisions and count them for mistakes... 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:16 Speaker 00 Don't you make me turn this laptop around, young man. Sorry, I had to.
0:23 Speaker 00 This topic is about holding your team accountable without being a helicopter manager. Now, this is where it's going to get interesting.
0:32 Speaker 00 I've heard lots of team members, especially recently, say they felt like they were reverting back to office space where it felt like, you know, the managers, "Yeah, I just need to know the top five things you did last week, and if you could put those in an email for me, that would be great." Too soon? But, you know, there is a time and a place. I mean, honestly. If you ever felt like you had to hover over your team?
1:03 Speaker 00 Leading a team is sometimes a work for a sheep, a sheepdog, right? You need to gather the herd, you need to protect your team. On top of all this, you need to monitor almost every detail of their work and frequently intervene in tasks or decisions because otherwise the needle just doesn't move. It's just so exhausting. Oh, boy. When a lack of accountability creeps into your team, someone has to do it. Sadly, people quickly get used to it and leaders make decisions and count, and count, and count them from mistakes. You don't want that. People should be able to feel accountable and not rely on leadership as a go-to problem solver.
1:48 Speaker 00 Or, I'm going to go here, ready? Teams and people should be accountable and not always feel like they have to go to the Scrum Master to solve the problem. A lot of teams should go to the Scrum Master to get the needed resources to help resolve the issue so it's not an ongoing thing. But the Scrum Master's not there just to solve every problem for you. This is the difference between enablement and empowerment. Scrum Masters that enable teams are in organizations that are failing.
2:17 Speaker 00 I'm going to say it again, scrum masters that enable teams are in organizations that are failing. Scrum masters that empower teams to solve problems and give them the tools they need, and then take their time to solve problems the team cannot resolve, that's where your winners are. That's where you're going to have good, high performing, strong agile teams. So how do we get there? Well, first, we have to define clear roles and responsibilities. This is in my Agile 12-step program. I talk about it often. In fact, I can tell you, this is step three in the Agile 12-step program.
2:54 Speaker 00 You know the saying, "When everyone is responsible, no one is accountable." I think I've heard that once or twice before. I often think about it when multiple people work on the same thing, same project, same office, same product. And I think of teams too, but oftentimes personalities clash, roles clash, who's making decisions? I went to one group, and they literally had a scrum master, an iteration project manager, a project manager, a release train engineer. By the time you're done, it was like, "Who do I even talk to?" Right? Imagine you work as a pool. To enjoy swimming, you want clear, clean water.
3:37 Speaker 00 So you do your routine without others jumping on you or crossing into your lane. You make sure that you have clear lines, so that it's kind of like one of those Olympic pools where you swim with the lines in it, right? But teams often have to swim in a pool with blurry water, sometimes filled with dirt or muck, sometimes even jello, and people jumping around from place to place, using each other's heads as little standpoints.
4:06 Speaker 00 Ask yourself, does every team member have a well-defined role with a specific set of accountabilities? If your answer is no, you probably have accountability trouble. I'll just call it dirty pool, right? There's poop in the pool. In principle, when everyone knows exactly what they should be accountable for, it reduces the tendency to defer decisions or tasks to a manager or a scrum master or a lead. Likewise, nobody's going to come out and play to victim. If it's not done, it's because you didn't do it. Start by looking at what should be done and what skills you have on your team and try to make sense of it. Try to get it all panned out. Try to get it all worked out together. Next is ownership culture.
4:51 Speaker 00 Everyone should want to become an expert in their area. They should have a growth mindset, not a fixed mindset. They should be self-starters. It sounds nice, doesn't it? But honestly, how many people are really like that? Especially when you can just go to a manager and ask them to solve it for you. Easy peasy, right? But there's a trick that many people don't know about that can help help others feel accountable and take ownership. Are you ready? Let them make the decision. I talk about this a lot in my class. Where even if I know the answer, I'll go to a leader or a manager and I'll say, hey, I was thinking this. What's your thoughts? And then when I tell me, I'm like, oh, I'm so glad you thought of that. And that's exactly what I thought of before I walked in the room. I'm just leading them down the path, right?
5:34 Speaker 00 Instead of telling them, this is what we need to do, let them come up with the options and decide. If you decide and it's wrong, you can be angry about yourself and have a desire to fix it. But if your leaders decided for you, you could kind of ignore it because it's their fault. I, I, I don't want to get there, right? So your team members take ownership by getting involved. They might not like it in the beginning, but it can refresh your team's culture a lot. Let them help come up with goals, processes, innovation. Let them help refine it and doing things like that. Trust me. If you do this, the pool will be easy to swim in and you'll, you'll be able to breathe. All right, let's talk about peer-to-peer feedback. Surprise, well, not really.
6:19 Speaker 00 Communication is the solution to just about everything. If people can talk to each other. If, here, I'm going to go here. If people can tell each other off, they can certainly hold each other accountable, right? I've seen organizations where people are walking on eggshells every time Johnny walks in the room or whatever the case may be here. When Stephanie walks in, we gotta be careful what we say. You shouldn't be that way. If you are comfortable in your own shoes and comfortable around the other teams. And sometimes people jokingly say, Lee, you make Deadpool look like a PG movie. And I, it's not that I'm vulgar or profane. It's just, I'm very direct about what I have to say. So I think this whole feedback culture, dream big.
7:05 Speaker 00 Team meetings are fueled by people that talk to each other and help each other improve. Effective teams share knowledge and get this, they share fun and genuinely engage in what they do. Feedback is, Feedback 360 is not, Feedback is 360, not Feedback 360. Yeah, they are set right. You don't need a manager to tell you what you can improve and work on. All right, here's what we can improve next time and here's what we can work on. Let's hold hands. Go team, right? All you need is the guts to ask around. Your teammates see what's going on, take advantage of working with a team. Peer feedback is awesome because then it gets to you before leadership comes around and says, hey, this is what you're doing wrong.
7:47 Speaker 00 How about this? Recognize consequences and understand rewards. Unpopular strategy? Likely. Let me tell you about one of my colleagues. One of my colleagues did not care about what reports he delivered. He didn't check them. He even put random numbers in sometimes. He cheated clients. What happened to him? Nothing. When he left the company, another colleague took over the job and had a lot to explain to the client when all the mistakes were discovered. The corporate umbrella covers cases like this, but how do you want to hold your people accountable without consequences? When you do your job, okay. When you don't do your job, okay also. Right?
8:31 Speaker 00 It doesn't, every team needs to have a system in place where there are clear consequences for not meeting goals or expectations. Likewise, they need to, uh, they need to have rewards or a reward model in place for exceeding those expectations. It doesn't have to be something dramatic. One million dollars and you get a car and you get a car, you know, we can't do that. But think of such things as simple recognition in team meetings, bonuses, spiffs, additional training or supervision. There's lots of things you can do and even if people are doing bad, you can give them additional training and more basic things, right? But I think the key here is you don't want to neglect good behavior.
9:13 Speaker 00 Uh, link accountability directly to tangible outcomes. Only when team members understand what the tangible outcomes are, are they going to take their responsibilities seriously? You can't just say, oh, we're going to do all the things. That never works. But I think the key to all of this is don't hover over them. They know what they're supposed to do and they know how to do it. Helicopter managers are a sign of an incapable team. But they may also miss the mark because they don't understand role clarity, ownership, feedback culture, consequences. We need to get in an environment where everyone takes on some accountability because if not, why bother? It's someone else's problem, not mine, right?
9:57 Speaker 00 So at the end of the day, you have to ask your question, yourself a question, especially if you're in a Scrum Master role. You have to ask, is this a situation where I have to solve it for them? Or is this a situation where I'm going to empower them to solve it themselves? Uh, maybe it's time to start not solving things for them. Let them get some work done. Let them understand and figure out why these things are happening. And let us get to work now so we can perfect everything and make everything as good as it could possibly be for the team and for the organization. That's going to do it. I hope 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. As always, we encourage you to stay healthy, stay well and stay agile, my friends. Until next time, do take care. Bye now.
Previous Work Spilling Over? How to Know if You’ve Got a Rollover Habit - Mike Cohn Next Goat Yoga & Walking the Plank: A Lesson in Balance Page updated November 7, 2026 · transcript and summary are machine-generated