Pod Insights The Agile Daily Standup - AgileDad The Unglamorous Truth About Building Trust About this episode The Unglamorous Truth About Building Trust
I spent my first few months as a Scrum Master chasing the wrong thing. I thought trust was something you earned with one big moment. Deliver a miracle sprint. Shield the team from an impossible deadline. Stand up to that one difficult stakeholder in a meeting. I was waiting for my chance to be heroic.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 A very close friend and subscriber to the podcast sent in a request for me to review this note. It says, "I spent my first few months as Scrum Master chasing the wrong thing. I thought trust was something that you earned with one big moment. Deliver a miracle sprint, shield the team from an impossible deadline, stand up to that one difficult stakeholder in a meeting. I was waiting for my chance to be heroic and shine. Then, one of my senior team members, Marcus, taught me something I still think about every single week. Trust is a water system, not a trophy." This should be interesting. "Water engineers don't wait for pipes to burst. They flush lines, test samples, check
0:58 Speaker 00 valves. On Tuesday mornings when nothing's wrong, their best work is invisible. No emergencies, no applause, just the tap working when someone turns it on." That is what trust actually should look like in agile teams. It's the Scrum Master who updates the team before they ask about that delayed dependency. It's admitting, "I messed up in a meeting invite" instead of pretending the calendar glitched. It's the fifth time you moved a blocker out of the way without announcing it in Slack. I learned this the hard way when I missed a single commitment to Marcus. One missed follow-up on a tool request he'd mentioned. It wasn't dramatic, but I watched his eyes change during a stand-up
1:40 Speaker 00 the next day. He stopped volunteering information. He started giving shorter updates. The trust pipe had sprung a small leak. Here's the brutal part. That leak took me six weeks to repair. Six weeks of consistently following through, remembering the small details, showing up. One moment of inconsistency caused me over a month and a half of credibility. If you're new to agile leadership, stop waiting for your hero moment and start doing this instead. Send the status update, even when there's nothing new to report. Still waiting on a legal review. I'll check again on Thursday." Builds more trust and radio silence, followed by, "Oh, sorry, I forgot to update you guys, but yeah, it's still in flow."
2:24 Speaker 00 Admit mistakes immediately. I should have caught that sooner carries more weight than any excuse you could possibly give. Your team already knows that you're human. You're not perfect. Pretending otherwise just makes them wonder what else you're trying to hide.
2:40 Speaker 00 Keep the small promises you make. Said you'd review the PRD by Friday? Do it by Thursday. Promise to look into a tool request? Put a reminder in your calendar now so you don't forget. These tiny deposits matter more than the quarterly team building event.
2:59 Speaker 00 Document decisions in real time. That quick hallway conversation with your product owner? It counts. Send a summary before lunch. Your team shouldn't have to guess what was decided when they weren't even in the room.
3:13 Speaker 00 The truth is, you will mess up. I know I still do. But here's what I've learned about repair. The reservoir often fills slowly. Inconsistency drains it fast. There's no shortcut, no dramatic gesture that speeds it up. Just patient, boring consistency. Showing up, following through, doing what you said you were going to do again and again and again and again. Your best days as a Scrum Master are like nothing happened at all. Like everything was fine. No crisis averted, no standing ovation. Just the team trusting you enough to tell you about problems while they're still small. Just developers raising blockers in a stand-up without hesitation.
3:57 Speaker 00 Just stakeholders believing you when you say, we'll get to that. We'll figure it out. That's not boring. That's kind of the whole point. Ask yourself the question, what's one small commitment you can keep this week? That you might normally let slide or set aside? I would love for you to drop a comment after this and tell me what you think and what you came up with. Because what I can tell you is these types of thoughts, you're not alone. Other people have these types of thoughts. And it's just a matter of trying to define what a Scrum Master really does. And it's every evolving role where Scrum Masters, Agile Project Managers, AI Integration and Change Management are all kind of coming to a head.
4:37 Speaker 00 I think it's important for us to understand why building trust is important and how we can go about doing. That's going to do it for today's episode. I hope you enjoyed it. If you have a topic you want us to discuss, and thank you for that email. If you have a topic you want 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. Bye now.
Previous Not Every Backlog Item Needs Detail - Mike Cohn Next 7 Mindsets of High Performers That Will Change How You Work Page updated November 6, 2026 · transcript and summary are machine-generated