It’s Monday and you need a decision by Tuesday. You could invite six people to a call, or send a short note and ask for replies. The deadline alone won’t tell you which is better. Start with what needs to happen between now and the decision.

Imagine a team choosing the date for a small support-guide pilot. If everyone can assess the same proposal independently, a note may be enough. If one answer changes the next question, a conversation may save a long, tangled thread.

When the reply fits in the margin

Use a memo when people need time to read, check a fact or consult their own calendars. State the proposal, the reason for it, the decision-maker and the reply you need. Give a real deadline and say what happens next.

For example: “Proposed: start the support pilot on 12 May. Please flag a staffing conflict by Thursday at noon; Jo will confirm the date after reviewing replies.” Include the relevant link and enough context for someone who missed the earlier discussion. Avoid treating a missing response as approval unless that expectation was agreed in advance.

A yellow folded note waits on a sunlit desk beside an empty purple chair.
Some decisions need a conversation. Others need time to read and reply.

When one answer changes the next question

Meet when people need to work through a disagreement, compare constraints in real time or build an answer together. For the pilot, perhaps staffing depends on launch timing, while launch timing depends on an unresolved training plan. Hearing those constraints together may be quicker than several rounds of replies.

Send a short starting point first: the choice, the constraints you know and who can decide. Invite the people needed to make or inform that choice, not everyone who may later need the outcome. End with the decision, owner and next step in writing, including any issue that remains open.

Make the switch when the format stops helping

A memo can expose a disagreement that deserves a call. If replies start answering different questions, summarize the sticking point and invite the relevant people to resolve it. Equally, cancel or shorten a meeting if the necessary answers arrive beforehand. Send the outcome to those who were expecting to attend.

Neither format automatically creates participation. A live discussion can favor the quickest voice; a written request can disadvantage someone without the time, access or context to respond. Share material early where possible, make room for questions, and offer another way to contribute when needed.

Planning memo

Can support start the pilot on 12 May?

Jo needs to know who can cover the support queue while two people try the guide. Here’s how the same memo can lead to two different next steps.

A written reply is enough

“I can cover the queue until noon.” Jo can check the rota and confirm the date in the thread.

Get two people on a call

“I can cover if training moves, but the trainer needs our start time first.” Jo asks the trainer and the shift lead to pick a workable time together.

Finish with a record

Whichever route you take, leave the same trail: what was decided, who owns the next action, and when the decision will be checked if that matters. A short recap is especially useful when the final conversation happens in a call but others contributed in writing.

Before sending the invite or the memo, write the response you hope to receive. If you can name it, you can choose a format that gives people a fair chance to provide it.