The Async-First Quarterly Planning Playbook for Distributed Teams

Quarterly planning was invented for teams that all worked in the same office. You blocked off Wednesday and Thursday, ordered lunch in, and ran a whiteboard for two days. By Friday you had OKRs.

When your team is in San Francisco, London, Bangalore, and Sydney, that format is a disaster. There is no two-day window where everyone is awake. The "compromise" of an 8-hour Zoom marathon at 11 PM Bangalore time produces worse decisions than a normal Tuesday and burns out half the team going into the new quarter.

The fix is not to find a better window. The fix is to stop trying to do planning live, and design the whole cycle around writing.

Why the classic offsite breaks across time zones

Three reasons the live offsite fails for distributed teams:

It excludes someone. Either APAC stays up until 2 AM, or SF starts at 5 AM, or someone gets recordings. None of these is the same as being in the room.
It compresses thinking into talking. The best planning insights come from someone reading a doc on Monday and realizing on Wednesday that the third bullet is wrong. A live offsite skips Wednesday.
It rewards the loud. In a 30-person Zoom across 3 time zones, the four most senior US voices dominate. The engineer in Bangalore who has the cleanest view of the technical risk has 90 seconds to make her case.

The async-first playbook fixes all three. It takes longer in calendar time (two weeks instead of two days) but less total person-time, and the output is better.

The two-week cadence

Here is the shape. Adjust durations to your team size; the structure holds.

Week	Day	Activity	Format
1	Mon	Inputs published	Async writing
1	Tue-Wed	Comments and questions on inputs	Async
1	Thu	Proposals from each team	Async writing
1	Fri	Cross-team comments on proposals	Async
2	Mon	Live review #1 (90 min)	Sync, two slots
2	Tue-Wed	Revised proposals	Async writing
2	Thu	Live review #2 (90 min)	Sync, two slots
2	Fri	Final OKRs published	Async writing

Two live meetings totaling three hours, both repeated in two zone-friendly slots so nobody is at 11 PM. Everything else happens in writing.

Week 1, Monday: publish the inputs

Leadership writes one document. Three sections, no more.

Where we are. Numbers from last quarter. What worked, what did not. Honestly.
Where we want to be. Two or three top-level outcomes for the next quarter, with rough success criteria.
Constraints. Headcount, budget, dependencies, anything that is not negotiable.

This is the hardest doc in the cycle to write because it forces leadership to make trade-offs explicit before the team weighs in. That is the point. Vague top-level direction produces vague team OKRs.

Publish this Monday morning in the zone where most of leadership lives. Anyone in APAC reads it on their Tuesday morning.

Week 1, Tuesday-Wednesday: open comments

Two days of structured async commenting. Two rules:

Comments are questions or counter-proposals, not vibes. "I disagree" is not a comment. "I disagree because Q2 numbers show X" is.
Leadership replies in writing within 24 hours. Every comment gets a response that either accepts the point, defers it, or explains why not.

By Wednesday end-of-day in the latest zone, leadership locks the doc. Late comments go to a parking lot for the next quarter.

Week 1, Thursday: each team writes a proposal

Each team writes one document with their proposed objectives and key results, mapped to the leadership inputs. This is also where teams flag dependencies on other teams.

The format that works: 1 page maximum per team. If a team needs more than one page to explain three objectives, they have not finished thinking.

Week 1, Friday: cross-team review

Every team reads every other team's proposal and leaves comments. This is where dependency conflicts surface. ("You said you need our data pipeline ready by week 4, but we have it scoped for week 8.") These conflicts are the entire point of cross-team review. They are also the conflicts that would have been invisible in a 30-person Zoom.

Friday is the right day for this because it gives APAC the weekend to read in their own time without working their evening, and US/Europe respond on Monday.

Week 2, Monday: live review #1

The first live meeting. Two slots, same agenda, run twice:

Slot A: 8:00 AM PT / 11:00 AM ET / 4:00 PM London / 8:30 PM Bangalore.
Slot B: 4:00 PM PT / 7:00 PM ET / midnight London / 4:30 AM Bangalore / 9:00 AM Sydney.

Slot A catches Americas, Europe, and India. Slot B catches Americas, late Europeans, and APAC. Most people only need to attend one. (See our best meeting times for US/India teams guide for the underlying overlap windows.)

The agenda is fixed. 90 minutes, no slack:

15 min: dependency conflicts surfaced last Friday.
30 min: the two or three highest-stakes trade-offs from the proposals.
30 min: open Q&A on anything still unclear.
15 min: what each team will revise this week.

This meeting is not for status updates. It is not for slide decks. It is for the conversations the comment threads cannot resolve.

Week 2, Tuesday-Wednesday: revisions

Each team revises their proposal based on the live review. Same async commenting rules.

This is the second-most-important window of the whole cycle, and it is silent. No meetings. Teams just write, and other teams read.

Week 2, Thursday: live review #2

Same two slots as Monday's review. Different agenda.

15 min: quick sign-off on revised proposals.
30 min: any remaining cross-team conflicts.
30 min: confirm the planning calendar for the quarter (kickoff dates, mid-quarter check-ins, retro).
15 min: explicit "what could still derail this" conversation.

If you cannot get to "no remaining conflicts" by the end of this meeting, something went wrong in the previous 10 days and you probably need an extra week. That is rare. Most cycles converge.

Week 2, Friday: final OKRs published

Leadership publishes a single doc that includes:

The final top-level outcomes (unchanged from week 1, ideally).
Each team's OKRs, in one place.
Dependencies, with owners.
Mid-quarter check-in dates.

This becomes the source of truth for the quarter. It is not a slide deck. It is a document the team can re-read in week 7 to remember what they signed up for.

Make the live windows visible

The live meetings only work if both slots are scheduled in zones where people are inside their humane working hours. The fastest way to verify this is to put your team on a Timezoners board, select the people who need to attend, and look at the green zones.

A common mistake: the team picks 8 AM PT for slot A because that is when SF prefers it, without noticing that lands at 8:30 PM Bangalore. The board makes the trade-off visible before you book the meeting, not after.

What to keep sync, what to move async

After running a few cycles, a clear pattern emerges. Some things have to be live, even across awkward time zones:

The two 90-minute reviews.
A 30-minute leadership-only call to lock the inputs in week 1.
Hard conflict-resolution conversations between two teams (rare, ad hoc).

Everything else is async by default:

Writing proposals.
Cross-team commenting.
Status updates.
Final OKR publication.
Mid-quarter check-ins (replace with written updates plus a 15-minute Loom).

The total live time across the whole cycle is around 4 hours per person. Compare that to a two-day offsite. Your team gets two days of their life back.

Where to go next

TL;DR

Replace the two-day offsite with a two-week async-first cycle.
Two 90-minute live reviews, each run in two zone-friendly slots.
Leadership publishes inputs in week 1, teams write proposals, cross-team review surfaces dependency conflicts.
Use a Timezoners board to pick the live slots so neither slot lands at 11 PM for a region.
Final OKRs are a written document, not a slide deck. Total live time per person across the whole cycle: about 4 hours.