Give the message
a place to land.
An independent guide to the ordinary communication work of a small team: shared context, a clear request, a visible decision, and a handoff another person can understand.
Read the conversation guideAn independent editorial resource. Not a network operator, communications platform, consultancy, or service provider. No real teams, clients, or results are represented.
Make the reason for the message visible.
A team can use the same channel while working from different assumptions. Someone may read a note as a decision, another as a draft, and another as a question that needs no reply.
Begin by naming the purpose and the context the reader needs. A request becomes easier to understand when its relationship to the work is explicit rather than hidden in an earlier conversation.
This is a reading and writing resource. It does not inspect team messages, prescribe an organizational policy, or promise a change in performance.
Context, request, decision, handoff.
These functions can appear together, but they should remain recognizable. A concise message can still be unclear if the reader has to infer which part requires a response.
- Context
- What the reader needs to know to understand the topic. Include the relevant source or earlier decision instead of assuming everyone saw it.
- Request
- What response or contribution you are asking for. Make a question look like a question rather than an implied instruction.
- Decision
- What has been agreed, by whom in the actual team process, and which conditions or open points remain.
- Handoff
- The next responsibility and the information that needs to travel with it. A handoff is more than forwarding the conversation.
A little structure can preserve the meaning.
A useful message can distinguish the source material from the proposed next step. That distinction allows someone to question the proposal without losing the background.
The exact format should fit the team and its existing requirements. These labels are writing prompts, not a compulsory workflow or a software feature.
“Context: the draft still uses the earlier title. Request: please confirm which title the approved source uses. Open point: the change has not yet been agreed.”
A channel is a setting, not a shared memory.
Where a discussion happens affects how someone finds it later. Keep the purpose of the exchange and the place of the lasting record distinct.
A discussion
Useful when the team needs to develop an understanding. Preserve the open questions and avoid treating the last message as an automatic decision.
A decision record
Useful when a conclusion needs to remain findable. Link it to the relevant context and distinguish the result from the discussion that preceded it.
A handover note
Useful when responsibility moves. Explain what is complete, what remains unresolved, and where the next person can find the source material.
Read it as the person who was not in the room.
A final reading can reveal assumptions that felt obvious while you were writing. The aim is not a longer message; it is a message whose purpose and status are easier to recognize.
- Can the reader tell whether this is a question, a proposal, or an agreed decision?
- Is the necessary source or context available without reconstructing an entire thread?
- Does the note show what remains uncertain?
- Can the next person identify the responsibility being handed over?