How long should the weekly outbound review run?

Keep it to 20 to 30 minutes on a fixed agenda. Anything longer typically means the team is using the meeting for problem solving instead of inspection. Reps come prepared with the scoreboard refreshed, one experiment to propose, and one blocker to surface, which compresses the time the meeting itself needs to spend on context.

Should reps prepare anything before the Monday review?

Yes. Each rep brings the scoreboard refreshed for their slice, one proposed experiment for the upcoming week, and one blocker they want help unblocking. RevOps brings the consolidated leading and lagging splits, and the pod lead brings the prior week's experiments and their outcomes.

What is the difference between the weekly review and a daily standup?

A standup is a 15 minute blocker clearing session for the day ahead. The weekly review is a longer inspection ritual focused on metric trends from the prior week and decisions for the upcoming one. Conflating the two is the most common reason both rituals degrade into status meetings.

Which metric should you look at first if the team is missing plan?

Start with pipeline coverage for the next quarter, then walk back through speed to first touch and positive reply rate. Coverage tells you whether you have a top of funnel problem or a conversion problem, and the two leading metrics tell you whether the issue is ops execution or message relevance.

The Weekly Outbound Review: What to Look At Every Monday

The weekly outbound review is a 30 minute Monday ritual that decides where the team spends the next five days. It is a structured inspection of leading and lagging signals from the previous week, paired with two or three written decisions about what to change in upcoming sequences, lists, and call blocks.

What the weekly review actually is

A 20 to 30 minute structured inspection of leading and lagging metrics, run on a fixed agenda, ending with two or three written decisions and named owners.

The 5 block agenda

Scoreboard read (5 min), leading signal review (8 min), lagging signal review (7 min), decision block (8 min), and writeup (2 min). The structure is what keeps the meeting from drifting into status.

Which metrics to inspect

Six to eight metrics including positive reply rate (3 to 6 percent), meeting hold rate (75 to 85 percent), SQO rate (50 to 65 percent), and pipeline coverage (3x to 5x). Skip the rest at this cadence.