Cross-Timezone Team Workflow

Design our cross-timezone workflow. The spread: {{team_zones}} (who's where, the overlap window honestly, what currently requires sync that shouldn't, the friction: {{friction}}). Build: the overlap-hours budget (the precious shared hours reserved for what NEEDS them: decisions, debate, connection — never status; the recurring-meeting audit against this rule), the async-first defaults (decisions proposed in writing with respond-by times, the recorded walkthrough instead of the explain-it meeting, the meeting-only-if a decision stalls twice async), the handoff pattern if work flows across zones (the end-of-day handoff note format: state, next action, blockers — the relay-race discipline), the timezone fairness rotation (the painful meeting slot shared, not permanently assigned to the smallest office), the response-time norms by channel (what expects same-hour vs same-day vs whenever — stated, so nobody's anxious at 9pm), and the connection budget: the deliberate non-work rituals that survive distance, because async-efficient teams quietly starve without them.

Run this prompt with your real data

This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.

More Operations prompts