Methodology · 6 min read
JTBD Switch Interview Method
Evidence of the forces and triggers behind a purchase.
Bob Moesta, Chris Spiek, Clayton M. Christensen, Taddy Hall, Karen Dillon and David S. Duncan · View sources ↓At a glance
- Use this when
- You need to understand what caused a customer to leave an old solution and choose a new one.
- What you will work towards
- Evidence of the forces and triggers behind a purchase.
- Bring to the reading
- A specific decision from your work and the customer evidence you have so far.
What it is
A structured interview technique, developed by Bob Moesta and Chris Spiek at The Re-Wired Group, for uncovering the real "job" behind a purchase by reconstructing the timeline of a customer's switch from their old solution to the new one. Where the existing Jobs-to-be-Done Positioning Framework (Category 2) is about what to do with a job once you know it, the switch interview is the research method for finding it: a 45 to 60 minute conversation that walks backwards from the moment of purchase through the moment the old way first started to fail, surfacing the specific event, not a vague dissatisfaction, that pushed the customer to act. The technique treats a purchase decision as a story with a beginning, a middle, and an end, rather than a single rational moment of feature comparison, because in practice most B2B and consumer purchases are triggered by a specific "first thought" event that a features survey never captures.
When to use it
- You need to run the "Test with Customers" step of the JTBD Positioning Framework. That framework names switch interviews as its validation method; this entry is the fully worked-out version of how to run one.
- Win/loss interviews keep surfacing generic reasons ("better fit", "good timing") that do not explain what actually happened. A switch interview digs past the polite summary to the specific triggering event.
- A Voice of the Customer programme needs a deeper qualitative input, not another survey. Switch interviews are a source VoC synthesises, in the same way NPS and Win/Loss are, but they answer a different question: not "how do you feel" but "what exact sequence of events led you here".
- You are building positioning for a new category or an unfamiliar segment. A features-based competitive comparison assumes customers know how to evaluate you; a switch interview instead reveals what they were actually doing before you existed.
- Sales reports that deals close for reasons the marketing team cannot explain. Interviewing four or five recent buyers with this method usually surfaces a common triggering event the team had not put into messaging.
How to run it
- Recruit recent buyers, not long-tenured customers. Interview people who switched in the last one to three months; memory of the specific triggering event fades quickly, and a customer of two years will reconstruct a tidier, more rational story than the one that actually happened.
- Open with the moment of purchase and work backwards. Start with "Walk me back to the moment you decided to buy," then ask what happened just before that, and before that, building the timeline in reverse rather than asking "why did you buy?" directly, which tends to produce a rehearsed, rationalised answer.
- Find the "first thought" moment. Push for the specific event, a failed report, a frustrated conversation with a boss, a competitor's ad, that first put the idea of switching in the customer's head. This is usually weeks or months before the actual purchase, and it is the moment competitive messaging should target, not the purchase moment itself.
- Map the four forces of the switch. For each interview, note the push (what was wrong with the old way), the pull (what was attractive about the new way), the anxiety (what worried them about switching), and the habit or attachment (what made staying with the old way comfortable). A sale only happens when push plus pull outweighs anxiety plus habit; positioning that only addresses push and pull will keep losing to anxiety and habit unless those are named and addressed too.
- Ask about the people involved, not just the buyer. Who else weighed in, and what were they worried about? A champion's anxiety is often different from the economic buyer's, and both need addressing in different collateral.
- Capture verbatim language, not paraphrase. Record the interview (with permission) and pull direct quotes for the trigger event and the anxiety; the customer's own words about why they almost did not switch are usually sharper copy than anything the team would write internally.
- Synthesise across 8 to 12 interviews before generalising. One interview is an anecdote; a pattern across 8 to 12 recent switchers, with the same trigger event and the same anxiety showing up repeatedly, is a finding you can build a positioning hypothesis or a Message Architecture pillar on.
Cadence & ownership
PMM or a customer-insights function owns the interview programme and the synthesis. Run a batch of 8 to 12 interviews whenever positioning is being built or refreshed for a segment, rather than on a fixed calendar cadence; the method is project-based, triggered by a specific need (a repositioning, a new segment, a win-rate problem), not an always-on listening system in the way a Voice of the Customer programme is. Where a VoC programme already exists, feed synthesised switch-interview findings into its shared taxonomy so the trigger events and anxieties surfaced here sit alongside NPS and Win/Loss themes rather than living in a separate, forgotten document.
Example
Fictional field-service scheduling software Routewise struggled to explain why mid-market plumbing and HVAC companies switched to it from spreadsheets and paper schedules, since its competitive positioning assumed customers were comparing it feature-by-feature against other software. PMM ran ten switch interviews with customers who had signed up in the previous eight weeks. Working backwards from the purchase moment, eight of the ten interviews converged on the same first-thought trigger: a missed appointment that a customer complained about publicly, on a review site or directly to the owner, that the scheduler could have prevented had the office known about a technician running late. The push was reputational risk, not scheduling inefficiency; the pull was a live map view that showed technician location in real time; the anxiety was "will my technicians actually use another app"; and the habit was years of trusting a paper whiteboard the office manager could see at a glance. PMM rewrote the top-line message from "modern scheduling software" to "stop losing customers to missed appointments", added a specific onboarding step addressing technician adoption anxiety directly in the sales demo, and briefed sales to ask about a recent missed-appointment complaint in discovery calls. Over the following quarter, demo-to-trial conversion rose from 22% to 34%, and sales reported the missed-appointment question reliably opened the same trigger story the interviews had found.
Pitfalls
- Asking "why did you buy?" directly instead of walking the timeline. A direct why-question produces a rationalised, socially acceptable answer ("better value", "good fit") rather than the actual sequence of events. Recovery: always start from the purchase moment and move backwards event by event; if the conversation drifts into generic reasons, bring it back to "and what happened right before that?"
- Interviewing long-tenured customers instead of recent switchers. Memory of the specific trigger fades within a few months, and long-tenured customers reconstruct a cleaner story that has drifted from what actually happened. Recovery: set a hard recruiting window (purchased in the last one to three months) and decline interviews outside it, however willing the customer is to talk.
- Generalising from one or two interviews. A single vivid trigger story is memorable and tempting to build a whole positioning pivot on, but it may be an outlier. Recovery: hold off on any positioning change until 8 to 12 interviews show the same trigger, force, or anxiety repeating, and note how many of the sample described it, not just that one customer did.
How the ideas connect
Choose where to go next
Make it useful
Bring it back to your work.
Name one decision this guide could help you make. Write down the evidence you need, the output you would produce, and how you would know it was useful.
Check your understanding
Practise applying JTBD Switch Interview Method in five short scenarios.
5 practical scenarios. Choose an answer, explore the reasoning, and revisit the guide whenever you need.
Sources
- Bob Moesta and Chris Spiek developed and popularised the switch interview technique through The Re-Wired Group's client work and public training; see their write-up of the technique's best-known worked example, "The Mattress Interview".
- Clayton M. Christensen, Taddy Hall, Karen Dillon & David S. Duncan, Competing Against Luck (2016), which documents the Mattress Interview case in full.
← All entries in Market & Customer Understanding · Try the category quiz