Pod Insights The Agile Daily Standup - AgileDad Rebuilding Psychological Safety About this episode Rebuilding Psychological Safety
If people feel unsafe, they do the minimum and pray no one notices. If the bar is too low, everyone’s happy… until the customer sees the work. The sweet spot? High safety and high standards. People speak up, try things, and still hit the mark. Think: honest kitchen with a strict head chef, and nobody burns the risotto, but jokes are allowed.
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:16 Speaker 00 We've all been there before. Psychological safety, completely gone. People freaking out, trust broken, everything blows up. You can sense in a person's voice that the momentum has just left the building. And it's usually after some type of performance review or some type of intervention that takes place. Those are usually the times when you see this the most. And I think we just have to face the fact that if people feel unsafe, they are going to do the bare minimum and just pray no one notices that they're there. If the bar is too low, everyone's happy until the customer sees the actual work. The sweet spot, high safety, high standards. People speak up, they try things and still hit the mark. Let's think about it.
1:01 Speaker 00 Honest kitchen with a strict head chef. Nobody burns the risotto, but jokes are allowed. It just makes sense that that's the type of kitchen you'd want to work in. If it was crackdown and everybody was just clamped down, it would be a lot harder to work in that environment. And I think the piece that we're missing is the reset mechanism. And when I say the reset mechanism, what do I mean by that? I'm talking about simple, tight and repeatable. We're going to run three short rituals. Each ritual will take under an hour, but sends a loud signal that it's safe to contribute so the bar stays high. The first one we'll refer to as a transparency brief now. Why?
1:44 Speaker 00 Kills the rumors and replaces guessing with clarity. Just makes it simple. So share what changed about roles, expectations, processes, and what hasn't about quality, timeliness and values. Restate the non-negotiables, read your red lines. Explain how you'll measure progress for the team, not just for the person who struggled. And say it like a human. We coach in public on process. We give consequences in private. We're not hunting for culprits out here. We're hunting for clarity. Here's what stays the same. Here's what we're changing. And here's how we'll know that it's working. If you want to score bonus points, bring donuts. Clarity always tastes better with donuts, especially Krispy Kreme glaze. But bring a handout with you if you need to.
2:29 Speaker 00 Make it a one pager that outlines goals, what done means, quality gates, next milestones. I often refer to this in my training as a team quick start guide. Now, I know many of you are probably not old enough to remember this, but back when I was young, I bought a VCR. It was a video cassette recorder and you could record movies right there on that VC. Okay, I'll stop. The voice is terrible, but the point I'm trying to make is inside the box, it had a 212 page manual. You know, the one I'm talking about, the one that no one ever read. And then in addition to that manual, it also had a single sheet of paper on top. That was a color slick and it's a quick start guide. And on two sides of the paper, it told you how to the three wires and you were in business. That's what you need, the quick start guide to reset the team. Let's go to the second one.
3:15 Speaker 00 I call it voice mechanisms. So this one, once again, short setup, but why do we do it? Fear shrinks voices. So you have to invite those voices back. So you can run an anonymous pulse with three quick questions like, do you feel safe asking for help? Do you know what good looks like? What's one friction we should remove? Hold open office hours, 30 minutes, twice this week, twice a week. Cameras are optional. Pets are always welcome. That's always a good thing. And start with a safe to try list, three to small, three to five small experiments that we will attempt together as a team with no blame if they completely flop. If you're unsure, got an idea, add it to the safe to try. Locked, tell me, we'll help move the boulder together.
4:00 Speaker 00 Many hands make the load light. And I think if you're trying to do this in real life, we should celebrate lessons, not just wins. We still honor the red lines, quality, compliance, customer safety, et cetera. And no experiments with production data. We don't want to introduce Captain Chaos in the mix and have everything just completely blow up in our face. A last one I'll talk about is called servicing. And after a rough patch, people forget that they can win. They they forget what it's like. So I think like for a demo or debrief, everyone shows one tiny improvement. A cleaner checklist, a clearer PRD, faster handoff. Try naming a scale behind it. Clarity, pairing, test coverage, etc. Take screenshots and bullets.
4:43 Speaker 00 Make it like a mini playbook entry, if you will, so that way you have all these different things together. And make sure you start off with something like, today, we're celebrating the habits that make great work repeatable. Show one change that others can steal. I mean, you know, adopt. It's it's stealing. But a playbook of wins allows new folks to learn from what we've done in the past. That small confetti moment should be allowed. It should be something that you can do. Call it your book of files. Yes. Okay. If you keep the standards high, then this becomes a public process, private consequences type of situation. If you need to escalate, do it. One on one, but with dignity.
5:27 Speaker 00 Make sure you focus on cadence over control. Quick, short, 20 minute reviews weekly. That beats daily play by play when it comes to this type of thing. And clarity always beats pep talks. Define done. You'll argue less and shit more. I I think that if you do this correctly, you should see over the course of two to four weeks, some signals to show you that it's working. Things like more questions in meetings, more tiny experiments, faster peer feedback, fewer nasty surprises at the finish line, all those things, right? So I think it's only logical and fair that you try and experiment and try new things, knowing that when you try new food, it might taste good. That's going to do it for this episode. Thank you, Daniel Tiger.
6:10 Speaker 00 If you have a topic you want us to discuss, learnmoreatagiledad.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 The Man Who Proved Meaning Is Stronger Than Suffering Next 5 Habits to Keep Your Team Motivated Page updated November 6, 2026 · transcript and summary are machine-generated