The Compelled Test (Storytelling as Product Signal)
After they describe a big problem, measure your own reaction — do you feel compelled to go work on it?
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 86%
An interview test that inverts the usual grading direction: instead of scoring the candidate's answer, you score your own reaction to it. Ask them to describe a big problem they worked on, then check whether you come away wanting to work on it. Because so much of a product leader's job is rallying people to a problem, the interviewer's felt pull is a direct, hard-to-fake measurement of the exact skill being hired for — regardless of how boring the problem sounds on the surface.
Origin
Yuki Yamashita, Chief Product Officer at Figma and former Head of Design at Uber, on Lenny Rachitsky's podcast. He pairs it with a second question about controversial product decisions.
Core principles
- 01The job is largely storytelling and communication — so test it live, not by proxy.
- 02Grade your own reaction, not the candidate's articulateness; the pull you feel is the unfakeable metric.
- 03A boring-sounding problem is the ideal test case — it removes inherent glamour as a confound.
- 04A great product person can make a problem feel existential and interesting, and can rally people to it.
- 05The paired controversy question tests whether they can hold and fairly represent both sides of a conflict.
How to run it
- 1
Ask for a big problem they worked on
Deliberately keep it plain: talk about a big problem you worked on. Do not ask for their most impressive or most successful project — the mundane framing is what makes the test valid.
Pro tip The less glamorous the problem sounds on the surface, the cleaner the read on their storytelling.
- 2
Run the thought experiment on yourself
Coming out of their answer, ask yourself: do I feel compelled to work on that problem? That is the entire grading criterion. You are measuring the pull they generated in you.
Pro tip Do this immediately, before you start rationalising. The felt reaction decays fast under analysis.
Watch out Be honest about the pull. Interviewers who talk themselves into being compelled defeat the instrument.
- 3
Check whether they made it existential
A great product manager can take a dull-sounding problem and convey why it is existential for the business and genuinely interesting — and rally the team around it. Look for that transformation, not for the problem's inherent importance.
Pro tip Ask how they actually rallied their team. The answer tells you whether the framing was invented for you or used for real.
- 4
Pair it with the controversial-decision question
Ask them to describe a time they were part of a controversial product decision — what happened and what they did. It is revealing because they must set up the conflict, explain why the problem mattered, and represent both sides.
Pro tip Watch for the even-keeled delivery. Someone who can hold both perspectives without caricaturing the opposition has real perspective-taking ability.
Watch out A candidate who can only argue their own side is telling you how they will handle their first serious disagreement with you.
- 5
Score the composite as the storytelling signal
Combine the compelled test (can they pull people toward a problem?) with the controversy test (can they hold multiple perspectives fairly?). Together these cover the storytelling and communication core of the job.
In the wild
Yamashita's thought experiment is simply whether, coming out of the answer, he feels compelled to work on that problem. He notes that no matter how boring the problem sounds on the surface, a really great product manager can convey why it is so existential and so interesting, and can genuinely rally people around it.
→ The interviewer's own sense of pull becomes the score — a measurement of the exact capability (rallying a team to a problem) that the role requires day to day.
Asking about a controversial product decision is revealing because the candidate has to set up the conflict, explain why the problem was important, and represent both sides such that you understand why the conflict existed at all — and do it in an even-keeled way.
→ Candidates who can take on the different perspectives fairly reveal a great deal about themselves; those who flatten the opposing side reveal something too.
Common mistakes
Grading the problem instead of the telling
An interviewer who is impressed because the problem was inherently important has measured the candidate's past employer, not the candidate. The test only works when you separate the problem's intrinsic interest from the interest they generated.
Asking for their most impressive project
That framing lets a glamorous problem do the persuasive work. Ask for a big problem, plainly, and let the mundane ones through — they are the highest-signal test cases.
Letting the candidate caricature the other side
In the controversy question, a candidate who paints the opposition as obviously wrong has failed the perspective-taking test — even if their side was right. The signal is whether they can make you understand why the conflict genuinely existed.
Is it for you?
Best for
Interviewers hiring product and design leaders whose core job is rallying cross-functional teams to a problem through narrative
Not ideal for
Individual-contributor roles with no persuasion component, or interviewers who cannot reliably introspect on their own reactions
From the transcript
“describe to me a time when you're part of a controversial product decision”
“for me is always like coming out of that do I feel compelled to work on that problem”
From the episode
My favorite interview questions from 100+ guests