How to run a virtual annual planning session that produces decisions, not just notes

A planning call drifts when nobody has said what it must produce. The agenda lists topics, such as the budget, hiring, and the product roadmap, and a topic is not a decision. Without an output named in advance, the conversation does what conversations do: it follows whoever talks most and ends when the time runs out.

Two other things make it worse online. Speaking order is set by who unmutes first, so confident talkers get the early framing and everyone else reacts to it. And agreement is cheap to type and costly to retract, so a thumbs-up in the chat gets read as commitment when it was only politeness.

The fix is structural, not motivational. Move the thinking into writing before the call, vote silently so the room sees the real spread of opinion, and force every priority through the same two questions: who owns it, and by what date. The rest of this piece is that structure. If you want the general case for it, see how to facilitate group decisions online.

Send pre-work five working days ahead and keep it to 20 minutes of effort per person. Three pieces are enough:

• A one-page review of the year, written by the sponsor or team lead, covering what shipped, what slipped, and what changed in the market or the budget
• Each person's written answers to three prompts: the top three priorities for next year, one sentence of reasoning for each, and one thing the team should stop doing
• The decision rule, stated in one line, such as who decides after hearing the group and whether the rule is vote, consent, or sponsor call

Collect the answers in one shared document or board and read them yourself before the session. Group the near-duplicates and note the outliers. Your job in the opening is to show the team its own thinking, already sorted, so the three hours go to deciding and not to collecting.

Tell people the pre-work is not optional and say why: anything not written down by the deadline cannot be voted on. That one sentence does more for completion than a reminder email. Pair it with the session planner if you want the agenda timed before you send it.

Here is the full block. The times assume a team of six to twelve on video, one facilitator, and a shared board or document everyone can edit:

• 0:00 to 0:15 Opening. State the purpose in one sentence, name the outputs (3 to 5 priorities, one owner and one date each, a decision log), restate the decision rule, assign a note-taker and a timekeeper, and open a parking lot for items that belong elsewhere
• 0:15 to 0:35 Read-out. Everyone reads the sorted pre-work silently, then asks clarifying questions only. No arguing yet, because nothing has been voted on
• 0:35 to 1:35 Priority sorting with silent voting. Cluster the candidates, name each cluster in a few words, vote silently, reveal the totals, then discuss only the top clusters and the surprises
• 1:35 to 1:50 Break. Cameras off, no content, no chat
• 1:50 to 2:35 Owner and date assignment. For each surviving priority, one name, one first-milestone date, and one sentence on what done looks like
• 2:35 to 2:50 Decision log read-back. The note-taker reads every row aloud and people correct it on the spot
• 2:50 to 3:00 Close. Each person says one sentence: what I am committing to and when you will see it. Name who sends the log within 24 hours and set the first check-in date

Open with a short framing of the kind in how to open a virtual session, and time every block the way a timed agenda does. If the team spans time zones, read live sessions and time zones before choosing the start time.

Silent voting means people choose before they hear each other argue. It separates what people think from what the loudest person just said.

Run it in four moves:

1. Cluster the pre-work candidates on a board and give each cluster a short name. Ask whether any cluster is missing and add it, then stop adding
2. Give each person 3 votes to spend on clusters, with no more than 2 on any one. A chat poll, a board dot-vote, or a numbered form all work
3. Reveal all votes at once. Revealing one at a time lets early results steer the late voters
4. Discuss in this order: the top cluster, any cluster with a wide split, and any cluster one person fought for and nobody else picked. That last one is where hidden knowledge often sits

Silent voting does not make the decision. It shows the room where it stands so the discussion goes where the disagreement is. If a top-voted priority has no one willing to own it, that is information too, and you handle it in the next block, not here. For a broader menu of moves, see workshop facilitation activities.

Use a proposal format. The sponsor or the person closest to the work proposes one owner and one date, and the group tests the proposal in two questions:

• Does the owner have the authority and the time to do this, given everything else on their list this year?
• Is the date a date or a hope, and what would have to be true for it to hold?

Write the owner as a single name. A team, a department, or “everyone” is not an owner, and a pair is a coin flip about who acts. If two people really share the work, name one as accountable and the other as contributor.

When the owner declines, do not argue. Ask what would change the answer: more time, a smaller scope, a different date, a decision from someone absent. Write the answer in the log. A priority nobody can own after that conversation has told you something real about the plan, and it is better to cut it now than to carry it as a shared wish.

If your team struggles to follow through on what it assigns, routing action items to named people is the next thing to fix.

Treat both as design problems, not personality problems. These moves work online without singling anyone out:

• Write first, then speak. Give 2 minutes of silent writing before any open question, so everyone arrives with something in hand
• Use the chat as a real channel. Ask for answers in chat on a count of three, then read several aloud, naming the idea and not the person unless they agreed
• Change the speaking order. Go round the room in a set order, start with the least senior person, and let the sponsor speak last so the sponsor does not set the answer
• Use pairs. A two-person breakout before a whole-group question gives a quiet person a rehearsal and a partner to carry the point
• Invite by name only with warning. Tell someone before the session that you will ask for their view on a specific item, so the invitation is a courtesy and not a cold call
• Hold a queue. Ask people to raise a hand or type a plus sign, and call on them in order, which ends the unmute race

For the person who talks over the room, give the role a job instead of a rebuke: make them the timekeeper, or ask them to restate the previous speaker's point before adding their own. More on this in the person who takes over the room, and on the other side, quiet participants need a different door and how to run a breakout room.

One page, one table, one owner of the document. Every row is a decision the group actually made, not a topic it discussed. Use these columns:

• Decision: one sentence, written so someone who was absent could act on it
• Owner: one name
• Date: the first milestone, not the final deadline
• Done looks like: one observable sentence
• Depends on: any decision, budget, or person the work is waiting for
• Dissent: who disagreed and why, in a few words, so the disagreement is on record without being re-litigated

The note-taker sends the log within 24 hours and the owners reply to confirm. Review it at the first check-in, which belongs on the calendar before the session ends. A decision log that nobody opens again is a fancier set of notes, so the check-in date is the part that makes it work.

Copy this into your planning document and tick it off.

Before the session

• ☐ Purpose and outputs written in one sentence each
• ☐ Decision rule chosen and stated
• ☐ Pre-work sent five working days ahead with a deadline
• ☐ Pre-work answers read, grouped, and loaded on the board
• ☐ Note-taker and timekeeper named
• ☐ Breakout rooms and voting tool tested
• ☐ Calendar hold set for the first check-in

During the session

• ☐ Outputs and decision rule restated in the opening
• ☐ Silent writing before every open question
• ☐ Votes revealed all at once
• ☐ One owner and one date per priority
• ☐ Every row of the decision log read aloud
• ☐ Each person states one commitment before leaving

After the session

• ☐ Decision log sent within 24 hours
• ☐ Owners confirmed by reply
• ☐ Parking-lot items assigned a home
• ☐ First check-in held on the date promised