Loss Review.

What

Once a month, the floor sits with its closed-lost deals from the prior month and reads them for pattern. Every lost deal has a reason code; the codes are grouped; the top three are named. One of them is usually structural and usually fixable in an afternoon if the floor commits to it. That is the Loss Review.

Why

Every loss is a data point in a pattern. The pattern is the lesson. The rep is the data. A meeting that names the rep produces hidden information, because the rep defends herself and the room calibrates to her defense. A meeting that names the pattern produces visible information the team can act on. The Loss Review is the manifesto's most direct expression of Principle 7: review the system, not the rep.

Who

• Sales Master. Runs the review. Names the patterns. Pulls the room back when it slides toward blame.
• Pipeline Owner. Brings the reason-coded data: every closed-lost deal from the prior month, with its code and stage at loss.
• Every Closer. Present. Speaks only to clarify a code or to surface a structural pattern they've seen. Does not relitigate individual deals.

Cadence

Once a month, on the same day, in the first week after month-end. Sixty minutes, no more. If it runs long, the ritual has slipped. See failure modes.

Script

1. Open (3 min). Sales Master frames the meeting: the review is about patterns, not deals; about the system, not the rep. The framing matters every time. The blame reflex is strong.
2. Reason codes (15 min). Pipeline Owner reads the distribution: how many losses, what codes account for what share. The top three reasons get the most air; the long tail gets noted and skipped.
3. Pattern walk (25 min). The room reads each top reason as a pattern. "Six deals lost to price after demo" is the pattern. The question is not who lost them; the question is what is the system producing that ends in that loss. Anyone speaking to defend themselves is gently redirected.
4. Commit (10 min). The Sales Master names one or two system-level changes the floor will run for the next month: a different demo flow, a stage-gate insertion, a script for a specific objection. Owned, dated, written down.
5. Close (5 min). Restate the commitments. End on time.

Failure modes

• It becomes a witch hunt. Someone names a rep, usually the lowest-performing one, and the room calibrates around her defense. The ritual is dead in that moment. The Sales Master's only job is to never let it happen.
• It relitigates the deal. "If we'd just given them another week" lives in last month. The review is about the system this month and next, not about deals that already closed. Cut the deal-by-deal autopsies.
• It produces no commitments. A Loss Review that surfaces a pattern and walks out without naming the change is theater. One commit per top reason; written, owned, dated.
• It runs without reason codes. If the data isn't coded before the meeting, the meeting becomes anecdote-trading. The Pipeline Owner codes the losses before the floor walks in.