Working across timezones tips and tricks
summary
Company-wide remote work with an ~2-hour Paris–San Francisco overlap and ~80 people relies on heavy async communication: write very explicit messages on Slack/Teams, back them with documents in Google Drive/Notion, and use Loom for quick demos. Use a pre-change design doc to plan multi-PR refactors and avoid 60-comment PR reviews, keep a project launch checklist that lists impacted services and exactly how to toggle and rollback feature flags, record verbose meeting agendas and send clear notes. Expect occasional hour shifts and treat timezone handling as a team responsibility.
AI-written summary · about
chapters (11)
- 0:00Remote work across timezones
- 1:06Timezone overlap challenges
- 2:31Async communication in remote teams
- 5:59Documents for async discussions
- 7:26Project planning documents
- 9:34Meetings across timezones
- 11:45Missed meetings with async updates
- 13:11Work-life boundaries in remote roles
- 15:45Adapting to team changes
- 17:09Hour shifts for critical projects
- 18:20Q&A: Preventing team silos
related talks
10mManaging across timezones; A retrospective
27mLost on an Island: Building Remote Collaboration in Cross-Continent Distributed Teams
45mOptimizing remote work: Pull Requests, Stand-ups, and emojis with Kasey Kelly
33mTips for Managing a Widely Distributed Team
38mDistributed Sys Teams
27m"Thriving in a Connected World"
26mRemote-first teams work better
23mManaging diverse engineers for high-impact deliveries