All Things Workplace

Async Update Instead of a Meeting How-to

Sep 10, 2026 | How-tos, Meetings & 1:1s

Your recurring “quick sync” has become a round-robin. Four people read tickets aloud. Nobody decides anything. You leave with the same blockers and a calendar scar.

Time box: 15-25 minutes to draft a written update, cut fluff, post it, and track asks. Async fails when the ask is buried. Put the decision or help request in the first screen. Status without a clear ask trains people to skim and still book meetings.

Use this with the Individual Contributor hub and New Manager hub. For the longer guide, see async updates instead of meetings.

When to use (and when not to)

Use async when the job is:
– Inform, status, or FYI
– Progress against a known plan
– A searchable record across time zones
– Replacing a meeting that produces zero decisions

Do not use async when you need:
– Conflict repair, sensitive feedback, or performance talk
– Complex tradeoffs that need rapid back-and-forth
– Shared judgment on something brand new under ambiguity
– Anything legal-sensitive, harassment-related, or termination-adjacent (those are live, with the right people)

Never replace a difficult conversation with a Slack update. Never “async” a termination or ER issue.

Who is involved

  • Author (you)
  • Distribution list (team channel, stakeholder list, or standing doc watchers)
  • Optional decision owner explicitly tagged on the ask
  • Readers who only need FYI (say so)

Pull names from your stakeholder map so you’re not spamming the whole company.

Prep

  • Know the audience (team vs. cross-functional vs. exec skim).
  • Know the channel norm (Slack thread, Teams, email, Notion/Google doc).
  • Set a cadence (daily standup alternative, twice weekly, or weekly).
  • Decide a response SLA for asks (for example: “Reply by tomorrow 2pm if blocking; emoji ack if FYI”).

Template: Progress / Plan / Problems / Ask

Lead with the work. Put Ask where tired eyes land first if the update is long; many teams put Ask at the top and repeat it at the bottom.

Update: [project or team] | [date]
Owner: [name]
Response SLA: asks need a reply by [day/time]; FYI = emoji ack optional

ASK (if any):
- @[Name]: please [decision or input] by [day/time]

Progress: what shipped or moved (facts)
Plan: next 1-3 concrete steps
Problems: blockers / risks (impact if known)
No ask / FYI only: [yes/no]

Progress is evidence (“Merged auth fix; QA on staging”), not vibes. Plan is near-term. Problems without an ask is a diary. Pair them.

Before / after (fictional)

Before (buried ask):

This week was busy. We talked to design, did some tickets, waiting on a few things, will update later. Thoughts?

After:

Update: Checkout redesign | Wed | Owner: Jordan
ASK: @Sam (Legal) approve or redline refund paragraph by Thu 3pm PT

Progress:
- Mobile cart prototype v3 in Figma
- Analytics events reviewed with Data

Plan:
- Usability test Thu (3 customers)
- Eng handoff Friday if Legal clears

Problems:
- Legal review blocks Eng handoff

FYI only for others: emoji ack fine

Steps inside the time box

  1. Minutes 0-5: Skeleton. Paste the template. Write Ask first if you have one.
  2. Minutes 5-15: Fill facts. Progress and plan in bullets. Cut autobiography.
  3. Minutes 15-20: Cut fluff. Delete adjectives, meeting recaps, and anything readers can see on a dashboard.
  4. Minutes 20-25: Post and track. Publish. Add open asks to a tracker (doc table or pinned thread). Set a reminder for the SLA.

If drafting regularly takes more than 25 minutes, your update is too wide. Narrow to one project or one week.

Scripts: convert meeting ↔ async

Propose async instead of a recurring meeting:

Proposed async update for [topic] instead of the weekly 30. I’ll post every [cadence] in [channel/doc] with Progress / Plan / Problems / Ask. Flag by [day] if you still need 15 live minutes for decisions.

Decline a one-off politely:

I can cover this async. Draft update here: [link]. If there’s a decision that needs live tradeoffs, happy to book 15.

Escalate async → meeting:

The thread is looping on [tradeoff]. Booking 15 minutes with [decision owner] so we don’t burn another day. Pre-read: [link].

More decline language: how to decline a meeting politely. Meeting design: how to run effective meetings.

Output

  1. Standing update (same place every time: channel or doc).
  2. Open-asks tracker:
Ask Owner Due Status
Approve refund copy Sam Thu 3pm Open

Close the loop when asks resolve. Unclosed asks are why people invent meetings again.

Response SLA so async isn’t ignored

State the rule in the update header. Examples that work in many teams:
– Blocking asks: reply by next business day (or a named time).
– FYI: optional ack.
– If no reply by SLA: one bump, then escalate to a 15-minute live slot.

Don’t set “ASAP” as a deadline. Don’t hide bad news in paragraph four. Bad news belongs in Problems with an Ask.

Watch-outs

  • Walls of text. If it needs a scroll marathon, split projects or link out.
  • Hiding bad news. Async is not a place to soft-pedal risk.
  • Never closing asks. Track them or you’ve created unread theater.
  • Culture mismatch. Some orgs still need a short live ritual; hybrid is fine (async first, 15 minutes only for open decisions).
  • Wrong topics. No performance warnings, ER issues, or legal-sensitive matters in a status thread.

How this connects

Use read-the-room to notice when a live slot is actually informing, then convert it. Keep decision-heavy topics in 1:1s or dedicated forums. Stakeholder lists from your map tell you who must be on the distribution vs. FYI.

You’re done when the update has a clear ask (or an explicit “FYI only”), fits one screen for busy readers, and every open ask has an owner and due time.