How I helped developers talk about feelings and needs
summary
A cross‑functional, mostly remote team runs a three-hour remote workshop after one-on-ones reveal simmering clashes; the facilitator uses rules of engagement, check‑ins, explicit definitions of feelings versus needs, thinking time and silence to surface misunderstandings. Outcomes: a concrete team agreement including a policy on what kind of AI to use, a commitment to a weekly one-hour coffee for connection, and the habit of reading an agreement item each daily standup. Two people later leave but the team keeps collaborating.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:12Why feelings are hard
- 7:57Teams and psychological safety
- 11:10Case study team in crisis
- 21:53Workshop rules
- 31:24Breakthrough in workshop
- 36:00Misunderstandings and agreements
- 41:35Handling conflicts
- 43:01Power of listening
- 47:21Prime directive for collaboration
- 50:09Practical techniques
- 51:53Feelings and needs at work
- 52:37Final thoughts
related talks
28mBuilding bridges beyond the screen: Cracking the code of remote team-building
01h 18mLeading teams to collaborate-when they really don't want to.
24mKeep talking and no-one explodes – Tips for smooth teams
59mEmpowering Soft Skills with Team Dynamics/Communication Skills
37mFixing the mistakes we -all- make as developers, leaders and teams
01h 20mWorkshop - Teamwork Ain't Always Easy
40mClosing Keynote
46mCracking the cadence of your software engineering 1:1s