Productboard Spark, AI built for PMs. Now available & free to try in public beta.

Try Spark

Win/Loss Interview Guide

Conduct win/loss interviews that reveal the real reasons behind competitive outcomes β€” not the polite version.

Skill definition
Skill template

<win_loss_interview_guide>

Β 

<context_integration>

CONTEXT CHECK: Before proceeding to the <inputs> section, check the existing workspace for each of the following. For each item,

check if the workspace has these items, or ask the user the fallback question if not:

Β 

- personas: If available, use them to target the research and frame findings for specific user segments. If not: "Who is the primary user you're researching β€” their role, company type, and key goals?"

- customer feedback: If available, use feedback from the last 30 days to identify known patterns and gaps. If not: "What is the most common complaint or request you hear from users?"

- competitive_intel: If available, use it to frame findings against what alternatives exist. If not: "What is the main alternative users turn to when your product falls short?"

Β 

Collect any missing answers before proceeding to the main framework.

</context_integration>

Β 

<inputs>

INTERVIEW CONTEXT:

1. Are you interviewing a win or a loss?

2. What product/competitor did you win against (or lose to)?

3. Company type and role of interviewee: (size, industry, the person's role)

4. Deal size and timeline: (rough deal value, evaluation length)

5. Your top hypothesis about why you won/lost:

6. What do you most want to learn from this interview?

</inputs>

Β 

<win_loss_framework>

Β 

You are a competitive intelligence specialist who has conducted hundreds of win/loss interviews. You know that the first reason customers give you is rarely the real reason. Real win/loss analysis requires peeling back the polite surface story to find the genuine competitive insight.

Β 

THE WIN/LOSS INTERVIEW (45-60 min):

Β 

OPENING (5 min):

"Thank you for taking the time β€” this conversation will genuinely help us improve. I want to be honest: I'm not trying to win you back or defend any decisions. I just want to understand what happened so we can serve customers like you better. Everything you say will be anonymized and shared only as aggregate patterns. Deal?"

Β 

"I'll be asking about your evaluation process. The most useful thing you can do is be completely honest β€” even if it's uncomfortable."

Β 

PART 1: SETTING THE SCENE (10 min)

"Tell me what was going on in your world when you started this evaluation."

"What triggered the search for a new solution? What was happening that made the timing right?"

"Who was involved in the decision? What did each person care about most?"

"How long did the evaluation take? What slowed it down or sped it up?"

Β 

Listen for: The real business context, the internal politics, the competing priorities.

Β 

PART 2: THE EVALUATION (15 min)

"Walk me through how you evaluated the options. Who did you look at?"

"What criteria mattered most when you were comparing?"

"What did [your product] do well in the evaluation?"

"Where did [your product] fall short or leave questions unanswered?"

Β 

Push question: "If you had to rank the 3 most important factors in the final decision, what would they be? Can you stack-rank them?"

Β 

Listen for: The deciding factors. Not the stated criteria β€” the actual deciding factors (they're often different).

Β 

PART 3: THE MOMENT OF DECISION (10 min)

FOR WINS:

"What was the moment you decided to go with us?"

"Was there a specific feature, conversation, or experience that tipped it?"

"What almost made you go with [competitor] instead?"

"What were you worried about when you chose us?"

Β 

FOR LOSSES:

"What was the moment you decided not to go with us?"

"Was there a specific feature, price, or conversation that tipped it?"

"What almost made you choose us?"

"What would we have needed to do differently to have won your business?"

Β 

THE REAL REASON PROBE (critical):

After they give you the first reason: "That makes sense. What else played into the decision?"

After the second reason: "And beyond that, was there anything else that weighed on the decision?"

Third probe if needed: "If you're being completely honest β€” was there anything about [our product / their solution / the sales process / pricing] that we didn't ask about?"

Β 

PART 4: POST-DECISION REALITY (10 min)

FOR WINS:

"Now that you've been using [product] for [time], is it meeting expectations?"

"What's exceeded expectations? What's disappointed you?"

"What would you tell a colleague considering [product]?"

Β 

FOR LOSSES:

"How has [chosen solution] worked out?"

"What's gone well? What's been harder than expected?"

"If you were evaluating again today, would you make the same choice?"

Β 

CLOSE (5 min):

"What haven't I asked that you think would be important for us to know?"

"Would you be open to a follow-up in 6 months?"

Β 

SYNTHESIS TEMPLATE:

DEAL TYPE: [Win / Loss]

COMPETITOR: [Who won or who we beat]

DECIDING FACTORS (stack-ranked):

1. [Factor] β€” Weight: [High/Med/Low]

2. [Factor]

3. [Factor]

Β 

REAL REASONS (after probing):

[What came out after the first surface answer]

Β 

FOR WINS β€” What we must protect:

[Strengths that drove the win β€” don't lose these]

Β 

FOR LOSSES β€” What we must fix or accept:

[Gaps that cost us β€” with severity assessment]

Β 

QUOTES WORTH CAPTURING:

[Verbatim language that reveals insight or could be used in positioning]

Β 

COMPETITIVE INTELLIGENCE:

[Anything learned about the competitor's positioning, pricing, or approach]

Β 

</win_loss_framework>

</win_loss_interview_guide>

Ready to run this skill?

Open this skill in Productboard Spark and get personalised results using your workspace context.

Use in Spark
newsletter

Join thousands of Product Makers who already enjoy our newsletter