Player FM 앱으로 오프라인으로 전환하세요!
Patterns in Agile Teams that Destroy Vulnerability with Alba Uribe, Quincy Jordan, and Justin Thatil
저장한 시리즈 ("피드 비활성화" status)
When? This feed was archived on September 27, 2025 20:13 (). Last successful fetch was on November 28, 2024 15:27 ()
Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 321875130 series 2481978
This week, Dan Neumann is joined by three colleagues Alba Uribe, Quincy Jordan, and Justin Thatil, to have a second conversation about vulnerability, especially about the patterns Teams can fall into that are a threat to vulnerability and the overall safety of the work environment.
In this episode, they explore these dangerous antipatterns and how to prevent them.
Key Takeaways
- Avoiding the Antipatterns:
-
- If you “Bring your whole self to work” you are able to be vulnerable and propose ideas.
- If you are making promises you can’t keep, people won’t feel trustful of the environment anymore. Trust and transparency need to be built into Teams in order for them to be effective.
- Remote work presents challenges to building relationships that can foster vulnerability.
- How does a Scrum Master create an environment for people to allow themselves to be vulnerable?
-
- A Scrum Master can show his/her own vulnerability in order to model the behavior to others (asking questions, making sure the camera is on in video calls).
- Setting up a safe environment can require collaborating or setting expectations with those who are not on the team about the environment.
- Vulnerability requires a lot of emotion, allowing yourself to feel and connect with others.
- Assessing the root cause of a negative emotion that can arise as a result of the process is needed in order to prevent its repetition.
-
- Being neutral only exacerbates the problem instead of seeking a potential solution.
- Know the Team Agreements or Rules of Engagement: How are we going to interact? What are we going to do when we have differences?
- Activities that numb vulnerability are a pattern to avoid.
-
- Highlighting weaknesses promote a sense of fear and unsafety.
- When some individuals disregard others’ ideas, vulnerability is at risk.
- All questions are good questions! Promoting open communication is the best way of encouraging vulnerability.
- A certain level of emotional intelligence is required to promote more human connection.
- Unhealthy comparisons are vulnerability destroyers.
-
- Don’t compare Teams’ performance, it is just not effective.
- Looking back to a different Team composition and comparing past results to today’s is not useful.
- Favoritism is also an antipattern.
Mentioned in this Episode:
Listen to Ep. 171: Fostering Vulnerability in Agile Teams
Positive Intelligence: Why Only 20% of Teams and Individuals Achieve Their True Potential and How You Can Achieve Yours, by Shirzad Chamine
Want to Learn More or Get in Touch?
Visit the website and catch up with all the episodes on AgileThought.com!
Email your thoughts or suggestions to [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!
332 에피소드
Patterns in Agile Teams that Destroy Vulnerability with Alba Uribe, Quincy Jordan, and Justin Thatil
저장한 시리즈 ("피드 비활성화" status)
When? This feed was archived on September 27, 2025 20:13 (). Last successful fetch was on November 28, 2024 15:27 ()
Why? 피드 비활성화 status. 잠시 서버에 문제가 발생해 팟캐스트를 불러오지 못합니다.
What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.
Manage episode 321875130 series 2481978
This week, Dan Neumann is joined by three colleagues Alba Uribe, Quincy Jordan, and Justin Thatil, to have a second conversation about vulnerability, especially about the patterns Teams can fall into that are a threat to vulnerability and the overall safety of the work environment.
In this episode, they explore these dangerous antipatterns and how to prevent them.
Key Takeaways
- Avoiding the Antipatterns:
-
- If you “Bring your whole self to work” you are able to be vulnerable and propose ideas.
- If you are making promises you can’t keep, people won’t feel trustful of the environment anymore. Trust and transparency need to be built into Teams in order for them to be effective.
- Remote work presents challenges to building relationships that can foster vulnerability.
- How does a Scrum Master create an environment for people to allow themselves to be vulnerable?
-
- A Scrum Master can show his/her own vulnerability in order to model the behavior to others (asking questions, making sure the camera is on in video calls).
- Setting up a safe environment can require collaborating or setting expectations with those who are not on the team about the environment.
- Vulnerability requires a lot of emotion, allowing yourself to feel and connect with others.
- Assessing the root cause of a negative emotion that can arise as a result of the process is needed in order to prevent its repetition.
-
- Being neutral only exacerbates the problem instead of seeking a potential solution.
- Know the Team Agreements or Rules of Engagement: How are we going to interact? What are we going to do when we have differences?
- Activities that numb vulnerability are a pattern to avoid.
-
- Highlighting weaknesses promote a sense of fear and unsafety.
- When some individuals disregard others’ ideas, vulnerability is at risk.
- All questions are good questions! Promoting open communication is the best way of encouraging vulnerability.
- A certain level of emotional intelligence is required to promote more human connection.
- Unhealthy comparisons are vulnerability destroyers.
-
- Don’t compare Teams’ performance, it is just not effective.
- Looking back to a different Team composition and comparing past results to today’s is not useful.
- Favoritism is also an antipattern.
Mentioned in this Episode:
Listen to Ep. 171: Fostering Vulnerability in Agile Teams
Positive Intelligence: Why Only 20% of Teams and Individuals Achieve Their True Potential and How You Can Achieve Yours, by Shirzad Chamine
Want to Learn More or Get in Touch?
Visit the website and catch up with all the episodes on AgileThought.com!
Email your thoughts or suggestions to [email protected] or Tweet @AgileThought using #AgileThoughtPodcast!
332 에피소드
All episodes
×플레이어 FM에 오신것을 환영합니다!
플레이어 FM은 웹에서 고품질 팟캐스트를 검색하여 지금 바로 즐길 수 있도록 합니다. 최고의 팟캐스트 앱이며 Android, iPhone 및 웹에서도 작동합니다. 장치 간 구독 동기화를 위해 가입하세요.