Weekly Status Meeting Agenda

What success looks like

Use live time for exceptions, decisions, and dependencies. The practical test is whether the people involved can point to a short review that changes the week's plan without reconstructing the whole conversation.

A practical method

Set the boundary for the work

Write a short review that changes the week's plan as the boundary. Keep only the evidence, authority, and participation needed to produce that specific result.

Work through the sequence

Collect status asynchronously, flag red or changing items, rank them by impact, and timebox only the exceptions that require the group. Place that instruction in the shared workspace and use it to distinguish the real work from background discussion.

Create a usable record

A durable record should make sense beside this example: The written dashboard covers twelve workstreams; the call handles the two with missed dependencies. Name any owner, due point, decision rule, or review trigger needed for another person to act.

Worked example

The written dashboard covers twelve workstreams; the call handles the two with missed dependencies.

Copy this example

The example connects directly to a short review that changes the week's plan. Put similarly concrete wording in the invitation, agenda, or record so the result can be checked later.

For a related example aimed at a bounded async process that still produces a decision or update, continue with Asynchronous Meetings: When and How to Use Them.

A failure to avoid

Watch for Reading every line of a dashboard that participants could review before the call. If it appears, pause and compare the discussion with a short review that changes the week's plan before more meeting time is used.

A useful recovery question

Ask: “What is the smallest responsible move that would still create a short review that changes the week's plan?” If the answer depends on missing evidence, record that evidence, one owner, and the exact return condition.

Final checklist

• The stated goal is a short review that changes the week's plan.
• The working method is visible to everyone involved.
• The record is specific enough to support an example such as: The written dashboard covers twelve workstreams; the call handles the two with missed dependencies.
• The design actively guards against Reading every line of a dashboard that participants could review before the call.

Next, use the meeting agenda builder to turn the method into a working artifact.