How to run a weekly team review in 15 minutes

A weekly team review usually starts with good intentions and ends as an hour of people reading their status aloud while everyone else waits for their turn. Nobody learns much, and the one thing that mattered, the task that is quietly stuck, gets thirty seconds at the end.

The fix is to move the status out of the meeting. People write their update before the review, everyone reads it in silence at the start, and the time together goes to the only things that need a conversation: what is blocked, and what matters most next week.

What the review is for

Keep the purpose small enough to finish in fifteen minutes. By the end, three things should be true:

• Everyone knows what is at risk this week, and why.
• Every blocked task has one person who will unblock it, and a date.
• The team agrees on its top priorities for next week. Three at most.

Anything else, like a design debate, a client problem or a planning question, is a separate conversation with the people it concerns. The review's job is to spot it and give it an owner, not to solve it.

Before the meeting: five minutes each

1. Pick a fixed deadline for updates, a few hours before the review. Thursday at 4pm for a Friday morning review works well.
2. Each person writes their own update in the same shared place: one doc, one channel thread, or one page in your project tool.
3. Keep it to four lines. If it doesn't fit, the extra detail belongs in the task, not the update.
4. Name blockers with a person and a thing. “Waiting on Sam for the menu prices” is useful. “Blocked on content” is not.
5. Mark one risk, even if it's small. It trains the team to say early what could go wrong.

Done this week: [what finished]
Next week: [up to three things]
Blocked on: [who, and what you need from them]
Risk: [one thing that could go wrong]

The agenda, minute by minute

1. Minutes 0 to 3: everyone reads the updates in silence. No one presents. Questions go in a list for the next part.
2. Minutes 3 to 9: blockers only. For each one, agree who unblocks it and by when. If it needs more than two minutes of discussion, it becomes a follow-up between the two people who need to talk.
3. Minutes 9 to 13: next week's priorities. Propose up to three for the team, then check them against the risks you just read.
4. Minutes 13 to 15: one person reads back the decisions, owners and dates. Anyone who disagrees says so now.

Start on time, even if someone is late. The updates are written down, so a late arrival can catch up by reading them, and the habit of waiting is what turns fifteen minutes into thirty.

Write down three things, not the whole meeting

The record of a review should take one minute to write and one minute to read. Post it in the same place as the updates, straight after the meeting.

Week of [date]
Decided:
Owners and dates:
Still open:
Top priorities next week: 1. 2. 3.

When the next review starts, glance at last week's “Owners and dates” first. If a promised unblock didn't happen, that is the first blocker of the new week.

Rules that keep it short

• Same day, same time, every week. A review that moves around becomes optional.
• Nobody reads their update aloud. If it needs explaining, the update wasn't clear enough, and that's worth fixing in the template.
• Parked topics get an owner before the meeting ends, or they come back next week as the same problem.
• If no one is blocked and the priorities haven't changed, end early. Fifteen minutes is the maximum, not the target.

When it goes wrong

People don't write their updates. Move the deadline earlier, shorten the template, and have the facilitator reply to missing updates before the meeting, not in it. If someone often has nothing to say, four lines is still the right size: “Done: nothing new. Next: same task. Blocked: no. Risk: none” is a useful update.

The review turns into problem-solving. That usually means a blocker landed without a clear owner. Ask “who needs to talk to whom?”, write that down, and move on.

The same blocker appears three weeks in a row. It isn't a blocker anymore, it's a decision someone hasn't made. Name the person who can make it, and put the decision on their agenda, not yours.

Your team is spread across time zones. Run the same format without the meeting: updates by the deadline, a facilitator who reads them all and tags the people who need to talk, and a written record by the end of the day. Meet only when two or more blockers need a live conversation.

Try it for four weeks

The first review in a new format usually feels rushed, because people are used to talking through their status. By the third week the updates get sharper, blockers show up earlier, and the meeting starts to end before the fifteen minutes are up. Give it four weeks before you judge it, and change one rule at a time.