Blog / Research
Switch Interview Technique: A Step-by-Step Guide
Learn how to run a Switch Interview to reconstruct the exact moment a customer switched products — and surface the causal forces behind any JTBD purchase
On this page
- What Is the Switch Interview Technique?
- The Forces of Progress Framework
- How to Structure a Switch Interview: The Five Timeline Stages
- Recruiting the Right Participants
- Running the Interview: Questions, Probes, and Common Pitfalls
- Analysing and Activating Switch Interview Findings
- A Switch Interview in Practice: Agency Example
- Frequently Asked Questions
What Is the Switch Interview Technique?
A Switch Interview is a structured retrospective interview that reconstructs the exact moment a customer decided to replace one solution with another. A general jobs-to-be-done interviews for B2B SaaS session ranges across a user’s broader workflow and motivations. The Switch Interview is narrower: map the causal chain that led someone to fire their old solution and hire a new one.
The technique comes from Bob Moesta and Chris Spiek’s demand-side innovation work, developed alongside Clayton Christensen’s Jobs to Be Done theory. The core insight is that people do not buy products — they hire them to make progress in a specific circumstance. Switching, in JTBD terms, means firing the incumbent (whether that is a competitor, a manual workaround, or simply non-consumption) and hiring something new.
That framing matters because non-consumption is a legitimate “old solution.” A customer who built spreadsheets for five years before buying your tool is still a switcher — and their switching story is just as instructive as one who moved from a named competitor.
Use the Switch Interview technique when you need to:
- Validate a new product by understanding what demand already exists in the market
- Diagnose churn by interviewing customers who switched away
- Sharpen positioning by finding the exact language customers use when they felt the pull toward your solution
- Uncover demand triggers that your product discovery research has not yet captured
The Forces of Progress Framework
The Forces of Progress framework explains why switching is never just a rational cost-benefit calculation. Four forces act on every customer at once, and a switch only happens when two of them outweigh the other two.
Push is the pain or frustration with the current situation — the accumulating dissatisfaction that makes the status quo feel untenable. Pull is the attraction toward a new solution — the vision of a better outcome that draws the customer forward. These two forces accelerate switching.
Anxiety is the fear that the new solution might not work, or that switching will be costly, embarrassing, or disruptive. Habit is the gravitational pull of existing routines, integrations, and muscle memory. These two forces resist switching.
A purchase happens only when Push + Pull exceeds Anxiety + Habit. That arithmetic is why a customer can recognise a problem for months without acting: Push may be real, but Habit keeps them in place until a specific trigger tips the balance.
Each stage of the Switch Interview targets a specific force:
| Force | Interview focus |
|---|---|
| Push | First Thought and Passive Looking stages |
| Pull | Active Looking and Decision stages |
| Anxiety | Decision stage — “what almost stopped you?” |
| Habit | Ongoing Use — what they miss or have abandoned |
A simple pain/gain model captures Push and Pull but ignores the two resisting forces. That gap matters: in practice, the highest-variance force across participants is often Anxiety, which means messaging that addresses only pain and gain will leave a meaningful proportion of potential switchers stuck.
For a wider view of where this method sits, see our overview of jobs-to-be-done research methods.
How to Structure a Switch Interview: The Five Timeline Stages
The Switch Interview follows a narrative arc across five stages. They are not a rigid script — experienced interviewers move between them fluidly as the respondent’s story unfolds. Treat them as waypoints, not a checklist.
In a 60-minute session, a rough time budget looks like this:
Stage 1 — First Thought (8–10 minutes)
Surface the earliest moment the customer sensed something was wrong with their old solution. This is often months or years before the actual switch. The goal is not to find the trigger yet — it is to locate the seed of dissatisfaction. A useful prompt: “Cast your mind back — when did you first get the sense that what you were using might not be quite right?”
Stage 2 — Passive Looking (8–10 minutes)
Most customers do not move straight from dissatisfaction to active searching. There is a passive phase: half-noticing alternatives, storing away a colleague’s comment, bookmarking an article. This stage explores that low-intensity information-gathering. It maps primarily to Push — what kept nudging the customer without yet compelling action.
Stage 3 — Active Looking (10–12 minutes)
Something converts passive awareness into deliberate search. Reconstruct that trigger precisely. Was it an incident? A conversation? A deadline? Push peaks here, and Pull starts to enter — the customer begins comparing options with intent.
Stage 4 — The Decision (15–18 minutes)
This is the richest stage. Reconstruct the final choice: what tipped the customer across the line, who else was involved, and — critically — what almost stopped them. Anxiety surfaces most clearly here. Spend time on it.
Stage 5 — First Use and Ongoing Use (8–10 minutes)
Capture early post-hire experience. Did the new solution actually do the job? Regret or friction here can signal that the job was misunderstood at the point of sale. This stage also reveals residual Habit — what the customer still misses or works around from their old solution.
Leave a few minutes at the start for rapport-building and framing, and five at the end to clarify any ambiguous moments in the timeline.
Recruiting the Right Participants
The Switch Interview depends entirely on participants who can narrate a genuine, recent switching decision with enough detail to be analytically useful.
Ideal respondent profile: recent switchers who made the switch within the past 3–6 months. Memory degrades quickly for the kind of emotional and contextual detail the interview depends on. Avoid recruiting enthusiasts or early adopters who have reflected extensively on their decision — they tend to produce over-rationalised accounts that flatten the causal texture you need.
Decision involvement: confirm at screening that the participant personally drove or meaningfully influenced the switch. In B2B contexts especially, a user who had the product handed to them by an IT team is not the same as the champion who built the business case. Both perspectives have value, but they answer different questions.
Sample size: 6–10 switchers is typically sufficient to reach pattern saturation. Prioritise quality of recall and decision involvement over volume.
Sourcing channels: CRM segments filtered by sign-up or churn date, post-onboarding email sequences with a brief screening survey, in-product prompts triggered at the 30- or 60-day mark, and warm introductions via customer success teams. For churn research, an outbound sequence to recently churned accounts — framed as a “help us understand” request rather than a retention attempt — tends to achieve reasonable response rates.
Incentives: in B2B contexts, a charitable donation or a report summary often works better than a cash incentive, which can feel transactional. In consumer contexts, a voucher or direct payment is standard.
Consent and recording: always obtain explicit consent before recording. Tell participants that recordings are anonymised and used only internally. For detailed guidance on finding and screening the right people, see our post on how to recruit B2B interview participants.
Running the Interview: Questions, Probes, and Common Pitfalls
Open by setting the frame clearly: you are not here to evaluate the product or gather opinions. You want to hear the story of how the switch happened, told in as much detail as the participant can remember.
Opening question: “Take me back to the very first time you thought your old solution might not be working — what was happening at the time?”
That question does several things at once. It anchors the respondent in narrative mode, points them toward the earliest Push signal rather than the most recent event, and opens with circumstances rather than opinions.
Probing for specificity: when the respondent gives a general answer — “I was just frustrated with it” — probe into the concrete event behind the generalisation:
- “Walk me through that day.”
- “Who else was in the room?”
- “What did you do next?”
Specificity is the point. The causal forces live in the details, not in the summary.
Probing for Anxiety without leading: “Was there anything that almost stopped you from making the switch?” is a clean, non-leading probe. Avoid “Were you worried about the learning curve?” — that names the Anxiety rather than drawing it out.
Common pitfalls:
- Hypotheticals. “Would you switch again if the price increased?” produces opinion, not causal insight. The Switch Interview deals only in what actually happened.
- Opinion drift. Respondents slip naturally into evaluation mode — “I think the product is great because…”. Redirect gently: “That’s useful context — can you take me back to the moment when you first noticed that?”
- Early feature-steering. Resist the urge to ask about specific product features until late in the interview. Doing so narrows the respondent’s story prematurely.
B2B complexity: buying decisions in B2B often involve a champion, a budget holder, and an end-user who are different people. Map the stakeholder cast early in the interview and ask about each one’s role in the decision. A champion’s Pull story and a budget holder’s Anxiety story are both data — they just map to different forces.
Note-taking vs. recording: recording is preferable when consent is given, as it frees the interviewer to listen rather than transcribe. If recording is not possible, a second team member should take verbatim notes while the interviewer leads. Debrief within an hour of the session, before recall degrades.
Analysing and Activating Switch Interview Findings
After transcription, code each passage against the four forces. A simple force-tension map — Push and Pull on one axis, Anxiety and Habit on the other — gives you an at-a-glance view of where each participant’s switch was driven from and where it was most resisted.
Across participants, look for the struggling moment pattern: the specific combination of circumstance and emotional state that reliably precedes switching. When five out of eight respondents describe the same kind of pressure event as their First Thought trigger, that is a demand signal, not a coincidence.
Pay close attention to language clusters — the exact phrases customers use when describing the job they needed done. These are not just analytical data; they are positioning copy. If multiple respondents describe their old situation as “flying blind,” that phrase belongs in your messaging, not a paraphrase of it.
Identify the force with the highest variance across participants. Frequently this is Anxiety — some switchers overcame it easily, others nearly did not switch at all. High variance means that force is a design or messaging lever worth prioritising, because small changes to how you address it can meaningfully shift conversion or retention.
Outputs depend on the research question:
- For new product validation: a demand-side story and a revised value proposition canvas
- For churn research: a retention intervention mapped to the specific Anxieties or renewed Habits that drove departure
- For positioning: a narrative brief that replaces internal feature language with customer circumstance language
Share findings as a narrative timeline, not a bullet-point readout. Stakeholders need to feel the causal logic — the sequence from First Thought to Decision — to act on it. A list of themes strips that sequence out and leaves the “so what” ambiguous. Guidance on carrying that through to decisions is in our post on turning research insights into product impact.
A Switch Interview in Practice: Agency Example
On a recent engagement with a B2B software company in the project management space, we ran eight Switch Interviews with customers who had migrated from a legacy, on-premise tool within the previous four months.
The team expected Pull — excitement about the new product’s interface — to be the dominant force. The interviews told a different story. The most consistent First Thought trigger was not frustration with the old software’s features, but a specific organisational event: a change in team size that made the old tool’s licencing model suddenly feel disproportionate. Push was structural, not functional.
Anxiety was also higher than anticipated. Several participants described a near-abandonment point when they realised their historical data export would require manual reformatting. One participant called it “the moment I nearly talked myself out of it.”
That single insight — that data migration anxiety was close to blocking conversion for a meaningful share of switchers — led the client team to reprioritise an automated import feature that had been sitting low on the roadmap, and to add a migration support section to their onboarding sequence. Positioning shifted too: rather than leading with interface modernity, the team began leading with continuity — the idea that switching did not mean starting over.
Frequently Asked Questions
How is a Switch Interview different from a standard user interview?
A standard user interview explores attitudes, workflows, and feature needs across a broad topic area. A Switch Interview has a single, precise goal: reconstructing the causal story of why and how someone replaced one solution with another. It is retrospective, narrative-led, and maps every answer to one of the four forces of progress rather than to open-ended themes. The analytical frame is fixed from the start.
How many Switch Interviews do I need to run?
Six to ten recent switchers is usually sufficient to reach pattern saturation. Prioritise recency — the switch should have happened within the past 3–6 months — and decision involvement. A participant who drove or heavily influenced the switch will give you more causally useful data than one who was a passive recipient of someone else’s decision.
Can the Switch Interview technique be used for churn research?
Yes, with a small adaptation. Instead of interviewing customers who switched to your product, you interview customers who switched away. The same five-stage timeline applies, and the same four forces are in play — but the direction is reversed. You are now trying to understand what accumulated Push built against your own product, and what Pull something else exerted. The findings typically inform retention interventions and early warning indicators for customer success teams.
What makes a Switch Interview fail?
The most common failure modes are recruiting participants who were not meaningfully involved in the decision, allowing the interview to drift into opinion and evaluation, and asking hypothetical questions. A close second: analysing only Push and Pull while treating Anxiety and Habit as noise. When the resisting forces are ignored, the findings tend to produce feature requests and satisfaction scores rather than the causal insight the method is designed to surface.
About Glasgow Research — Glasgow Research helps B2B SaaS teams turn customer and market research into product decisions. Work with us.
Author
About Vadim Glazkov
Vadim Glazkov is the founder of Glasgow Research and a product research expert working with founders and B2B SaaS teams on customer interviews, JTBD, market validation, and decision-ready research.