To replace a status meeting, give the update a home, a deadline, an owner, and a route for urgent blockers. Then try the new process for two cycles and ask what got missed. Canceling the invite is the easy part; making sure people can still get help is the job.

A status meeting can be useful. It can also be eight people listening to a board being read aloud, with occasional guest appearances by the mute button.

First, separate updates from decisions

Look at the last two meetings. Which items simply reported progress? Which needed people to resolve a dependency together? Move routine reporting to a shared document or thread. Keep a smaller conversation for a real trade-off, sensitive issue, or blocker that needs live back-and-forth.

Tell people where to find the update, who posts it, when readers should respond, and who closes decisions. Atlassian’s guidance similarly recommends explaining the replacement and how collaborators will stay informed.

Further reading: Atlassian: Think before you sync

Copy this weekly update

Project: onboarding pilot · Week of May 4 Changed: Email copy is approved; test segment is ready. Next: Launch to 10% of new signups on Tuesday. Blocked: Reporting access is pending. @Morgan, can you confirm access by Monday at noon? Decision: Priya will choose a fallback if access is not ready and post it here. Urgent issue: Message Priya directly; do not wait for the next update.

Use the same headings each week and link to the source of detail. The person compiling the update should remove stale items, not create a second project plan in prose.

Run a two-cycle experiment

  1. Announce the pause and the replacement: where updates appear, when they are due, and how to escalate.
  2. For two cycles, watch for unanswered questions, hidden dependencies, and work that slows down. Ask attendees what they missed, including quieter contributors.
  3. Keep the written process if it works. If a recurring issue needs discussion, restore a shorter call for that issue and the people who can resolve it.

Do not treat every recurring conversation as a status meeting. Coaching, relationship building, and difficult feedback can deserve protected live time.

Start with the copyable async update template and adapt it for your team.