Pod Insights The Agile Daily Standup - AgileDad The Best Retrospective You’re Probably Not Doing - The Introspective About this episode The Best Retrospective You’re Probably Not Doing - The Introspective - Ro Fernandezhttps://medium.com/@rociofernn/the-best-retrospective-youre-probably-not-doing-e2622c1ecd12A few months ago, we kicked off a cross-functional project that had everyone excited — product, design, engineering, marketing… Energy was high. The goal was clear. At least, we thought it was. Fast forward three weeks. Things were already slipping. Some teams were waiting on decisions that hadn’t been made. Others were building in parallel, but with different assumptions. And one team member quietly said in a 1:1:“I’m just not sure what success actually looks like here.”That’s when it hit me:We hadn’t missed the retro. We had skipped the prevention. 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 Just last week, I featured an article from Ro Fernandez, and apparently somebody's a big fan because they sent in another one of your articles for me to review. This one is going to be interesting. It's called "The Best Retrospective You're Probably Not Doing." Now, I'm going to read through the article. I'm going to give you live commentary as I go, and this is my first read-through, Ro, so I've never read the article before. Let's get started. "The Retrospective That Actually Works Before You Need One." Interesting. "A few months ago, we kicked off a cross-functional project that had everyone excited: product, design, engineering, marketing. Energy was high. The goal was clear, at least we thought it was. Fast forward three weeks. Things were already slipping. Some teams were waiting on decisions that hadn't been made. Others were building in parallel, but with different assumptions. And one team member quietly said in a one-on-one,
1:00 Speaker 00 "I'm just not sure what success actually looks like." Then it hit me. We missed the retro. We'd skipped the prevention. "Most teams wait until things go wrong to decide to reflect. But what if we paused earlier, before the fire, and actually looked for gaps?" "That's when I started using a much simpler, more human approach to team retros and planning check-ins. It's fast, it brings clarity, and it creates alignment without endless talking. So far, I'm in. This sounds interesting. But is it a retro if it happens before? I'm just curious. We'll have to figure out the name." So, here's how it works. They call it the "traffic light exercise." Now, those of you who know me know that I have something I call "red light, green light report", so I'm a big fan of these types of exercises, so let's see where this one takes. It says, "Give your team three to six dots.
1:45 Speaker 00 Green is for what's working well, orange is for what needs improvement, and red is for what's not working at all. Give them two to five minutes and have them place their dots on a shared board with these key areas: timeline, resources, roles and responsibilities, goals, decision-making, communication, and anything else tied to work." Now, I'm guessing when they're saying "resources" here, they... Well, it could be money. It could be financial. We haven't cleared that up yet. Those roles and responsibilities is next, but I wonder if resources could be people as well here. So maybe we need to add people to this list just to make sure we didn't miss anything. And what you get from this is pure gold. You immediately see where people feel confident, where they feel unsupported, unclear or worried. You don't have to guess. It's visual. It's anonymous if needed, and it opens the door for real conversations.
2:29 Speaker 00 Why this works and when to use it. Most retros look backward, but by then you've already paid the cost of the problem. This method helps you name the problem before it shows up or revisit it with more precision when it does. In fact, if you had the same method after too, as a team retro. You can use it at the start of a project to pressure test the plan, midway through to check for blind spots, and after completion to reflect on and improve for next time. It turns reflection into prevention and turns your team into co-owners of the process. Because most of the team's problems aren't about effort. They're usually about lack of clarity, misaligned expectations, unspoken assumptions, missing resources, unrealistic timelines, or simply not knowing, or not knowing what's not working until it's too late.
3:13 Speaker 00 And giving your team language, structure, and safety to name those things, that's not a retro. That's just good leadership. This is interesting, so I'mma pause here. I love the idea. It creates that container of psychological safety. It helps people understand how to work together and it utilizes some of the radical candor concepts of talking about things before they get to the point where they need to be talked about. So I'm a huge fan so far. I love what you have here. I think it's a great idea. I think we need to change it because it's not really a retrospective if you're not retrospecting on something that happened. And maybe we could call it an introspective? I like that because an introspective is introductory and it just kind of gauges where people are in the heat of the moment. So for me, you know, I don't know that the title is the way I would have worded it, Rob,
3:58 Speaker 00 but everything else about this is screaming, hey, 100% go for it, right? So you encourage people, you say, try to set your next kickoff. I'd love to hear how it goes. If you've used something similar to help your team, drop it in comments. I'm always collecting better ways to make work actually work. Oh, I can tell that we have a lot in common. In fact, I hope you're listening to this because I am going to invite you to be a guest. On one of the podcast episodes, because I feel like we connect in many ways. And I feel like this is this is the beginning of a good friendship. I like the materials that you put out so far. I haven't found anything yet that I you know, adamantly disagree with. So yeah, let's make that happen. For everyone else, I hope you enjoyed this episode.
4:36 Speaker 00 Very straightforward and a good idea, something fun to try. The only other part that I don't want to say bothered me, but the only other part that I thought it could potentially be a red flag is the anonymity. One of the things that I talk about when I discuss retros and introspectives is that I don't want it to be anonymous. I want people to feel comfortable talking in front of other people. And you know, I know at first for brand new teams, maybe the anonymity is important, but I want teams to get to the point where they're so confident in their beliefs that they can openly talk to others about how they feel and what's going on. So for me, retros are not a place for anonymity. But outside of that, everything else is great. Everything else that you have here is awesome. And I hope that you can maybe update this and call your introspective.
5:19 Speaker 00 Because I think you're on to something here. And I don't think it's just another meeting. I think it's something to help us prepare. And I think it's a good idea. That's going to do it for this episode. I hope you enjoyed it. If you have a comment, question, concern, or an article you want me to review, feel free to reach out, learn more at agiledad.com. I'd love to hear from you. And as always, I encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous Top 5 Ways to Be Better at Giving and Receiving Praise Next Top 4 Ways to Eliminate Backlog Bloating Page updated November 6, 2026 · transcript and summary are machine-generated