# How to Run a Win/Loss Program

> A start-to-finish operating guide for standing up a win/loss interview program: who interviews, what to ask, how to code findings, and how to keep leadership actually reading it.

Free guide for sales leaders. Topic: [Sales Content, Playbooks & Battlecards](https://www.peerlab.ai/library/topic/sales-content-playbooks-battlecards/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/how-to-run-a-win-loss-program/

## How to use it

Stand up the program in the order given; run the interview guide close to verbatim for the first two quarters, and use the action tracker to prove to leadership that findings actually change something.

## What's inside

- A scope-and-objectives framework (who to interview, minimum sample size)
- The neutral-interviewer rule and why the deal-owning rep can't run it
- A full word-for-word interview guide (14 questions)
- Loss-reason and win-driver coding taxonomies
- Monthly and quarterly reporting cadence and format
- An action-tracker template with named owners and due dates
- Governance steps to keep leadership actually reading it
- A common-pitfalls checklist

### A Start-to-Finish Operating Guide

## Step 1: Define objectives and scope
Decide explicitly before building anything:
- Are you interviewing every closed-lost deal, a sample, or closed-lost + a sample of closed-won (you need won deals to know what's actually working, not just what's failing)?
- What decisions will this program actually inform: product roadmap, competitive positioning, sales process, pricing? Name them now; a program with no decision attached to it dies after 2 quarters.
- What's the minimum sample size per quarter for the data to be directional? (Rule of thumb: at least 10-15 interviews per quarter, or 20% of closed deals above a minimum deal size, whichever is larger.)

## Step 2, Decide who conducts interviews
**Never the rep who owned the deal.** Buyers won't tell the losing rep the truth, and won reps will get generic praise instead of specific detail. Use a neutral interviewer:
- Enablement or product marketing (most common)
- Sales ops / RevOps
- An outside third party for strategic/large deals (removes any residual bias entirely)

## Step 3: Build the interview guide
Keep it to 12-15 questions, 20-30 minutes. Core structure:

**Opening (sets a candid tone):**
1. "Thanks for taking the time: this isn't a sales call, I'm not trying to win you back, I just want the honest version of what happened so we get better."

**Decision process:**
2. Walk me through how the decision ultimately got made.
3. Who was involved, and who had the final call?
4. What alternatives did you seriously consider?

**Evaluation of us:**
5. What stood out, positively or negatively, about working with us during the process?
6. Where did we lose you, if there was a specific moment?
7. What did our rep do well? What could they have done differently?

**Evaluation of the winner (for losses) / evaluation of runner-up (for wins):**
8. What made [winner/runner-up] compelling?
9. Was it product, price, relationship, timing, or something else?
10. If you could change one thing about their offer, what would it be?

**Decisive factor:**
11. If you had to name the single biggest reason for the outcome, what was it?
12. Was this decision close, or was it clear-cut?

**Closing:**
13. Is there anything you wish we'd asked, understood, or done differently?
14. Would you be open to revisiting this in the future, and under what circumstance?

## Step 4, Determine sampling and cadence
- Interview within 5-10 business days of close, memory degrades fast after that.
- Track response rate; if under 30%, revisit incentive/framing (a short thank-you gift or a summary of "what we changed because of this" for repeat participants helps).
- Segment interviews by deal size and by competitor faced, small samples pooled across very different deal types produce misleading trends.

## Step 5: Code and analyze with a fixed taxonomy
Don't leave loss/win reasons as free text only: code them against a consistent taxonomy so trends are comparable quarter over quarter:

**Loss-reason taxonomy (example: customize to your market):**
- Price/budget
- Product gap (name the specific capability)
- Competitor relationship/incumbency
- Timing/priority shift
- Poor sales process (slow response, weak discovery, no multithread)
- No decision made (lost to inaction, not a competitor)
- Champion left / lost internal support

**Win-driver taxonomy:**
- Product capability (name it)
- Sales process/rep execution
- Pricing/commercial terms
- Existing relationship/reputation
- Implementation/support confidence

## Step 6: Report on a fixed cadence
- **Monthly:** a 1-page trend snapshot: top 3 loss reasons, top 3 win drivers, any competitor movement.
- **Quarterly:** a deeper deck: trends by segment, by competitor, by rep team, with specific verbatim quotes attached to each finding (quotes make findings land; aggregate percentages alone don't).

## Step 7: Close the loop: route findings to an owner
Every finding needs a named owner and a due date, or it's just an interesting deck. Route by type:
- Product gaps → product/roadmap owner
- Competitive positioning gaps → enablement (feeds the Battlecard Effectiveness Scorecard)
- Sales process gaps → sales leadership/playbook owner
- Pricing/packaging gaps → RevOps/pricing owner

**Action tracker template:**

| Finding | Source (quarter) | Owner | Action | Due date | Status |
|---|---|---|---|---|---|
| | | | | | |
| | | | | | |

## Step 8: Govern it so leadership actually reads it
- Get an executive sponsor who asks for it, not just receives it.
- Put it on a standing quarterly business review agenda, a program with no calendar slot gets deprioritized within two quarters.
- Show the action tracker's status at every readout, "here's what changed because of last quarter's findings" is what keeps leadership engaged.

## Common Pitfalls
- Letting the deal-owning rep conduct or sit in on the interview
- Collecting data with no taxonomy, producing a pile of anecdotes nobody can trend
- Reporting findings with no owner or due date attached
- Only interviewing losses: you can't tell what's actually working without wins in the sample
- Waiting weeks after close to interview, when memory (and honesty) has already faded