When Team Members Raise Concerns with Clarity, Not Anger | Prabhleen Kaur

Summary

---

Podcast Summary

Podcast: Scrum Master Toolbox Podcast

Episode: When Team Members Raise Concerns with Clarity, Not Anger
Host: Vasco Duarte
Guest: Prabhleen Kaur
Release Date: February 12, 2026

---

Main Theme

This episode explores how a Scrum Master's success can be measured not merely by delivery metrics, but by the team’s ability and safety to openly voice concerns with clarity and trust—not anger. Prabhleen Kaur shares her experience and retrospective techniques to build team trust and psychological safety, emphasizing that true team maturity is reflected in constructive, proactive communication and openness.

---

Key Discussion Points & Insights

Retrospective Formats that Build Trust

• Prabhleen’s Favorite Retrospective Format (01:35–04:09):

  • Prabhleen introduces a four-column retrospective format designed to foster deeper engagement and trust within the team:

    • Keep Doing: Continue effective practices and processes.
    • Stop Doing: Immediate feedback on obstacles or pain points.
    • One Thing to Make You Happy: Surface small desires or team wishes (e.g., skipping Friday stand-ups, team outings).
    • Gratitude: Structured, explicit appreciation among team members.

  • She notes increased participation and positive feedback, especially for the happiness and gratitude columns, which offer ongoing insight into team morale and encourage peer recognition.

    “When every 15 days, 10 days, you're sitting with the team and making a point to say thank you to each other... that brings up the space where everybody feels mutually respected.”
    — Prabhleen Kaur (03:56)

  • Prabhleen stresses that these practices allow emergent team needs to surface without waiting for formal feedback sessions.

The Link Between Trust, Retrospectives, and Team Performance

• Trust as Team Accelerator (04:09–05:38):

  • Vasco highlights that trust amplifies team speed and collaboration, referencing "The Speed of Trust" by Stephen M.R. Covey.

  • Appreciation during retrospectives is seen as a critical trust-building tool, not often leveraged enough.

    “Trust is what makes teams speed up... over time increases the collaboration, increases the understanding and increases ultimately the speed of delivery for the teams.”
    — Vasco Duarte (04:51)

• Mutual Motivation Through Helping (05:03–05:38):

  • Prabhleen adds that recognition of contributions motivates both the giver and receiver, reinforcing positive team behaviors.

Defining Scrum Master Success

• A Story of Psychological Safety (06:03–07:51):

  • Prabhleen recounts an experience where a team member proactively raised a critical delivery concern, seeking a collaborative solution without anger.

  • Rather than hiding issues or fostering blame, the team member engaged with Prabhleen and the Product Owner, showing trust and maturity.

    “At that point, I realized that I have really succeeded as a Scrum Master because the team is comfortable enough telling me that this is not working out. And he didn't come to me... with a lot of distress or anger. He was actually conscious... and let's have a conversation about it.”
    — Prabhleen Kaur (06:35)

  • Key Success Metric:

    • A Scrum Master’s success is not about hitting story point quotas, but about creating an environment where team members:
      • Recognize problems early.
      • Raise concerns constructively and calmly.
      • Seek collaborative resolutions.
      • Feel safe and motivated.

• Maturity and Openness (07:51–08:40):

  • Vasco commends the team's ability to surface and address issues together rather than concealing them, calling this a sign of great maturity and effective Scrum Mastery.

    “Not being afraid of it... but actually opening up the conversation, allowing others to bring their perspective in, and then solving it together as a team, I think that shows enormous maturity and... the contribution of the Scrum Master.”
    — Vasco Duarte (08:11)

Rethinking Team Metrics

• Beyond Quantitative Output (08:40–09:25):

  • While stakeholders often prioritize deliverables or story points, Prabhleen advocates that a Scrum Master should focus on:

    • The team’s responsiveness to change.
    • How well the team is collaborating and functioning as a unit.

    “Those numbers could be reflective, yes, but then we have to see that with every passing sprint how well the team is responding to change. And if that is happening very well, this means that the team is working like a team.”
    — Prabhleen Kaur (09:00)

