The Remote Team Scheduling Guide
Practical, opinionated writing on how distributed teams plan their week, run their meetings, hand off across time zones and keep their calendars from quietly burning people out.
Foundations
Remote team scheduling fundamentals: a field guide for distributed managers
The core ideas every distributed manager should internalise before they touch a calendar invite — anchored teams, follow-the-sun, async-by-default, and the cost of every synchronous meeting that crosses a coastline.
Foundations · 11 min readFollow-the-sun vs anchored overlap: choosing the right shape for your remote team
Most distributed teams default to "everyone joins one all-hands" without realising that the underlying scheduling shape is a strategic choice. We compare the two dominant models and the kinds of work each one supports.
Operations
Designing a fair meeting rotation when no single time works for everyone
When your team spans three or more continents, no single weekly slot is fair to everyone. A documented rotation, applied honestly, is the difference between a team that scales and a team that quietly resents whoever runs the calendar.
Operations · 10 min readStandup times across three continents: what actually works
A practical breakdown of the standup patterns we have seen succeed in teams spanning the Americas, Europe and Asia — and the patterns that look elegant on paper but quietly burn the team out.
Operations · 11 min readOn-call handoffs around the clock: building a follow-the-sun rotation that actually hands off
A 24-hour on-call rotation is only as strong as its handoff. We walk through the structure, the documentation conventions and the calendar mechanics that make follow-the-sun on-call sustainable.
Time zones
Daylight saving survival guide for international teams
Twice a year, an hour quietly disappears or appears in your team calendar. If your scheduling tools and your team conventions are not built to handle it, you will lose at least one important meeting per transition.
Time zones · 7 min readIANA zones vs UTC offsets: why the difference matters in practice
Treating "UTC+1" and "Europe/Berlin" as interchangeable is one of the most common bugs in scheduling tools. We explain why the IANA database is the only correct way to store and reason about time zones.
People
Process
Async-first decision making: the document, not the meeting, is the unit of work
When a global team treats its written documents — not its meetings — as the place where decisions actually happen, the calendar gets dramatically lighter and the work gets dramatically clearer.
Process · 6 min readOffice hours: the most underrated tool for distributed teams
Office hours are the simplest, lowest-cost tool for letting a distributed team get unstuck without scheduling a one-off meeting for every question. We cover the pattern and the failure modes.