The project status meeting is one of the most common and least efficient formats in the workplace. It exists to answer the question "where are we?" — a question that could, in most cases, be answered by a written update.
But it persists. So here is how to navigate it.
Why status meetings exist
Status meetings exist because some people process information better in conversation than in writing. They also exist because written updates require someone to write them, and meetings feel like less work than documentation. And they exist because some leaders want to hear updates directly, which is a preference, not a requirement.
None of these are bad reasons. They are just worth understanding.
The anatomy of a status meeting
A typical status meeting follows a predictable structure:
- Minutes 0–5: Waiting for people to join. Small talk. Someone's audio is not working.
- Minutes 5–25: Each person gives an update. Updates range from "everything is fine" to a detailed explanation of a problem that affects only one person in the room.
- Minutes 25–40: Discussion of the one problem that affects only one person. The other attendees wait.
- Minutes 40–60: Action items are assigned. The meeting ends. Three of the action items will become agenda items at the next status meeting.
How to give a useful status update
A good status update answers three questions: What did we accomplish? What are we working on? What is blocked?
It does not include: background context the room already has, explanations of why something took longer than expected, or updates on things that have not changed since last week.
If nothing has changed, say "no change on my end" and stop. This is not a failure to contribute. It is an accurate report.
How to handle the problem that derails the meeting
When someone raises a problem that requires a detailed discussion, the correct response is: "Let's take that offline — who needs to be in that conversation?" This is not dismissive. It is respectful of the other attendees' time.
If you are the person with the problem, offer to schedule a separate session rather than resolving it in the status meeting. The status meeting is not the right venue for problem-solving.
The proposal: Suggest replacing the status meeting with a shared written update once a week. Reserve the meeting slot for issues that genuinely require discussion. Most teams that try this find the meeting becomes shorter, more focused, and more useful.
Read next
→ How to Give a Status Update Without Sounding Like a Press Release