---

Notable Quotes & Memorable Moments

• On Team Emotional Safety:

  “When something goes wrong, they are the people who come to you, not in anger, not with any other emotion, but with concern that we are going to fail as a team if this is not set right. So that's my success matrix.”
  — Prabhleen Kaur (07:21)

• On Building Appreciation into Routine:

  “Appreciation brings a space where the trust is automatically built... everybody feels mutually respected.”
  — Prabhleen Kaur (03:49)

• On Retrospectives Creating Continuous Improvement:

  “I don’t have to wait for another working agreement session... I know what the team is looking at and they want to happen.”
  — Prabhleen Kaur (03:34)

---

Timestamps for Key Segments

• Favorite Retrospective Format & Its Impact: 01:35–04:09
• The Importance of Trust & Appreciation: 04:09–05:38
• Measuring Scrum Master Success—A Team Story: 06:03–07:51
• Team Openness as a Success Metric: 07:51–08:40
• Evaluating Success Beyond Delivery Metrics: 08:40–09:25

---

Summary

This episode underscores that a Scrum Master's greatest achievement is not visible in productivity charts, but in the psychological safety and trust they cultivate, enabling teams to raise concerns constructively. Prabhleen Kaur’s practical retrospective formats and personal stories offer actionable advice for fostering such teams. The conversation is straightforward, empathetic, and full of insights for Scrum Masters seeking to move beyond surface metrics to real team health and maturity.

Transcript

[A]

Hey there agile adventurer, just a quick question.

[B]

What if for the price of a.

[A]

Fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[B]

Hello everybody. Welcome to our success Thursday. This week we have with us Prableen Kaur. Hey Prableen, welcome back.

[C]

Hello. Thank you for having me.

[B]

Absolutely. So Thursday is success day here on the podcast. But before we dive into the success question, share with us Prablin, what's your favorite Agile retrospective format and why?

[C]

For sure. So I do want to share a little anecdote from my side. That is when I joined a team as a new Scrum Master wherein the team was already formed and they were a team since years. When I joined I realized that they are using the three column format of retrospective, which is the most common of all. And the participation was super low. Like this. Despite trying to have a conversation in retrospective, asking questions, pointing the cards out, nothing actually was working for me. So I thought that okay, maybe we should experiment with the retrospectives format. And I chose to do that. And I made four columns out of three. The first was what we should keep on doing, because of course retrospective is the space where we discuss the process and the things we have to improve or the good things we are doing. And the next column was what we should stop doing because we generally get the very immediate feedback there that this is not working for me. So just stop doing it or it is making my life tough. The change I did for the next two columns was the third column is one thing which will make you happy. So it could be any smallest of the thing, maybe a team outing or probably having some space out, not having standups on Friday, Anything, anything which will make you happy. And the fourth column was about expressing the gratitude and this also ties back to the conversation we have had about building trust. Appreciation brings a space where the trust is automatically built. So when every 15 days, 10 days, you're sitting with the team and you're making a point to say thank you to each other for all the work you've done. And it could be anything, you know, somebody helped you with a piece of the code or something was there where you were not there and that person filled space for you. Or it could be a sincere thank you to the team from anybody that, okay, you made the things work out even from the. So that brings up the space where everybody feels mutually respected. So that's the retrospective format I really enjoy using. And of course the team also enjoys because I get great feedbacks there. And especially for the column, one thing which will make you happy, that has made my life easy because I don't have to wait for another working agreement session to happen. I know what the team is looking at and they want to happen. So this is the retrospective format I love using and it has really helped me. So it's about we should keep on doing, stop doing one thing which will make you happy and the gratitude you have for the day.

[B]

