Lost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
summary
Distributed teams across 12 time zones find only a one-hour global overlap most days, so the team enforces calendars with personal busy slots, documents nightly priorities documents for the handoff, and uses Slack channels per project, JIRA for tickets, GoToMeeting for large calls, and Google Drive/GitHub for artifacts. Daylight‑savings mismatches cause real calendar chaos, but these rules plus regular video check‑ins and occasional in‑person meetups produce measurable continuity: fewer missed handoffs and repeat client engagements lasting 4–5 years.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:52Be Aware
- 3:11Be Organized
- 4:46Be Transparent
- 8:28Be Flexible
- 9:52Be Curious
- 12:53Be Humble
- 16:50Be Vulnerable
related talks
40mSetting up your Distributed (Global) Community Team for Success!
47mExtreme Remoting
13mManaging Remote Teams
33mTips for Managing a Widely Distributed Team
36mHow YOUR scrum team can excel in a remote setting
37mBuilding & Scaling Distributed Teams
26mRemote-first teams work better
38mDistributed Sys Teams