How to apply this guide
Speak yesterday, today and blockers as explicit categories. Keep unresolved blockers separate from tasks you can finish.
Start with
Try “Yesterday finished import. Today testing export. Blocked on access from Diego.” Use three lines in the team’s channel.
Check before you finish
If a blocker is merely a risk, say so before formatting the update. Add who can unblock you, what they need to do and when it would help. Avoid writing that another person has agreed to do the work unless they actually confirmed it.
Evidence to keep: Keep the target field open and verify that the complete reviewed result reached the intended destination. This page’s key limit is: Speak yesterday, today and blockers as explicit categories. Keep unresolved blockers separate from tasks you can finish.
Make a short draft
Try “Yesterday finished import. Today testing export. Blocked on access from Diego.” Use three lines in the team’s channel.
Check the destination
Check the person and action before posting. Place the blocker first when it needs someone’s immediate response.
What to watch for
If a blocker is merely a risk, say so before formatting the update. Add who can unblock you, what they need to do and when it would help. Avoid writing that another person has agreed to do the work unless they actually confirmed it.




