How to Run a Switch Interview: The Timeline That Reveals Real Motivation

A switch interview reconstructs the exact chain of events that led a customer to fire their old solution and hire yours, working backward from the moment of purchase through first thought, passive looking, active looking, and deciding. It beats asking "what do you want" because people misremember their motivations but can accurately recall specific moments, dates, and conversations.

Quick answer: Interview a recent switcher (someone who bought in the last 30-90 days) and rebuild their timeline in five moments — first thought, passive looking, active looking, deciding, consuming — then tag each moment against the four forces of progress: push, pull, anxiety, and habit.

What a Switch Interview Actually Is (and Why It Beats Asking Customers What They Want)

A switch interview is a structured retrospective conversation with someone who recently stopped using one product and started using another. Instead of asking about preferences, you ask them to narrate the actual sequence of events — what happened first, what happened next, who said what. It is the core interviewing technique inside Jobs-to-Be-Done research.

The technique traces back to Bob Moesta and Chris Spiek, who developed it over two decades of consulting work later documented in Moesta's book Demand-Side Sales 101 and in Clayton Christensen's Competing Against Luck. Their argument, backed by hundreds of purchase-decision interviews across categories from mattresses to milkshakes, is simple: stated preferences are unreliable, but episodic memory of a specific event is not.

This is the same insight behind Rob Fitzpatrick's The Mom Test — people are polite liars about hypotheticals but honest narrators of things that actually happened to them. Ask "would you use a tool like this?" and you get flattery. Ask "walk me through the Tuesday afternoon you cancelled your old subscription" and you get truth, because you're asking for a memory, not an opinion.

If you're new to the underlying framework, it's worth grounding the switch interview inside the broader discipline first — see our complete guide to Jobs-to-Be-Done for the theory before you run your first session. The switch interview is simply the fieldwork that fills in that theory with real evidence.

Why "what do you want" fails

When you ask customers what they want, you get one of three unhelpful answers:

• A feature request copied from a competitor they already admire
• A vague aspiration ("something simpler") with no operational meaning
• A socially desirable answer that flatters the interviewer, not the truth

None of these tell you what actually moved someone from thinking about a change to paying for one. Only a reconstructed timeline does that, because it forces both of you to confront the actual causal chain rather than a post-hoc justification.

The Timeline: Five Moments in Every Switch

Every purchase decision, no matter how mundane, passes through five recognizable moments, and your job as an interviewer is to locate each one on the customer's actual calendar. Naming the moments turns a vague "eventually I just decided to switch" into a dated, causal sequence you can compare across interviews.

First thought

This is the earliest moment the idea "maybe I need something different" entered the customer's head — often months before any real search began. It is frequently triggered by an external event: a new hire, a breakup, a broken washing machine, a bad quarter. Ask for the scene, not the sentiment: "Where were you? What had just happened?"

Passive looking

The customer isn't actively shopping yet, but they've started noticing. They see an ad differently. A colleague mentions a tool in passing and it lands. This stage can last weeks or years and is where push (dissatisfaction with the status quo) usually first shows itself as a nagging, low-grade irritation.

Active looking

Something tips the customer from noticing to searching. They open a browser tab, ask a peer for a recommendation, book a demo. This is the moment worth dating precisely, because it usually coincides with a specific triggering event — what JTBD practitioners call the struggling moment.

Deciding

The customer compares options, negotiates internally (or with a boss, spouse, or procurement team), and commits. This is where anxiety about the new choice and habit (the pull of the status quo) fight it out loudest, and where most interviewers stop probing too early.

Consuming

The switch doesn't end at purchase. Onboarding, first use, and the first moment of regret or relief all shape whether the customer would switch again or churn back. If you want to map this stage in more visual detail after the interview, our guide to customer journey mapping is a useful companion — but note a journey map documents the intended experience, while a switch interview documents what actually happened to one real person.

Treat the five moments as a spine, not a script. Customers will jump around in time as they remember things — your job is to keep placing their answers back on the timeline, not to force them through the stages in order.

The Question Bank: Organized by the Four Forces of Progress

Every switch interview answer eventually maps to one of four forces described in Christensen's Forces of Progress model: two forces pushing the customer toward change, and two forces holding them back. Organizing your questions by force — rather than by timeline stage alone — keeps you from missing the anxieties and habits that quietly kill deals.

Use this table as a checklist during the interview, not as a survey to read aloud. If a customer's story is heavy on push and pull but light on anxiety and habit, you're probably only getting half the story — and half the story is what leads teams to build features nobody adopts.

Sequencing the questions inside the timeline

Layer the four forces onto the five timeline moments rather than asking about them separately:

