Choose the format that helps the work move forward
A meeting is useful when people need to think together. An asynchronous message is useful when people can review information and respond independently. Neither format is inherently more collaborative. The right choice is the one that helps the team reach a clear next step without asking everyone to spend more time than the decision warrants.
Before scheduling a call or starting a thread, ask three questions: What needs to happen next? Who must contribute? What would make their input easier? If you need a quick approval of an agreed direction, a message with the relevant link may be enough. If a designer, writer, and client disagree about the direction itself, a short conversation may help them uncover the reason. Urgency matters, but an urgent label does not automatically make a meeting useful; the right people and materials still need to be available.
Use messages for reviewable, independent work
Send an asynchronous message when the request is specific, the context can be shared, and contributors do not need to hear one another's answers in real time. Status updates, draft reviews, straightforward approvals, and handoffs often fit this pattern. A student team, for example, might share a presentation draft with a note asking each member to check one assigned section before the next editing session.
Make the message easy to act on. State what changed, link to the current version, name the input you need, and give a reasonable response deadline. “Please comment on whether the opening explains the problem clearly by Thursday” is easier to answer than “Thoughts?” If several people are reviewing, specify whether they should comment independently or build on earlier feedback. Keep decisions in the shared project record rather than relying on someone to find them later in a chat thread.
Messages also give people time to examine a design, test a prototype, or think through wording before responding. That can improve the quality of considered feedback. The trade-off is delay: if every reply introduces a new question, a thread can become a slow substitute for a conversation. Notice when that happens and change formats.
Meet when discussion will change the outcome
A meeting earns its place when the participants need to resolve conflicting priorities, generate ideas together, or make a decision that depends on several perspectives. Imagine a small team preparing a campaign: the visual concept is appealing, but it is difficult to adapt to the required formats. A conversation between the designer and the person responsible for delivery may expose the constraint faster than separate rounds of comments.
Meetings are also useful for sensitive or ambiguous feedback. A freelancer hearing “this does not feel right” may need to ask questions about audience, tone, and examples before revising. A call can help both sides distinguish a problem with the brief from a problem with the draft. The aim is not to discuss every detail live; it is to understand the issue well enough to agree on what to do next.
Invite only people who can contribute to or make the decision. Share the work and the question beforehand so participants can prepare. Give the meeting a clear endpoint, such as choosing a direction or assigning a test, rather than the vague goal of “catching up.” If the group cannot decide yet, record what information is missing and who will obtain it.
Use a short exchange when neither option quite fits
Some questions begin as messages and become meetings. If a thread circles around the same disagreement, people are interpreting the brief differently, or the proposed solution keeps changing, suggest a brief discussion focused on that single issue. Conversely, if someone requests a meeting to deliver an update, ask whether a written summary would let others review it on their own schedule.
You can also combine the formats deliberately. Share a brief and sample work asynchronously, hold a focused conversation to resolve open questions, then post the decision and next steps afterward. This approach gives quieter participants a chance to prepare and preserves a record for anyone who could not attend. It works well for project kickoffs, creative reviews, and final delivery checks.
Close the loop in the same place every time
Whatever format you choose, collaboration fails when the outcome is unclear. After a meeting, write down the decision, any unresolved questions, the owner of each next step, and the relevant deadline. After a message thread, mark which feedback was accepted, deferred, or declined so contributors do not have to guess. Keep that summary alongside the brief, task, or deliverable where the team will look for it.
A simple team agreement can remove repeated uncertainty: use messages for updates and review requests, schedule conversations for unresolved trade-offs, and document decisions in a shared project space. Adjust the agreement as the project changes. The goal is not to eliminate meetings or messages, but to let each do the job it handles best.
