Quarterly Planning for Distributed Teams

Last January a company I advised tried to plan its whole first quarter in a single day. One video call, nine hours, "so everyone's aligned." The product lead in Lisbon started at 2pm and was fading by ten. The two engineers in Manila joined near 10pm and gave up around one in the morning, having said maybe four sentences between them in the last stretch. By the time the folks on the US west coast were warmed up and genuinely arguing about roadmap tradeoffs, half the company had either logged off or stopped forming complete thoughts. They ended the day with a deck nobody quite believed in and a quarter that got quietly re-planned in Slack over the following three weeks anyway.

The opposite mistake is just as common and harder to spot. Another team, scarred by exactly that kind of marathon, swung the other way and ran planning entirely in threads. No big call. All async, all the time. It never ended. Their Q2 plan was still being "finalized" in late May, by which point it wasn't a plan, it was a diary of things that had already happened.

Planning is the hardest thing a distributed team does. Harder than standups, harder than handoffs, harder than any of the daily rituals people write guides about. It's the one process that genuinely needs a lot of people's real thinking pointed at the same questions in a compressed window, and a wide timezone gap is precisely the thing that makes a compressed shared window impossible. So teams reach for one of two bad shapes: cram it into a call that punishes half the company, or let it dissolve into a process with no edges. Both produce a plan nobody owns.

Why planning breaks worse than everything else

Most distributed-team advice is about lowering the bandwidth a task needs so it survives being spread out. Write the update down. Turn the meeting into a doc. Handle it in a thread. That works because most work is lower-bandwidth than we pretend.

Planning resists it. A quarter's plan is a pile of interlocking judgment calls, and the calls depend on each other. What sales commits to depends on what engineering can build, which depends on what got cut, which depends on what leadership decided actually matters this quarter. You can't cleanly slice that into independent async tasks, because the whole point is the interaction between the pieces. This is the same compounding you see in a cross-functional project where the delay lives in the boundaries between people, except now every boundary is live at once and every answer changes three other questions.

So the instinct to solve it with one big meeting isn't stupid. It's just badly aimed. The meeting tries to do everything at the same time: surface the context, generate the options, debate the tradeoffs, and lock the decisions, all in one exhausted nine-hour block where the people furthest from headquarters are least able to contribute. You spend your scarcest resource, real overlap between tired people, on the parts of planning that never needed to be live in the first place.

Stop treating planning as an event

The move that fixes this is to stop thinking of planning as a meeting and start thinking of it as a process with distinct phases, most of which don't need everyone awake together. Planning secretly has four jobs stuffed into that one call: assembling the inputs, generating options, resolving the genuine disagreements, and committing to a plan. Only one of those actually benefits from live time. The rest are better done async, and forcing them into the call is what makes the call so long and so bad.

Pull them apart and you get a shape that runs over a bounded stretch, say two weeks, with exactly one small live session in the middle instead of one giant one. Here's what each phase looks like when you build it for a team that's never all awake at once.

Gather the inputs before anyone argues

The first week is homework, and it's all written. Everyone who's going to shape the plan writes down what they're bringing into it before any discussion starts. What shipped last quarter and what didn't. The numbers. The customer signals. The constraints they already know about. The two or three things they think the team should prioritize, and why.

The reason to do this in writing, ahead of time, isn't just timezone logistics. It's that reading a colleague's reasoning in full beats hearing a compressed version of it over a call where the loudest and most awake person sets the frame. This is the same reason written brainstorming beats a live idea session: people think better before they've heard the room, not after. When the engineer in Manila writes her case for paying down a specific piece of tech debt, and everyone reads it on their own morning, it competes on merit instead of on who happened to be alert during the one hour it came up.

By the end of this phase you should have a single shared document that any participant could read cold and understand what the quarter is choosing between. If that doc doesn't exist yet, you are not ready for a live conversation, and holding one anyway just means talking in circles.

Spend the live hour on disagreement, not information

Now, and only now, do you get everyone together, and you keep it short. Ninety minutes, maybe two hours. Not because you're being kind, though you are, but because if the homework is done there is genuinely not nine hours of live work left.

The live session has one job: the real disagreements. The tradeoffs where smart people who read the same doc still landed in different places. Those need voices, tone, the back-and-forth of "wait, say more about that," the reading of the room that a thread can't carry. Everything that isn't a live disagreement, the status recaps, the context-setting, the stuff already settled in the doc, gets cut from the agenda ruthlessly, because it's the padding that turned the original marathon into a marathon.

Because this is the one piece you're protecting as synchronous, you owe it the same fairness as any meeting you make people cross a timezone for: pick the slot that spreads the pain, don't park it forever on the same far-flung person, and if a genuinely zero-overlap team can't find even ninety shared minutes, resolve the disagreements in a tight written exchange with a hard deadline instead of pretending a 3am call counts as participation. If your company already runs an occasional in-person offsite, this live strategic argument is exactly the kind of thing the offsite exists for, and it's a far better use of that rare room than the roadmap slides you could have sent ahead.

Converge with a decider, not a vote

A disagreement aired is not a decision made, and this is where planning most often dies. The call ends on a good note, everyone feels heard, and then nothing is actually chosen, so the "plan" drifts back into Slack and re-litigates itself for a month.

Name a decider for each contested call before the live session, and have them close it in writing within a day of the conversation. Not a vote, not consensus, one accountable person who takes the input and commits. This is the async decision ritual applied to the biggest decisions on the calendar: proposal, input, deadline, a named person who decides, and then disagree-and-commit from everyone else. The discipline that feels almost rude in the moment, one person saying "I've heard it, here's the call," is the only thing that reliably converts a lively planning discussion into a plan that exists.

Write the plan for the person who wasn't there

The output of all this is a document, and it has to stand on its own, because on a distributed team someone always missed the live session, and next quarter someone new will read this to understand what you committed to and why. Write it for the reader who wasn't in the room: what you're doing this quarter, what you decided not to do, who owns each thing, and the dates written as real dates in a named timezone rather than a vague "end of Q1." A plan that only makes sense to the people who were on the call is a plan with a sleep schedule attached, useless to anyone whose day started after it ended.

Get this rhythm right and quarterly planning stops being the thing everyone dreads. Most of the work happens on each person's own clock, the one live hour is short and pointed and actually worth attending, and you come out the other side with a plan people can point to instead of a memory of a very long call that a third of the company slept through.

Keep the Dates in Your Plan Honest

A quarter's plan is full of deadlines, and every one of them means a different moment to whoever reads it. Timely converts every time and date mentioned in Slack into each person's own local zone automatically, so when your plan says "design locked by 5pm Friday ET," the engineer in Manila reads it as the exact moment you meant instead of guessing which Friday and whose 5pm. One less way for a carefully made plan to quietly go wrong.

Add Timely to Slack — Free · See how it works