Give the message a job
Lead with the decision, question, or action. Include the relevant context, the person responsible, and a realistic deadline. “Can you review the budget by Thursday?” is easier to act on than a long thread that ends with no clear request.
Choose the right audience
A shared project space makes context available to the people doing the work. A direct message is better when the subject is private or concerns a small number of people. Confirm the audience and access settings before sharing confidential information.
Close the loop
When a discussion reaches a decision, summarize the outcome and where the durable record lives. Avoid assuming that an emoji reaction means the same thing to everyone. For urgent work, use the agreed escalation route rather than relying on a message alone.
A concise message template
Try: “Decision needed: approve the draft by Thursday, 15:00 Sofia time. Owner: Maya. Context: the current draft is linked below. If there is a blocker, reply here.” Replace the names and deadline with real details. The first line tells a busy reader what is needed; the rest gives enough context to respond. After the decision, post a short outcome and update the source document so future readers do not have to reconstruct the thread.
Choose the next step
| Situation | What to check |
|---|---|
| A simple acknowledgment | A reaction may be enough if the team shares its meaning. |
| A decision with consequences | Record the approval, owner, and resulting action in text. |
| An urgent incident | Use the agreed escalation route rather than assuming a message is seen. |
A practical checklist
- Open with the action or decision.
- Add enough context and a clear owner.
- Choose the smallest appropriate audience.
- Record the outcome where the team can find it.