How do you give a good progress update in a team chat?
Good progress updates help other people plan. Put confirmed work before future plans, make dates or owners concrete when they matter, and state blockers as dependencies rather than as complaints about a person.
Examples you can use
A standard update
Quick update: the research is complete, and I’m drafting the recommendations today.
A simple done-plus-next structure works for most daily updates.
When you are on track
The build is on track for Friday. QA starts tomorrow morning.
Give a concrete milestone instead of “making good progress”.
When there is a blocker
The layout is ready, but I’m waiting on the final copy before I can publish.
State the dependency plainly and avoid blaming a person.
A manager-facing update
I’ve completed the analysis. I’ll share the recommendation by end of day tomorrow.
Useful when your manager needs a clear expectation.
A cross-functional update
Marketing has signed off on the messaging. Engineering is now validating the tracking events.
Name the handoff so everyone sees where the work sits.
A concise stand-up note
Done: updated the onboarding flow. Next: test the new emails. Blocked: waiting for legal copy.
Labels make a compact update easy to scan.
How to make the message sound natural
- Be specificUse an outcome, owner, or date. “Working on it” gives the team nothing to plan around.
- Separate facts from plansSay what is already complete before describing the next step.
- Flag blockers earlyA neutral blocker update is helpful; waiting until a deadline passes is not.
A common mistake
Avoid
I finished update the deck yesterday, you can review now.
I finished update the deck yesterday, you can review now.
Try instead
I finished updating the deck yesterday — it’s ready for your review.
I finished updating the deck yesterday — it’s ready for your review.
Rewrite your own message
Paste a short work message and choose the person and tone.