The weekly status meeting in 30 minutes

Seven practices to make the PMO weekly status meeting about deciding, not just reporting: written status beforehand, exceptions only, and agreements with an owner and a date.

The weekly status meeting is the most common PMO ritual and often the worst used: an hour in which every owner reads their list, nobody listens to what isn’t theirs, and decisions are postponed “until next time”. The problem is rarely the meeting itself, but that it is used to inform when it should only serve to decide. These seven practices bring it down to 30 minutes and make it useful.

1. Report in writing beforehand, decide live afterwards

Each project’s status is updated before the meeting, not during it. If someone has to say “how it’s going” out loud, five minutes are already lost that a document would have saved in ten seconds. The rule: what can be read is not presented.

2. One fixed page per project

Always the same fields, in the same order:

• Overall status (green, amber, red) with a sentence that justifies it.
• What was finished since the last meeting.
• What will be done this week.
• Risks or blockers, with an owner and a date.
• The decision needed, if any.

A stable format lets you compare projects at a glance and spot who “didn’t update” without having to ask.

3. Talk only about exceptions

Green projects with tasks on schedule need no airtime. They are reviewed silently or skipped. The conversation is reserved for amber and red, and for whatever changed color since last week. With ten projects, it is common for only two or three to consume the discussion.

4. Every red comes with a proposal

A red project without a proposal turns the meeting into a complaint session. Ask the reporter to bring one or two options: cut scope, move a date, add a resource, accept the risk. Then the group chooses instead of diagnosing.

5. An agenda with time boxes

A structure that works for 30 minutes:

• 0–5 min: last week’s agreements: were they met?
• 5–20 min: exceptions (amber and red), each ending in a decision.
• 20–25 min: new risks and dependencies between projects.
• 25–30 min: recap of agreements and owners.

The facilitator politely cuts off anything off-topic and moves it to a separate conversation between the people involved.

6. Minimum attendees and clear stand-ins

Invite only those who report an exception or need to decide. Someone sitting for an hour to hear ten relevant minutes is a real cost. If an owner can’t attend, define in advance who stands in with authority to decide; otherwise the item slips another week.

7. Close with agreements that have an owner and a date

The last minutes are spent reading the list of agreements aloud: what, who and by when. It is sent out the same day. At the start of the next meeting, the first thing reviewed is that list. If it isn’t reviewed, people learn that agreements are optional.

How to tell it’s working

Three simple signs: the meeting ends on time, most of last week’s agreements were met, and nobody finds out for the first time in the meeting that a project is red. If the last one fails, the problem lies in communication between meetings, not in the meeting.

Start with one thing this week: ask for the status in writing 24 hours ahead and spend the meeting only on what is amber or red. Most teams get half an hour back on day one.

PMO meetings project management best practices

← Back to the index