Product thinking and discovery
Switch interviews
Reconstruct the last time someone hired or fired a product. Past timelines beat hypothetical "would you switch?"
A switch interview (or timeline interview) reconstructs how someone came to hire — or fire — a product. You are not pitching. You are reconstructing a timeline: first thought → passive looking → active looking → decision → using → (maybe) regretting.
Hypothetical "would you switch to X?" answers are weak. Stories of actual switches are strong. Use the same discipline as the Mom Test — see user research.
Concept
A switch interview is a past-tense walkthrough of a real hiring or firing. You want energy and specificity: what happened that day, what they used before, what almost made them stay, who else was in the room.
Walking through the prompts
Useful prompts:
- Walk me through the last time you started using [product / workaround]. What was going on that day?
- What were you using before? What almost made you stay?
- What else did you try? What did you hire when the milkshake was not available?
- When did you first think "I need something different"? What happened?
- Who else was involved in the choice? What were they worried about?
- If you fired a previous tool, what job was it failing?
Synthesize across interviews: do people describe the same job in different words? Where do push, pull, anxiety and habit show up? Which competitors (including spreadsheets) keep appearing?
Your real competition is often not the named rival on a G2 grid.
| Competitor type | Example | Implication |
|---|---|---|
| Direct product | Salesforce vs HubSpot | Feature and price wars; differentiation must map to the job |
| Adjacent product | Spreadsheet vs lightweight CRM | Win on speed-to-job, not enterprise checkbox parity |
| Workaround | Email + calendar + memory | Automate the ugly glue; anxiety of migration is high |
| Non-consumption | Doing nothing; enduring the pain | Must increase push awareness or make pull vivid |
| Hiring a human | VA, accountant, agency | Price against human time; trust and error modes differ |
Christensen emphasized non-consumption: people who have the job but hire nothing. They are not in your funnel yet. Beating them requires making the job and the progress obvious — not out-featuring a rival they do not use.
Workarounds deserve respect. A spreadsheet CRM is flexible, free and familiar. Your product must beat it on a specific job dimension (pipeline hygiene, multiplayer, mobile) while lowering anxiety (import, export, familiar metaphors).
Common mistakes
- Pitching in the interview. You will hear politeness, not a timeline.
- Asking hypotheticals. "Would you switch?" is cheap talk.
- Competitor lists that skip spreadsheets and nothing. Those are the real hires.
Check yourself
A prospect says "we'd love something like this." What do you ask instead?
Walk me through the last time you started using what you use now. What happened that day?
Who is a CRM's most common competitor in early interviews?
The spreadsheet — or doing nothing. Not only the named rival.
Key takeaways
- Reconstruct real hiring timelines. Prefer past behavior over hypotheticals.
- Listen for the same job in different words, and for all four forces.
- Competition includes workarounds, humans and non-consumption.
Further learning
Next, write the job so delivery cannot gut it: job stories.
Related
Jobs to be done
What customers hire a product to do — and how JTBD reframes competition and features.
Forces of progress
Push and pull move people toward a new product. Anxiety and habit hold them. Great products fail when the last two win.
User research
Interviews that avoid false positives, usability tests with five users, and synthesizing findings. Start here for the map.