Scaling Yourself for Managing Distributed Teams...
summary
Distributed SREs span three geographies and 18 engineers supporting JIRA and Confluence, and rapid growth creates friction, duplication and cost. Practical fixes include a 33-question Tuckman survey to surface team stage and a DESI decision artifact (Driver/Approver/Contributor/Informed) to force async participation; experiments like a Keep Talking and Nobody Explodes games night build cohesion; mandatory per-sprint cross-site demos increase velocity; one-region lead runs a quarter-long pilot to prove outcomes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:59What is my distributed team
- 1:44What are distributed teams
- 9:56Inspire
- 16:34Survey
- 24:05Planning
- 30:51Listening
- 40:33Summary
related talks
37mBuilding & Scaling Distributed Teams
33mTips for Managing a Widely Distributed Team
23mManaging diverse engineers for high-impact deliveries
46mLeading Distributed Teams
13mManaging Remote Teams
21mScaling Distributed Teams
43mCommunication Strategies for scaled and distributed teams
38mDistributed Sys Teams