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

The framework

People hire products to make progress

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.

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

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:

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 sources

Where Moesta discusses this