Feb 18, 2022
This week, Dan Neumann is joined
by three of his colleagues
Quincy Jordan, and Justin Thatil. In
today’s episode, they are exploring the concept of vulnerability as
it is introduced by Brené
Brown and its meaning for Scrum Masters and Agile Coaches who are
seeking to foster a safe environment where vulnerability is
welcomed and celebrated.
- What is vulnerability?
- According to Brené Brown, vulnerability is the emotional experience
during times of uncertainty, risk, and emotional
- Vulnerability is related to having courage
regardless of the circumstances.
- There are different phases of vulnerability: on
an individual and a collective level.
- You succeed and fail as a team; it is not about
each person’s performance but the collective execution.
- Teams need to trust and work together as a
unit, as a collective.
- What techniques can a Scrum Master use when
having a new team and trying to create some of the safety that can
- A Scrum Master should first show and model
vulnerability and then ask the team what they need in order to feel
- To establish safety.
- To open up to team members about the importance
of fostering vulnerability.
- A team has to be aware of the responsibility
implied in fostering a safe environment where vulnerability can
- Human connection is the catalyst to establish
- Myths about vulnerability:
- Vulnerability is disclosure: There have to be
boundaries to what you share; vulnerability shows that there is
trust and safety about what is appropriate to share at the right
- Vulnerability is weakness.
- Techniques to encourage
- Intentionally expose your troubles for others
to see that you are willing to be transparent; vulnerability is
- Establish what is OK in the team
Mentioned in this Episode:
The Seat of the
Soul, by Gary
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 Podcast@AgileThought.com
or Tweet @AgileThought using