Gavel Gavel
Experts Skills
Cited from real sources 7 min read Updated May 2026

A research method by Bob Moesta

Bob Moesta's Switch Interview for Jobs-to-be-Done Research

The Switch Interview is Bob Moesta's method for finding out who your product is actually for and why people really buy it. Moesta co-created Jobs to Be Done with Clayton Christensen. The move is to stop asking customers what they want and instead interview people who recently switched, reconstructing the timeline of the decision: the push that made them stop, the pull toward something new, the anxiety of the unknown, and the habit of the old. What people say they want is unreliable. What they actually did, and the forces around it, is the truth.

The line that reframes every user interview

"Bitching ain't switching."

People complaining about their current tool tells you nothing. Only the people who actually changed can tell you why.

Bob Moesta on Lenny's Podcast The ultimate guide to JTBD Watch at 36:58

The framework

People hire products to make progress

Start from the premise underneath the whole method. People do not buy products because the features are good. They hire a product to make progress in a situation, and they fire whatever they were using before. If you do not know the progress someone was trying to make, you do not know who your product is for, no matter how many feature requests you have logged.

Most founder research fails because it asks the wrong person. Surveying current users produces a wishlist; asking prospects what they would pay produces a polite fiction. The Switch Interview targets someone who recently made a change, hired something new, and fired something old. That switch is a real event with a causal story.

The engine of the method is the Four Forces of Progress. Two push toward change: the struggling moment they are in, and the pull of the outcome they want. Two hold them back: the anxiety of the new, and the habit of the present. A switch only happens when push plus pull beats anxiety plus habit. On Lenny's Podcast, Moesta names the hidden half of that equation:

There's this waterline, that there's these other forces, and there's two other forces. Every time I show somebody something new, it actually creates anxiety, anxiety of the new.
Bob Moesta on the Four Forces Watch at 12:31

Founders obsess over push and pull and ignore anxiety and habit. That is why a clearly better product still loses: the held-back forces were stronger than anyone measured. The Switch Interview exists to surface all four.

How to apply it

How do you run a Switch Interview?

Six moves. The skill is not the script, it is refusing to accept the first easy answer and reconstructing the decision moment by moment.

  1. 1

    Recruit people who actually switched.

    Do not interview happy current users or cold prospects. Find someone who recently hired your product or a competitor and fired something else. The recent switchers are the only ones who can narrate a real decision instead of guessing.

  2. 2

    Anchor on the struggling moment.

    Go back to when the old way stopped working. What was the first moment they thought there had to be a better way? The struggle is the seed of the demand, so do not skip past it to the purchase.

  3. 3

    Reconstruct the timeline, not the opinion.

    Walk the decision forward in time: first thought, passive looking, active looking, the trigger, the purchase, the first use. Ask where they were and what else was going on, not what they think in the abstract.

  4. 4

    Map all four forces explicitly.

    For every switch, name the push of the struggle, the pull of the new outcome, the anxiety of the new thing, and the habit of the old. The two you are tempted to skip, anxiety and habit, are usually why deals stall.

  5. 5

    Bracket and play it back to break easy answers.

    When someone gives a thin answer, offer two wrong extremes so they correct you, then replay their story back to them. The contradiction is where the real reason lives, not the first thing they said.

  6. 6

    Cluster switches into jobs, then build for the job.

    After enough interviews, the same struggle keeps recurring. Group switches by the progress people were making. That cluster, not a persona or a feature list, is who the product is for.

If I've been using Tide for 20 years and I ask you why do you hire Tide, you just make it up, you have no idea why you use Tide. But if you switch from Tide to Gain, or Gain to Tide, you can tell me that story very detailed.
Bob Moesta on why switchers are the only reliable source Watch at 53:25

This is the whole reason the method targets switchers. A long-time user invents a rationalization on the spot. Someone who just changed remembers the friction, the trigger, and the moment of decision in detail, because it was recent and it cost them something.

Boundary conditions

When it works, when it fails

Works best when

  • There is a real switching event to reconstruct, a hire and a fire that already happened
  • You can reach people within weeks of the decision while the timeline is still vivid
  • You want the causal reason behind a purchase, not a feature wishlist
  • The category has friction and anxiety, so the held-back forces actually matter

Fails when

  • You interview people who only complained but never actually switched
  • You accept the first stated preference instead of reconstructing the timeline
  • The product is so new there is no prior behavior to fire and compare against
  • You want statistical sizing; this is qualitative and causal, not a survey

There is a real disagreement inside Jobs to Be Done worth knowing. Moesta runs a tactical, qualitative version built on interviewing switchers and surfacing the forces. The Tony Ulwick lineage runs a more theoretical, quantitative outcome-driven version. Both call themselves JTBD. On Lenny's Podcast, Moesta draws the line on what he is and is not doing:

Study struggling moments, because at some point that's where we need the innovation the most. Think about the progress people are trying to make: what is their standard, not your standard.
Bob Moesta on what to do with the interview Watch at 58:34

The honest caveat: this method tells you why the people you talked to switched. It does not tell you how many of them exist. Pair the Switch Interview with sizing work before you bet the roadmap on a job you only heard described in a dozen rooms.

The receipts

Where Moesta discusses this

12:31
Timestamp

Lenny's Podcast · The ultimate guide to JTBD

The Four Forces and the hidden half

There's this waterline, that there's these other forces, and there's two other forces. Every time I show somebody something new, it actually creates anxiety, anxiety of the new.
24:57
Timestamp

Lenny's Podcast · The ultimate guide to JTBD

Why study people who switch

One of the things that I've been doing is I've been studying people for the last 10 years around why they switch from one company to another to literally understand the jobs of jobs.
36:58
Timestamp

Lenny's Podcast · The ultimate guide to JTBD

Bitching ain't switching

I need to talk to people who did something and tried, and though they might have failed, what made them try. So the phrase I have is, bitching ain't switching.
53:25
Timestamp

Lenny's Podcast · The ultimate guide to JTBD

Why switchers remember the real story

If I've been using Tide for 20 years and I ask you why do you hire Tide, you just make it up. But if you switch from Tide to Gain, you can tell me that story very detailed.

Useful? Pass it to a founder who still cannot say who their product is for.

Want the full playbook?

Get 108 product & growth frameworks.

35 frameworks 20 rules 45 heuristics & principles 52 operators

From Jen Abel, Jason Lemkin, Elena Vera, and 49 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

Related frameworks

Retention

ICP and Churn Diagnosis

Jason Lemkin

Most SaaS churn is not a product problem. It is a customer problem: you sold to the wrong ICP.

Shipping

Do Things That Don't Scale

Paul Graham

Startups don't take off by themselves. Recruit the first users by hand and do the unscalable work that delights them.

Shipping

Launch-Jankiest Rule

Garry Tan

Ship the jankiest MVP that still provides value. If users tolerate it, the problem is real.

Positioning

Sales Pitch Framework

April Dunford

Positioning is what you are. The sales pitch is how you say it to one buyer: setup, then differentiated value.