Managing diverse engineers for high-impact deliveries
summary
Teams adopt an async-first culture with Jira action lines that include time zones (e g Confluent CFKA at 1600 CCT), use Slack Donut for random coffee pairings, and rotate meeting facilitators across hubs. A critical bug slips through two sprints until a rule makes every high‑impact task have an explicit owner assigned (Alice fixes bug by Wednesday, Leo updates stakeholders). One blunt review is resolved by a single one‑on‑one call, ownership clarity and psychological safety measurably reduce clashes and improve follow‑through.
AI-written summary · about
chapters (8)
- 0:00Managing global teams
- 2:10Communication in distributed teams
- 7:14Accountability without micromanagement
- 10:54Psychological safety for collaboration
- 14:08Fighting distance-induced formality with intentional belonging
- 18:40Inclusive remote onboarding
- 20:08Celebrating global contributions
- 21:35Conclusion and key takeaways for global team leadership
related talks
52mToo many cooks! Supporting augmented teams without getting salty
10mManaging across timezones; A retrospective
47mAgile experience in changing environments and the challenges faced
18mAgile leadership and technical mastery, a harmonious alliance
43mScaling Yourself for Managing Distributed Teams...
40mThe Joys of Managing Engineering Teams
32mPanel discussion: The journey to building effective engineering teams
31mHarmonizing Across Product & Engineering (Cross Team Collab)