Competitor User Interview: Why They Chose It and What Would Make Them Switch
Use this guide with people who use a competitor product now. It finds why they chose it, the habits and costs that keep them, and the conditions to switch.
- Length
- 30 min
- Questions
- 15
- People
- 10 to 15
- Sections
- 5
What this guide finds out
- The event that made the user choose the competitor, and the options they compared.
- The habits, data and integrations that keep the user with the competitor.
- The problems the user puts up with, and the workarounds for them.
- The conditions under which the user would switch, and who would make that decision.
When to use it
- You enter a market where most target customers already use a competitor.
- You lose deals to one competitor and do not know what users value in it.
- You plan a migration offer and must know what makes switching hard.
Who to talk to
People who used a named competitor product at least weekly for the last 3 months. Talk to 10 to 15 people. Each interview takes about 30 minutes.
Screener for this guideCompetitor User Screener: Recruit People Who Use a Rival ProductUse this screener to find active users of a competitor product. It hides which company runs the study and checks use with a feature that the competitor does not have.The discussion guide
Each question has a probe note. The note tells the moderator, a person or an AI, what to do with the answer.
Warm-up
3 minLearn the role of the participant and the place of the product in their work.
Tell me about your role and the work you do with the product.
ProbeAsk for the task they do most often in it. Record the answer as context.
How long have you used it, and how many people on your team use it?
ProbeDo not ask a follow-up. Record the answer as context.
The choice
8 minRebuild the decision to start with the competitor.
What did you use before this product, and what happened that made you look for something new?
ProbeAsk for the specific event. If they say they were the first to use any tool, ask how they did the task before.
Which other options did you look at, and how did you compare them?
ProbeAsk which option was the last one they removed, and why. Do not name your own product.
What made you choose this one in the end?
ProbeIf they give a feature, ask what it let them do. If they give price, ask what they compared it with.
What were you worried about before you started?
ProbeAsk if the worry came true. Record the answer as an anxiety.
Life with the product
8 minLearn what users value and what they put up with.
What would you miss most if the product was gone tomorrow?
ProbeAsk for a recent time when that part helped them. Ask what they would do without it.
What annoys you about it?
ProbeAsk how often it happens and what they do about it. Record each workaround.
What other tools is it connected to, and what data do you keep in it?
ProbeAsk what would happen to that data and those connections if they left.
Conditions to switch
8 minFind the conditions and the people that a switch depends on.
Have you thought about leaving the product? What started that thought?
ProbeIf yes, ask what stopped them. If no, ask what would need to happen to make them think about it.
If you had to move to a different product, what would be the hardest part?
ProbeAsk about time, data, training and contracts. Ask who would do the work.
Who would need to agree to a switch?
ProbeAsk what that person cares about most. Ask when the next contract or renewal date is.
What would a new product need to do on the first day for you to switch?
ProbeAsk for one condition, not a list. If they say "be cheaper", ask how much cheaper and why that amount.
Close
3 minCollect the last details.
If you could ask the makers of the product for one change, what would it be?
ProbeDo not ask a follow-up.
Is there anything else about your choice of tools that you want to tell me?
ProbeThank them and end the interview.
Example finding
Most users would accept a better product only if it imported years of past records from the competitor.
“Everything from 2019 is in there. If I lose that, I lose the reason I keep the tool. Moving is not worth it.”
Mistakes to avoid
- Do not name your own product before the end. Participants then compare it with the competitor and stop describing their own experience.
- Do not ask "Would you switch?". Almost everyone says maybe. Ask what must happen first and who decides.
- Do not recruit people who tried the competitor once. Weekly users know the habits and costs that keep people there.
- Do not count complaints as reasons to switch. Users put up with many problems when switching costs are high.
Analyze the answers
Analysis templateJobs to Be Done Forces of Progress: Codebook for Switch InterviewsUse this codebook on jobs to be done switch interviews. It has two layers: the four forces for and against a switch, and the stages of the switch timeline.Questions
Use a screener that asks which tools people use and how often. List the competitor among other names, so the right answer is not obvious. Ask for a detail that only real users know.
Yes, if you ask about their own experience. Do not ask for confidential information about their employer or the competitor. Tell them who runs the study if they ask.
A switching cost is the time, money, data or risk that a move to a new product needs. High switching costs keep users with a product that they do not like.
Start with 10 to 15 users of one competitor. If you study two competitors, recruit a separate group for each.
Let the AI moderator ask these questions
The AI moderator interviews screened people by voice or text. Each claim in the study report links to its clip. The first 3 interviews are free.