Jobs-to-Be-Done Interrogation (The Big Hire)
Interrogate the moment someone first hired your product to find the real cause of usage
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 83%
A causation-hunting interview technique: instead of asking what features people want, reconstruct the exact moment and context in which they first decided to use your product. Use it to understand why customers really hire (or fire) you, and to separate utility jobs from the emotional jobs teams routinely under-weight.
Origin
Stein cites Clayton Christensen's 'Competing Against Luck' as a favorite and describes Christensen's interview-as-interrogation method as the first of his core product principles — deeply understand people.
Core principles
- 01Don't think of users as 'using' your product — think of them as hiring it to do a job (Christensen; the drill-vs-hole idea via Theodore Levitt).
- 02The most critical information is the context of the 'big hire' — the moment they first decided to use it.
- 03There are utility jobs and emotional jobs, and people usually discount the emotional ones.
How to run it
- 1
Reconstruct the first-use moment
Interrogate a user about when they first hired the product: Where were you? In bed? At work? What were you doing? Keep asking why until you reach the trigger (reading the newspaper, talking to a spouse).
Pro tip Treat it as an interrogation, not a survey — chase the causal chain rather than accepting the first answer.
- 2
Isolate the big hire
Pinpoint the aha moment when they first decided to use it — Christensen's 'big hire.' That is the causal information that explains adoption; study it and you'll build far better than by building things that just sound cool.
- 3
Name the utility AND emotional job
Ask what the real job is — often emotional, not just functional. For Close Friends the job wasn't 'post to a small list'; it was feeling connected to friends, closed only when a DM came back.
Pro tip Explicitly ask what emotional job is being done; teams default to utility and miss the driver.
Watch out Underweighting the emotional job leads you to optimize the wrong thing entirely.
In the wild
By interrogating why people wouldn't post to Stories, the team found a recurring 'audience problem' (an ex, a teacher, a judgy friend watching). The real job was vulnerable connection — sharing 'hey, I'm lonely, who's up?' — completed only when a friend DM'd back.
→ Reframing the job around connection (not a list feature) drove the redesign that turned a total flop into one of Stories' most popular features.
Common mistakes
Asking what features people want
Feature requests don't reveal causation. The context of the first hire does — skipping it leaves you 'building things that sound cool.'
Discounting the emotional job
Stein notes people usually discount emotional jobs; Close Friends looked like a utility (a list) but was really an emotional connection product.
Is it for you?
Best for
PMs and founders diagnosing why a product is or isn't being adopted
Not ideal for
Purely quantitative optimization where you already understand the job and just need to tune it
From the transcript
“Think of users as hiring you to do something for them.”
“people people don't want a quarter inch drill they want a quarter inch hole”
“there are utility jobs and there are emotional jobs. People usually discount the emotional ones a lot”
From the episode
Inside Google's AI turnaround: The rise of AI Mode, strategy behind AI Overviews, and their vision for AI-powered search
Robby Stein (VP of Product, Google Search)