Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
A realistic scenario
You found a problem that affects three teammates. It is important today, but it is not an emergency and the discussion may help others later.
Avoid rework
Three beginner mistakes
Sending 'Hi' and waiting before stating the request
Moving shared decisions into private messages
Using @channel for routine updates
The method
Complete it in six controlled steps
- 01
Identify the audience
Use a shared channel when the information belongs to a team or project. Use a direct message for personal or sensitive coordination, not to hide useful context.
- 02
Separate urgency from importance
State the deadline explicitly. Do not manufacture urgency with repeated mentions. Follow your team's documented incident route for true emergencies.
- 03
Write a complete first message
Include the issue, impact, evidence or link, requested action, owner if known, and decision time. The recipient should not need to ask what you want.
- 04
Use threads to contain detail
Reply in a thread when discussing one existing message. Post the final decision back to the main channel if people outside the thread need it.
- 05
Move channels with a summary
If a chat becomes a meeting or document task, carry forward the question, evidence, decisions, owners, and due dates. Do not make colleagues reconstruct context.
- 06
Close the loop
React or reply when you accept an action. Edit the original post or add a final update when the issue is resolved so the searchable record stays useful.
See the difference
Before and after
@channel urgent!!! Can someone check this?
Checkout test is failing for EU addresses. Impact: release QA is blocked. Evidence: test case 18. Could Priya confirm ownership by 14:00 UTC? Details in thread.
Original practice
Complete the exercise
Classify six workplace scenarios using the channel chooser, then rewrite one weak chat message so it includes context, action, owner, and time.
Use only fictional or fully anonymized data. Never upload an employer's confidential information to a portfolio.
Explain your decisions
Turn the exercise into credible evidence
Keep a one-page decision log for the six scenarios. For each, record the audience, sensitivity, urgency, discussion need, chosen route, and one rejected route. The point is not to prove that chat is always better than email; it is to show that you can make the communication trade-off explicit. End with the rewritten message and identify the context, action, owner, and time in separate annotations.
Quality gate
Check your own work
- Audience fits the channel
- Urgency is honest
- Request is complete
- Thread used for detail
- Decision recorded