How to run quarterly planning with a remote team
Quarterly planning is where a team decides what it will spend the next three months on, and just as important, what it will not. The output is a short list of goals, each with an owner and a way to tell whether it happened.
On a remote team the planning itself usually goes fine. The trouble is everything around it: proposals scattered across docs, a marathon call that ends with half the decisions unspoken, and a plan nobody can find by week three. Run it in one place instead. One channel for the quarter, one thread per proposed goal, walk-in voice rooms for the trade-offs, and the final plan pinned where the team already works.
The usual way
Remote quarterly planning often looks like this.
- The doc pile. Every lead writes a proposal in a separate doc. Comments land in five places.
- The marathon call. Three hours, twelve people, and the loudest proposal wins.
- The quiet cuts. Something gets dropped on the call, and the person who proposed it hears about it a month later.
- The lost plan. The final list lives in a slide deck. By mid-quarter nobody remembers where.
A format for a distributed team
1. Open one channel for the quarter
Make a channel named for the quarter and post one message at the top. Same shape every time.
- Deadline: when proposals close and when the plan is final.
- Shape: what a proposal needs, in three lines.
- Capacity: how many goals the team can carry, roughly.
- Owner: who makes the final call when the team cannot agree.
Pin it. That pin answers most of the first week's questions.
2. One thread per proposed goal
Anyone proposing a goal posts it as a new message in the channel, in three lines:
- The goal. One sentence on what will be true at the end of the quarter.
- Why now. What it unlocks, or what it costs to wait.
- What it needs. People, time, and anything from another team.
Questions, objections, and support go in that thread. By the deadline, each thread is a complete record of one proposal and the case for and against it.
3. Read before anyone talks
Give the team a few days to read every thread and reply asynchronously. People in other time zones get the same say as people who are online at the meeting hour.
Ask everyone to react to each proposal with one of three signals: must do, nice to have, not this quarter. The pattern is a starting point, not a vote.
4. Settle the trade-offs in walk-in voice rooms
Most proposals need no live discussion. The few that conflict, or that compete for the same people, do. Open a walk-in voice room for each contested trade-off and post the time in its thread.
Only the people with a stake need to come. Anyone else can walk in to listen and walk out again. That keeps each conversation short and keeps the one big call off the calendar.
5. Post the plan, and the cuts
When the owner decides, post the plan as one message in the channel:
- The goals. Each one with an owner and how the team will know it happened.
- The cuts. Each dropped proposal, with one line on why.
Then reply in every proposal thread with its outcome. Nobody finds out a month later. Pin the plan next to the original announcement.
Keep it alive through the quarter
- Check in monthly. Post "Month one" in the channel. Each owner replies with one line: on track, at risk, or done.
- Change the plan in the open. When a goal changes, edit nothing quietly. Post the change and the reason, the same way a decision log works.
- Archive, do not delete. Next quarter starts with a new channel. The old one stays searchable, so last quarter's reasoning is one search away.
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster. A quarter's planning can live in one channel, from the first proposal to the last check-in.
Every proposal is a thread. The case for each goal, the questions, and the outcome stay together.
Trade-offs happen in walk-in voice rooms. The rooms sit beside the channel, so joining a conversation is a click, not an invite.
Wren writes the notes. Wren is an AI helper. In a walk-in voice room, Wren posts notes and action items back to the channel the room belongs to, so the reasoning behind a trade-off lands next to the proposal it was about.
Scout finds last quarter's reasoning. Scout is an AI helper on the same roster. Mention Scout and ask why a goal was cut last quarter. Scout answers from what was said and links the message it came from.
Nix keeps the check-ins on time. Mention Nix in the channel and ask for a reminder on the first of each month. The reminder arrives in the channel on the day. How to keep track of follow-ups in team chat covers the details.
Try it this quarter
Make a channel for next quarter and pin the four-line announcement above.