Fear-Free Teams—Creating Psychological Safety for High Performance | Mariano Gontcher

Summary

Podcast Summary

Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Episode: Fear-Free Teams — Creating Psychological Safety for High Performance
Guest: Mariano Gontcher
Host: Vasco Duarte
Date: September 4, 2025

---

Episode Overview

This episode centers on how Scrum Masters can foster psychological safety and high performance in Agile teams. Mariano Gontcher, an experienced Scrum Master, shares his favorite retrospective format and his evolving perspective on what truly marks success for Scrum Masters. The discussion emphasizes actionable techniques for increasing team trust, self-management, and continuous improvement.

---

Key Discussion Points & Insights

1. Mariano’s Favorite Retrospective Format: “From Frustration to Action”

[01:23–07:01]

• Retrospectives are the heart of continuous improvement
  Mariano believes retrospectives are vital for building and evolving teams.

• Format Overview:

  • Starts with catharsis: team members anonymously write down their biggest frustrations from the sprint on sticky notes (“frustration box”).
    • “It’s important, the feelings, because it’s not information — you feel bad, good, okay.” — Mariano [03:01]
  • All frustrations are grouped and displayed for collective analysis.
    • This helps expose shared pain points and demystifies the sense of isolation.
    • “Maybe you have a frustration but never say during the retrospective and the other people next to have the same frustration. It’s real.” — Mariano [03:48]
  • Team votes on which frustrations are most important to tackle.
  • The “five whys” technique is applied to dig to root causes.

• Team Proposes Solutions — Not the Scrum Master:

  • Empowerment is key: team members, not the Scrum Master, propose and own solutions.
    • “The team, not you, not the Scrum Master...maybe you know what could be the solution, but don’t say, please don’t say. The opinion of the Scrum Master in a retrospect is out.” — Mariano [05:30]

• Action & Ownership:

  • Only 1–2 concrete actions are chosen, with one person responsible for monitoring progress.
  • Follow-up in the next retrospective is essential for accountability.

• Keeping Things Fresh:

  • Change format or themes (colors, sports motifs, etc.) to keep retrospectives engaging and avoid monotony.
    • “Maybe use the same process, right, but change the colors or the themes...” — Mariano [06:43]

---

2. The True Mark of Scrum Master Success

[07:22–11:12]

• Early Views of Success:

  • Mariano initially equated success with classic project management metrics (on-time, on-budget delivery, velocity).

• Evolved Perspective:

  • True success: when the team is self-managing, solves its own problems, and no longer needs the Scrum Master’s direct intervention.
    • “A successful team is one that manages itself, can solve its own problem. When they don’t need a Scrum Master to help them—that is the meaning of success.” — Mariano [08:37]
    • “The team don’t need me to tell them what to do. They know what to work on in daily. Sometimes I give the power of the retrospective to a team and it was wonderful...” — Mariano [09:25]
  • Psychological safety is essential: no fear in criticizing constructively or appreciating others.
    • “The team needs psychological safety. There is no fear of criticizing or appreciating; they feel strong together.” — Mariano [09:46]
  • Success includes sustainable, proactive, continuous improvement — not just technical fixes, but team-level problem-solving.
  • While delivery metrics matter, engagement and collaboration go beyond mere productivity numbers.

• Host’s Affirmation:

  • Vasco reframes: The goal is team empowerment and confidence — not absence of the Scrum Master, but the team’s ability to act independently.
    • “I would say differently: it’s when the team is empowered and self confident that they can do the work...when a team is confident and can resolve the issues they face, then the Scrum Master is free to concentrate on other aspects...” — Vasco [11:34]

---

Notable Quotes & Memorable Moments

• “Retrospective is the heart of continuous improvement.” — Mariano [01:36]

• “The opinion of the Scrum Master in a retrospect is out...Please, this is important.” — Mariano [05:30]

• “A successful team is one that manages itself, can solve its own problem. When they don’t need a Scrum Master to help them — that is the meaning of success.” — Mariano [08:37]

• “The team needs psychological safety. There is no fear of criticizing or appreciating; they feel strong together.” — Mariano [09:46]

• “When a team is confident and can resolve the issues they face on their own, then the Scrum Master is free to concentrate on the other aspects...” — Vasco [11:34]

---

Important Segment Timestamps

• [01:23] Mariano introduces his retrospective format
• [03:01] Importance of feelings and catharsis in retrospectives
• [05:30] The Scrum Master’s role: facilitator, not solution provider
• [06:43] Keeping retrospectives fresh and engaging
• [07:54] Mariano’s evolving definition of success
• [08:37] Self-management as the marker of team and Scrum Master success
• [09:46] Importance of psychological safety
• [11:34] Vasco’s synthesis on empowerment and the Scrum Master’s evolving role

---

Summary

This episode offers actionable advice on fostering psychological safety and team empowerment as the foundation for high performance in Agile teams. Mariano Gontcher advocates for retrospectives centered on emotional honesty and collective ownership, and describes the ultimate Scrum Master achievement: teams so empowered, they no longer rely on the Scrum Master for daily guidance. The conversation’s practical tips and reflective tone make it a must-listen for anyone striving to raise their Agile team’s performance and trust.

Transcript

[A]

Hey there agile adventurer. Just a quick question. What if for the price of 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 Thursday the big question of the week. Today, the success question will be answered by our guest Mariano Gonciar. Hey Mariano, welcome back.

[C]

Hello everybody.

[B]

So success is the big question of the week. Of course. But before we dive into that, Mariano, share with us what is your favorite agile retrospective format and why?

[C]

