Standup Update

  • Yesterday I [completed / worked on] [task]. Today I'm picking up [task]. No blockers.
    The classic three-question standup format
    "Yesterday I finished the auth migration. Today I'm starting on the session expiry logic. No blockers."
  • I'm blocked on [issue] — [name], are you able to help after standup?
    Flagging a blocker and naming a resolver
    "I'm blocked on the staging environment being down — Dev-Ops, are you able to look at it after standup?"
  • No update from yesterday — I was in [meetings/on leave]. Picking up [task] today.
    Explaining a gap day without over-explaining
    "No update from yesterday — I was in all-day interviews. Picking up the data pipeline work today."
  • I'm carrying over [task] — ran into [issue], will update by EOD.
    When a task is rolling over from yesterday
    "I'm carrying over the API rate limiter — hit an unexpected edge case with retries, will update by EOD."

Async Standup

  • Async update: Done: [X]. Doing: [Y]. Blocked: [Z] or None.
    Written async standup format
    "Async update — Done: CI pipeline fix. Doing: load testing setup. Blocked: None."
  • Flagging for async: [issue] — I'll DM [name] for context.
    Surfacing an issue in async format
    "Flagging for async: the prod cert expires Friday — I'll DM Tom for context on the renewal process."
  • Note: I'm [time zone / working hours] this week — async responses may be delayed.
    Setting expectations for cross-timezone standup
    "Note: I'm UTC+9 this week — async responses may be a few hours delayed."

Phrases to Avoid

These common phrasings undermine your professionalism. Here are better alternatives.

Avoid "I was busy yesterday."
Better "Yesterday I worked on [specific task] — I'm continuing that today."

"Busy" is uninformative. Name the specific task so the team understands where time went.

Avoid "Same as yesterday."
Better "Continuing [specific task] — [brief progress update]."

"Same as yesterday" gives no insight into progress or current state. A brief update keeps the team informed.

Avoid "I'll explain in Slack."
Better "Short version: [brief update]. I'll share more context in #team-channel."

Deflecting to Slack without any standup update defeats the purpose of the standup. Give the headline, then direct to Slack for details.

Practice Exercises

Choose the most professional or correct phrase for each scenario.

Frequently Asked Questions

How long should a standup last?

A standup should last 15 minutes or less for a team of up to 8. Each person should take 1–2 minutes maximum. If discussions arise, "take it offline" — schedule a follow-up rather than extending standup.

What does "take it offline" mean?

"Take it offline" means to have a detailed discussion outside the meeting — either in a separate call, Slack thread, or face-to-face. It keeps the standup focused.

What is an "async standup"?

An async (asynchronous) standup is a written update posted in Slack or a dedicated tool (like Geekbot), typically following the Done/Doing/Blocked format, instead of a live video call.