Temporal Inconvenience Rotation

Definition

Virtual teams spanning multiple time zones face the unavoidable constraint that no single meeting time is convenient for everyone. Rather than scheduling regular meetings at times that consistently inconvenience the same people (who always get early mornings or late nights), distributed teams should rotate meeting times so the burden of inconvenience is shared equitably across the team.

In the Book

Chapter 2 explicitly recommends: "When scheduling conference calls, rotate the time so that no one always has to get up early or stay up late to participate." This is framed as part of "being considerate" to distributed team members. The book notes that managers should "incorporate national and religious holidays, as well as vacations, in your project planning," showing that consideration for temporal constraints is part of team culture building.

Chapter 4 reinforces this during meeting planning: "When scheduling a meeting, keep in mind the time zones of your attendees. If you have to schedule regular meetings across multiple time zones, try to share the inconvenience across your team rather than always have the same person meeting before breakfast or late in the evening." The book also notes the complexity of daylight saving time changes, where a three-hour difference might shift to two hours between summer and winter, making static schedules problematic.

Why It Matters

This concept recognizes that time zones create real physical burden on team members (sleep disruption, schedule conflicts with local responsibilities) and addresses a common failure mode where distributed teams unconsciously privilege people in one time zone. By explicitly rotating the inconvenience, teams signal fairness and avoid the resentment that builds when some members consistently sacrifice sleep or personal time. It also prevents the informal hierarchy where "the people in the boss's time zone" get better treatment, which undermines trust in distributed teams.