What does a usable kill review look like each week?
A simple operator review that actually stops waste

Why do most weekly reviews fail?

Most weekly reviews fail because they are built to preserve comfort, not make decisions. Teams show dashboards, talk around edge cases, and leave every campaign alive for one more week. That is how waste survives.

A kill review has one job, stop spending time and budget on motions that are not producing enough signal to justify another cycle. If the meeting turns into storytelling, pipeline theater, or channel loyalty, you no longer have a kill review.

The second reason they fail is mixed metrics. Teams put replies, meetings, opportunities, activity counts, and anecdotes in one pile. Then they pick the metric that flatters the campaign. A usable review separates signal metrics from activity metrics and only asks activity questions after the signal call is made.

What should be on the page every single week?

Keep it brutally short. One row per motion. One owner. One stage. One decision. If you need ten tabs and a narrator, the review is too bloated to govern anything.

• Motion name and owner
• Channel and segment being tested
• Current stage, launch, warm up, live, iterate, or scale
• Primary signal metric for that motion
• Pre-set gate for kill, iterate, and scale
• What changed since last week
• Decision for this week
• Next action and deadline

For outbound send based motions, the cleanest weekly gate is positive on sends. The arithmetic is already good enough to make decisions. Under 0.5% positive on sends is a kill. Between 0.5 and 1% is iterate. At 1%+ you can scale. At 2%+ you can pour.

Notice what is not on that list. Vanity comparisons. Broad market claims. Long creative debates. A kill review is not where you decide whether your brand voice is brave enough. It is where you decide whether a motion still deserves oxygen.

How do you decide kill, iterate, or scale without fooling yourself?

Start by setting gates before launch. If you set them after seeing the data, you are not governing performance. You are negotiating with it.

That does not mean every weak week should trigger panic. It means every weak week needs context with discipline. If a motion is still in warm up, calendar behavior is broken, or ownership changed midstream, the interpretation changes. The gate does not disappear, but the diagnosis does.

This is where operator judgment matters. Outbound infrastructure does not mature in a day. Onboarding is about 21 days, and warm up usually takes 4 to 6 weeks. So a weekly kill review should distinguish between a motion that is genuinely live and a motion that is still structurally constrained.

Do not abuse that caveat. Teams hide behind ramp forever. A warm up explanation is fair early. It is not fair indefinitely.

A practical test for honest interpretation

• Was the motion actually live enough to judge this week?
• Did anything operationally distort the outcome?
• Is the problem signal quality, conversion after signal, or execution discipline?
• Can the owner name one change for next week?
• If not, why is the motion still alive?

Which inputs belong in the meeting, and which do not?

Bring only inputs that can change a decision. Leave the rest out. Weekly reviews get weak when the room tries to consume the entire GTM system at once.

• Include signal metrics tied to the motion
• Include notes on major changes, segment, list source, offer, owner, handoff, and calendar handling
• Include whether the motion is in launch, warm up, stable live operation, or expansion
• Exclude cosmetic dashboard charts
• Exclude activity bragging with no outcome relevance
• Exclude pipeline claims that cannot yet be attributed cleanly

A good example is replies versus positives. One week on the largest account produced 44,649 emails and 377 replies, a 0.84% reply rate. Useful fact. But it does not tell you the positive count for that week, so it cannot be used to claim scale readiness. Reply rate can tell you attention exists. It cannot replace the actual gate if your gate is positives on sends.

This is exactly where sloppy teams fool themselves. They see response activity and assume commercial traction. A usable kill review refuses that shortcut.

What trade offs and failure cases should you state out loud?

Every weekly kill review needs a section for failure conditions. Not because it sounds balanced, but because it stops dumb decisions. Advice without limitations is usually disguised marketing.

Here are the big ones. First, this framework works best when the motion has a clear primary metric and short enough feedback loops to review weekly. It is less useful for long cycle bets where signal arrives slowly and attribution stays fuzzy.

Second, this advice is not for founders who want every campaign preserved for political reasons. A real kill review will end pet projects. If you already know the room will not tolerate killing anything, save your time and do not call it a kill review.

Third, do not apply send based outbound gates to channels owned by sibling sites that need deeper execution nuance. If you need detailed outbound execution playbooks, that belongs under Outbound Pros. If you need deep multichannel sequencing mechanics, that belongs on the sibling sites built for channel execution depth. Mention the handoff and move on.

Fourth, poor downstream discipline can make a healthy top of funnel motion look bad. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. In those cases, killing top of funnel too early is a category error. The motion may not be the problem.

What does the meeting cadence actually look like?

Thirty minutes is enough if the prep is real. The owner updates the review sheet before the meeting. During the meeting, each motion gets a short readout and an immediate decision. If the team needs a separate workshop to redesign the offer, targeting, or process, schedule that outside the review. Do not let the review absorb strategy work.

• Open with motions already on watch
• Review only the current live set, not every historical experiment
• Force a call, kill, iterate, scale, or hold for a clearly named reason
• Assign one owner for each next step
• Carry unresolved structural issues into a separate fix list

I also like one line at the bottom of the sheet, what we are pretending not to know. That line catches the political excuses early. If everyone knows attribution is muddy, SDR follow up is inconsistent, or list quality changed, write it down. Hidden uncertainty is what keeps bad motions alive.

The benchmark to remember is not how busy the room felt. It is whether the portfolio got sharper after the meeting. A good weekly kill review narrows focus, protects winning motions, and stops sentimental spend.