1. Start with first thought and ask push-oriented questions about the triggering event.
2. Move to passive looking and ask what pulled their attention without them actively searching.
3. In active looking, ask what specifically prompted the search to become active.
4. In deciding, ask about both anxiety (what almost stopped them) and habit (what they'd miss).
5. In consuming, ask whether the anxiety was justified and whether the habit was hard to break.

This sequencing keeps the conversation chronological for the customer while giving you complete force coverage for your analysis.

Running the Interview: Recruiting Recent Switchers and the Follow-Up That Surfaces Anxiety

You get usable data only by interviewing people who switched recently — inside the last 30 to 90 days — because memory of specific events decays fast and gets reconstructed to fit a tidier narrative after that window. Recruit through purchase records, support tickets, or churn/win logs, never through open panels of "anyone interested in the category."

Recruiting criteria that actually work:

• Someone who completed the switch in the last one to three months
• Someone who can name the specific old tool or approach they replaced
• A mix of "happy switchers" and "regretful switchers" — both carry signal
• One person per interview; group interviews destroy the timeline reconstruction

Open the interview by asking permission to go slowly and by explaining that you're not evaluating them. Then ask a single opening question: "Tell me about the day you decided to buy this." Let them start anywhere — you'll place it on the timeline as they talk.

The probing follow-up that surfaces anxiety

Anxiety is the force interviewees are least willing to volunteer, because admitting fear feels like admitting they might have made a bad choice. The single most useful follow-up in a switch interview is asking about the moment just before commitment, when the decision was still reversible.

Interviewer: "You said you had the new tool open in one tab and your old spreadsheet open in the other for almost a week before you actually migrated. What was happening during that week?" Customer: "Honestly, I was scared I'd lose the formulas my old boss built. I didn't tell anyone I was stalling." Interviewer: "What would it have cost you if that fear had come true?"

That last question — "what would it have cost you" — is the probe that turns a vague hesitation into a quantifiable anxiety you can design against, whether through migration tooling, a rollback option, or better onboarding copy. Ask it every time you sense hesitation in the story, even if the customer downplays it the first time.

Common Mistakes That Turn a Switch Interview Into a Survey

Most switch interviews fail not because the interviewer asked the wrong questions but because they let the conversation drift into hypotheticals and generalities, which is exactly the mode the technique is designed to avoid. Watch for these failure patterns in your own transcripts.

• Asking about the future instead of the past. "What would make you switch again?" invites fiction. "What made you switch last time?" invites memory.
• Accepting the first answer as the real reason. The first reason a customer gives is almost always the sanitized, socially acceptable one — keep asking "and then what happened?"
• Skipping the anxiety and habit questions. Interviewers naturally gravitate to push and pull because they're positive and easy to talk about; anxiety and habit require more patience to extract.
• Interviewing too many people too shallowly. Five deep timeline interviews with recent switchers beat fifty shallow surveys — this is qualitative pattern-finding, not statistical sampling.
• Losing the causal chain. If you can't draw a line from first thought to consuming with dates and triggers, you don't have a switch interview yet; you have a testimonial.

Tony Ulwick's Outcome-Driven Innovation work at Strategyn makes a related point from the opposite direction: customers are consistently better at describing desired outcomes and specific struggles than at describing solutions. The switch interview is the fastest route to those outcomes, because it locates the exact moment the struggle became unbearable enough to pay to fix.

From Raw Timeline to a Jobs Model You Can Act On

A switch interview is only valuable once its raw narrative gets translated into something your team can prioritize against, which means converting forces and struggling moments into structured job statements and ranked opportunities. Treat the interview as raw material, not a deliverable in itself.

Once you've tagged a transcript with push, pull, anxiety, and habit moments, convert the clearest struggling moment into a proper job statement using the standard when / I want to / so I can structure — our guide on writing a JTBD job statement walks through the exact format.

A well-formed statement is what survives contact with a roadmap review; a paraphrased quote from an interview usually doesn't. If you've ever watched a sharp customer insight get flattened into a generic backlog ticket, our piece on why job statements survive the engineering handoff covers how to prevent that erosion.

With several interviews tagged, you can also feed the recurring outcomes into an opportunity score to see which struggles are both important and underserved — see our breakdown of the opportunity score formula for the importance-minus-satisfaction math Ulwick's method uses.

Habit is often a systemic force — org charts, budget cycles, existing integrations — rather than a purely individual one. It's worth reading it through a wider lens using our systems thinking guide before you assume a single feature will break the loop holding a customer to the old way.

A simple tagging table to run after every interview

Run every transcript through this table before you touch a roadmap. Patterns across five or six interviews are far more trustworthy than a single vivid story, no matter how compelling that story felt in the room.

Key Takeaways

• A switch interview reconstructs the actual, dated sequence of events behind a purchase decision instead of asking customers to predict or explain their own motivations.
• The five timeline moments are first thought, passive looking, active looking, deciding, and consuming — always ask "where were you" and "what happened next," not "why."
• Every answer maps to one of four forces from Christensen's Forces of Progress model: push, pull, anxiety, and habit — and anxiety is the one interviewers most often skip.
• Only interview recent switchers, ideally within 30-90 days of the decision, and interview them one at a time to preserve the causal chain.
• The probing follow-up "what would it have cost you if that fear had come true" is the single most reliable way to surface hidden anxiety.
• Raw interview transcripts are only useful once converted into job statements and scored opportunities — the interview is fieldwork, not the deliverable.