I think that gratitude aspect, the appreciation practice is something that we don't give enough attention to. So I'm really thankful that you brought that up also, because in the context of the Tuesday episode, the retrospective is a critical place for us to continuously build trust. Not just when it's gone, but also even if it's there to continuously amplify that trust. Because trust is what makes teams speed up. Right. Like there's this speed of trust book by. Is it McCovey? I'll have to check out the book.

[C]

But.

[B]

But that trust is what really over time increases the collaboration, increases the understanding and increases ultimately the speed of delivery for the teams.

[C]

That's true. And of course I feel that at the end of the day, we all are working and we do work because it sustains us, but we also work to see the good we are doing around. And when I realize as the human being that, hey, I made a little bit of difference for you, it makes the other person super motivated both ways that AI should keep on doing it because it is making the other person better. And of course it is making me in a place where I'm also contributing. So it's a very good feeling, a very sweet feeling to be in that it is a two way street for all the individuals.

[B]

Yeah, absolutely. So this trust that we want to build with the help of Retrospectives is. Is something that helps us as Scrum Masters be successful. But how would we know? So on Thursdays, we want to focus on that question. How would we know? So the question for you, Prablin, is how do you evaluate yourself and your own success as a Scrum Master?

[C]

I honestly want to share a conversation for this one. In one of the teams I was working, we were at a point where we were in production and the team was delivering relentlessly. And at that point, we were not even having the space to sit down with each other, each other as a team. But of course, we have a set of rules and SOPs before we get into the production. And one of the team members, he just walked up to me and he said, this is not going to work out. And he sat me down, he sat the PO down and he had an extensive conversation, and then we had the conversation with the entire team. The reason he was suggesting that this is not going to work out is because we were at the middle layer in the API creation team, so we had to have the deliveries coming from the first layer to us so that we give it to the last layer. But there were a little delays in that situation. At that point, I realized that I have really succeeded as a Scrum Master because the team is comfortable enough telling me that this is not working out. And he didn't come to me or to the PO and to the EM eventually with a lot of distress or anger. He was actually conscious that this is not going to work out. This is what I think we can do better, and let's have a conversation about it. So that was the point. I understood that I must be doing something right. So my idea of success as a Scrum Master is that when you look around, you see motivated people, and when something goes wrong, they are the people who come to you, not in anger, not with any other emotion, but with concern that we are going to fail as a team if this is not set right. So that's my success matrix.

[B]

Yeah, absolutely. That openness of first detecting the problem so that foresight is very important, but then not being afraid of it and trying to fix it on your own, in hiding so that no one can see it, but actually opening up the conversation, allowing others to bring their perspective in, and then solving it together as a team, I think that shows enormous maturity and in my book, also the contribution of the Scrum Master, because it takes effort, it takes time, and it takes practical approaches to be able to create this openness to talk about problems that in this case, they haven't even happened yet. Yep, there was a beautiful way to illustrate it.

[C]

I often feel that when it comes to the success of the team, especially people do get down to how many features were delivered. Was there a marker of story points which the team has touched, or any other metric which tells them they have pushed a lot of increments? But then that's of course a matrix to look at when it comes to stakeholders and when they want to see the completion of the product. But for the Scrum Master, I believe that those numbers could be reflective. Yes, but then we have to see that with every passing sprint how well the team is responding to change. And if that is happening, very well. This means that the team is working like a team. So that's another way to look at the same aspect.

[B]

Yeah, absolutely. Thank you for sharing that with us, Pravlin.

[C]

Thank you.

[A]

Alright, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access tools, over 700 hours of agile Gold, CTO level strategy talks, Summit keynotes, live workshops, E courses, Deep Dive interviews, books, and if you're into no Estimates, we got the pioneers of no Estimates in those Deep Dive interviews as well. Agile Business Intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners. Plus a private Slack community which is free of all of that AI slop you see everywhere. And of course without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place. Connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the [e-mail] membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community.

[B]

Slack. We really hope you liked our show. And if you did, why not rate.

[A]

This podcast on Stitcher or itunes.

[B]

Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.