Start with the job, not the app
A message can be clear and still fail if it arrives in the wrong place. A long decision request may disappear in a fast-moving chat, while a meeting to confirm one detail can interrupt several people. Before choosing a channel, ask: What do I need the recipient to do—read an update, answer a question, resolve confusion, or make a decision?
Then consider four factors. How soon is a response needed? How much back-and-forth is likely? Will people need a record they can find later? And how much interruption is reasonable? Also account for your team’s habits: a channel works only if the intended people can access it and know to check it. If you are unsure, make the request and its timing explicit rather than assuming that the tool conveys urgency.
Choose email when the message needs to stand on its own
Email suits information that people should be able to review on their own schedule: a project update, a request with several details, or a decision that needs a written record. It gives you room to state the context, name the action needed, and include relevant material without requiring everyone to be available at once. It is less effective for a question that depends on rapid, repeated clarification.
Make an email easy to act on. Use a subject line that identifies the topic, put the request near the top, and give a reasonable deadline if one matters. If you need a decision, list the options and say what will happen after the recipient replies. For example: “Please choose A or B by Thursday so I can prepare the draft.” That is more useful than a detailed message that leaves the next step unclear.
Use chat for brief coordination, not hidden decisions
Chat is helpful for short questions, quick status checks, and small points of coordination. It can keep work moving when an answer is likely to be simple: “Which version should I use?” or “Is the room available?” A short thread can also reveal that a question is more complicated than it first appeared.
Because chat moves quickly, important context can become hard to find. Avoid spreading a decision across dozens of messages if someone will need to refer to it later. Once a decision is made, put the outcome somewhere appropriate and easy to locate, such as a project note or follow-up email. Do not treat someone’s online status as a promise of immediate availability; if a response is genuinely time-sensitive, say when you need it and use your agreed urgent-contact method.
Move to a call when conversation will be faster than typing
A call can help when several questions depend on each other, a misunderstanding is growing, or a sensitive topic needs more care than a string of short messages allows. Hearing each other respond in real time makes it easier to clarify meaning and adjust course. A call is not automatically the best choice, though: it interrupts the other person and may be difficult to schedule or access.
Before calling, consider sending a brief note about the topic and asking whether now is a good time, unless your shared working agreement says otherwise. Keep the call focused on the issue you need to resolve. If it produces a decision or commitment, send a short written recap with the outcome, owner, and next step. This gives both people a chance to catch any misunderstanding.
Reserve meetings for work people need to do together
A meeting earns its place when people need to compare perspectives, solve a problem jointly, or agree on a course of action that cannot be settled easily in separate replies. It is usually a poor substitute for a one-way update. If everyone only needs the same information, a written message may be easier to review and less disruptive.
State the desired outcome before inviting people: “Agree on the two priorities for the next phase” is more useful than “Discuss the project.” Invite the people needed for that outcome, share enough context for them to prepare, and end by recording decisions and responsibilities. If the issue becomes simple before the meeting, consider cancelling it.
To build the habit of choosing well, review your next few messages before sending them. Write down the action you need, the response time that actually matters, and whether the result must be findable later. Pick a channel on that basis. If the exchange starts creating confusion or too much back-and-forth, switch channels deliberately—and bring the final outcome back into a clear written record.