First I need to say something that retrospective is a heart of continuous improvement. While there are many formats, my favorite is one I call from frustration to action. I did it from the various dynamics during my time at telecom group. I remember that at the beginning my teams retrospectively used the boring the boat, what were wrong, what to improve. And we always go to the same perfect answer, right? That's when I decide to change the dynamic. I want people to feel more comfortable and honest. Well, first of all is catharsis the frustration box. Instead of generic question, I ask each team member to anonymously write in a sticky note their biggest frustration from the sprint. If you remember my story about the I happened when I told that about the frustration and what is the army of fear? Well, it's like that. Not say what happened in that sprint, the last sprint. Just say what is the biggest frustration in the sprint. It's different. Maybe little, but it's important. Can be big or small. But it's a frustration that something feel during the sprint. It's important the fields because it's not information. You feel bad. Good. Okay. And then I put all the sticky notes in a board with a group divide by team. This allow the team to see that frustration aren't unique. Maybe you have a frustration but never say during the retrospective and the other people next to have the same frustration. It's real. But it happens when you finish to group them. Analyze and voting. Right. We analyze which is the nodes in the group and voting what is the best or the most important to solve. You can use five way technical to get a root of the problem. Why and why and why. I don't know if they know, but it's wonderful. And next step, the action. The contract. Right. The last step is crucial. Once we identify the root cause the team proposed solution. The team, not you, not the Scrum Master. The team that is important. Maybe you know what is or what could be the solution. But don't say, please don't say. Don't try to say your opinion. The opinion in Scrum Master in a retrospect is out. I know that I like to say, come on, do that. You know. But you need to say that they need to say, not you. Right. Please. This is important. Then when we finish this idea, we choose one or two concrete actions and assign a responsibility person. Maybe this person don't do the action. They need to do all the action. But is responsibility to continuous understand what happened with this action. If it's working, if not working. If need something else. I don't know. But it's important to have one or two not more concrete actions. Please. Because if you have many contract action, maybe don't can do it during the sprint or during the days. Right. And try continuous focuses on that action in the next retrospective. Again, say okay, what happened with that action or what happened during the spin. During the spin about this action. It's important to continue focusing on that action that all the team compromise. Right. And an extra tip it is just to know. Try to change the format or maybe the colors. Or maybe if you know the team. Oh, maybe one day was. I don't know formula one another day football. Trying to change the view about the retrospective. Because they don't feel that you are doing again and again. Maybe use the same process. Right. But change the colors or the themes about the retrospective.

[B]

Yeah, that's really. Let's say people centric discussion of a retrospective. And it really helps people express themselves. I really like how you start by. I mean you talked about it already a few times. Like empathizing through helping people describe their frustrations.

[C]

Right? Right.

[B]

And then stepping back and then letting the team take over the resolution. Right. Like take the ownership and make sure that things happen. So. But of course that was the retro. We run these retros because we want the teams to be Successful. And we want ourselves to be successful as well. Mariano. So share with us. When you think about yourself as a Scrum Master, what does success mean for you?

[C]

Okay, I start with the story. At first, when I was a newly certified of Scrum Master, my definition of success was very, very simple. Delivery, depression on the time budget. Right. I told you, I understand. I died in 2007. But during the years my perception changed because I am transformation in a pm. But when I start to work with like a Scrum Master, officially my definition of success changed. Not the delivery, the project of on time and budget. Or maybe the velocity, the best velocity. About the team. A success team is one of them. Management itself can solve its own problem. When they don't need a Scrum Master to help them. That is the middle succession. When I'm searching job well, this is bad for me. Is the succession one the team is. I don't know, it's grow, it's independent. They need self management. Right. The team don't need me to tell them what to do. They know what to work on in daily. Maybe I think instead of retrospective, I sometimes I give the powerful about the retrospective to a team and it was wonderful because the team understand what is the concept and it is great. It's like a patient in the doctor that say it's good, come on, go to the real life. I don't know. This is for me. The team needs psychological safety. There is no fear of criticizing or I don't know, appreciating, incompetent. They feel strong together. Obviously effective collaboration and communication. Not just with the team, outside the team. Right. And one part that is important, sustainability, continuous improvement. The team proactively defy problems. Not about the technical things, you know about problems in the team and try to do something to solve them. Right. Obviously the velocity is important because you need to do the work. Right. But if you get a team where the people are working together, you have more than a delivery. You have people that are engagement and the team and the productivity.

[B]

Absolutely. There's quite a lot of aspects. But one of those that I really appreciate you bringing up is this idea that the mark of a successful Scrum Master is when the team takes ownership. And if I turn that around, I mean we often say, oh, it's when the team doesn't need the Scrum Master. I would say differently. I would say it's when the team is empowered and self confident that they can do the work. And of course the Scrum Master can always make that better. You know, let's not forget that the team is focused on delivering things all the time. But the Scrum Master also understands the wider system, right? Like relationship with other teams, relationship with the product owner and et cetera. There's a lot of other things that go into it, but when a team is confident and can resolve the issues they face on their own, then the Scrum Master is free to concentrate on the other aspects that help the team deliver faster, higher quality, and collaborate better with others and stakeholders around them. So thank you for sharing that with us.

[C]

Mariano welcome. Thank you to you Vasco. The opportunity to do that.

[A]

All right, 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 to 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 to 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 Slack we really hope you liked our show.

[B]

And if you did, why not rate.

[A]

This podcast on Stitcher or itunes, Share.

[B]

This podcast and let other Scrum Masters.

[A]

Know about this valuable resource for their work.

[B]

Remember that sharing is caring.