Win-loss, Part 2 of 5: debrief rituals that actually run

A quarterly debrief is a meeting where someone presents a slide deck about bids that closed two months ago and the room nods. A per-bid debrief is a 30-minute working session that produces 8 to 12 KB-block edits and one process change. Only one of these compounds.

This is Part 2 of five. Last week we covered what to capture. This week is the ritual that uses the captured fields to produce learning.

Why quarterly debriefs fail

I’ve watched roughly twenty proposal teams attempt a quarterly debrief practice. About four of them stuck with it past month six. The failures share a structure.

The deck takes six hours to prepare. The meeting is an hour. Most of the meeting is the deck. The discussion is fifteen minutes at the end, when energy is gone. The action items get assigned to “the team” instead of a named person. By the time the action items are reviewed in the next quarterly, most of them are stale or have been quietly closed without resolution.

Leulu & Co named the same pattern: the debrief ends, the document is published, people move on. Nobody asks at sprint planning what happened to the actions from last week’s incident.

The structural fix is to stop running quarterly debriefs and start running per-bid debriefs, smaller, with a named owner and a 30-minute box.

The 30-minute format

Every closed bid (won or lost) gets a 30-minute debrief, scheduled at submission, held within ten business days of the outcome. The agenda has four questions. The proposal manager owns it. Output is captured in the win-loss dashboard or whatever your equivalent record is.

Minute 0-5 — read the structured data

Before discussion, the proposal manager pulls up the bid’s record: the bid/no-bid score, the win themes, the past-performance citations, the SME tickets, the deferred review comments, the draft-to-submit delta. The room reads. Five minutes, no talking.

This is the most important and most-skipped step. People walk into debriefs with a narrative already formed. The data is the corrective. If you don’t read it before discussing, you discuss the narrative.

Minute 5-15 — Question 1: what did the buyer tell us?

Verbatim where possible. The stated reason from the buyer’s debrief or email. If we didn’t get a buyer debrief, what did the salesperson hear in the post-decision call?

This is short on purpose. The buyer’s stated reason is data, not interpretation. We capture it, we don’t interpret it yet.

Minute 15-22 — Question 2: which deferred review comments now look prescient?

Pull up the deferred red-team and gold-team comments (capture field 13 and 14 from Part 1). For each, ask: in light of the outcome, did this comment turn out to be on the path of the loss?

This question is the highest-yield in the agenda. A comment that was deferred because “there isn’t time” and that lined up with the buyer’s stated reason is a process failure. We don’t moralize about it; we note it and propose a process change.

Minute 22-27 — Question 3: which KB blocks need editing?

Walk the section-by-section provenance. For each section the buyer flagged or the team rated as weak, find the KB blocks that sourced it. Propose specific edits — add a number, refresh a date, retire a block, split a block, write a new one.

This is where the debrief produces artifacts. By the end of minute 27, the meeting should have generated 5 to 12 specific block edits.

Minute 27-30 — Question 4: who owns the next move, by when?

Every block edit gets an owner and a date. Every process change (a calendar change, a review-rubric change, a SME-engagement change) gets an owner and a date. Nothing gets assigned to “the team.”

The proposal manager closes the meeting. Total time: 30 minutes.

The DRI rule

Every debrief has one DRI — directly responsible individual — and that person is the proposal manager who ran the bid. Not a committee. Not “win-loss as a function.” The PM who shipped the bid runs the debrief on the bid.

This rule fights the impulse to centralize debriefs in a “win-loss analyst” role. Centralized analysts are slower, less specific, and more political. The PM has the context. The PM owns the learning.

The DRI rule has a corollary: if the PM has left the company, the bid doesn’t get a debrief. Better to skip than to run a fictional one.

Calendar discipline

Three calendar habits keep the ritual alive.

Schedule the debrief at submission. When the proposal manager clicks submit, the next item on the calendar is the debrief, conditionally placed two weeks out. If the outcome lands earlier, pull it forward. If the outcome doesn’t land in 60 days, hold the debrief anyway against the pending status — the in-bid lessons are captureable without the buyer’s verdict.

Don’t batch. A team that runs five debriefs back-to-back on a Friday afternoon will phone in four of them. One bid, one debrief, one calendar slot.

Cap the agenda. A debrief that goes past 45 minutes is a debrief without discipline. The DRI’s job is to land the agenda in 30. If a topic genuinely needs more time, it becomes a separate working session — not an extension of the debrief.

What gets captured back

By the end of every debrief:

A proposal_outcome row with the buyer’s stated reason verbatim, source-tagged.
5-12 debrief_note rows, each with severity and (where applicable) a target KB block.
0-2 process-change tickets routed to the team’s project tracker.

The notes flow into the evidence linker the engineering team shipped this week. The linker proposes the edit; the block owner accepts or declines. The next bid sees the updated content.

This is the closing of the loop. Without the linker, the notes are good intentions. Without the notes, the linker has nothing to link. The ritual is the part of the system the software can’t do.

Why this works when quarterly didn’t

The per-bid debrief works because it stays attached to the bid. The team remembers. The data is fresh. The PM is the owner. The output is structured and links back to the artifacts that need editing.

Lohfeld makes the related point that perpetual slowness in proposal completion comes from process work that happens in the wrong place at the wrong time. Quarterly debriefs are the wrong place. Within ten days of outcome, with the people who shipped the bid, is the right place.

What’s next

Part 3 next Wednesday covers the five anti-patterns even good debrief practices fall into. Part 4 covers how the debrief output becomes durable KB change, including the review cadence that keeps changes from regressing. Part 5 closes the series with the eighteen-month view.

The takeaway from this part: a debrief without structure is a meeting. A debrief with four questions, a fixed clock, a single owner, and a written output linked to KB blocks is a learning system. The difference is in the discipline, and the discipline is mostly calendar discipline.