Beyond Code: Building trust in multinational and (not only) remote teams
summary
Compares psychological safety vs performance using Edmondson’s four-zone matrix (apathy, anxiety, comfort, learning) and shows that teams with high safety plus high standards become the only reliably innovative ones. Uses a Simon anecdote where a remote team measures a new multi-tool, accepts it, and ships it, while an on-site team dismisses the same idea—reducing future contributions. Recommends concrete practices: document decisions and agree on language, use Slack/Teams statuses, weekly lunches or coffee rituals, treat mistakes as learning and measure proposals before rejecting.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 1:12Remote vs on-site team dynamics
- 7:20Psychological safety explained
- 11:58Building trust in teams
- 13:22Remote practices for on-site teams
- 14:26Conclusion and key takeaway
related talks
36mPsychological Safety: Building fearless teams
56mBuilding Trust in Teams
27mFostering psychological safety in distributed teams
22mUnleash Your Team's Potential Through The 4 Stages Of Psychological Safety
34mDiverse Leaders in Tech - Psychological Safety: Building Trust, Accountability, and Inclusion
22mPsychological safety: How to become a team that learns
15mInfusing Psychological Safety into Your Teams
46mThe risks of performative psychological safety