The Ambiguity Navigation Rubric
Score behavioural answers on three axes: did they impose structure, seek inputs, and define milestones?
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 90%
Behavioural interview questions are only as good as the rubric behind them. This one converts 'tell me about an ambiguous situation' from a storytelling exercise into a three-axis scorecard: did the candidate impose structure and a path forward, did they actively seek inputs rather than declare certainty, and did they define the small milestones that would tell them whether the path was working. It is designed around the observation that the first path you chart is almost never the right one, so the real skill is chartering plus correcting, not chartering alone.
Origin
Jiaona Zhang (JZ), Head of Product at Webflow and a former Airbnb colleague of Lenny Rachitsky's, sharing her favourite interview question on Lenny's podcast.
Core principles
- 01The PM job is irreducibly ambiguous — no job description can enumerate what you will encounter.
- 02Complaining about ambiguity is disqualifying; imposing a path through it is the job.
- 03False certainty is as bad as paralysis — 'this is very clear, this is the way' signals someone who won't gather inputs.
- 04The first path charted is almost never right, so the ability to detect and correct beats the ability to decide.
- 05Milestones are the mechanism of correction: without them, there is no trigger to change course.
How to run it
- 1
Ask the behavioural prompt
Ask the candidate to describe a time they were in a genuinely challenging or ambiguous situation and how they navigated it. Keep it open — do not lead them toward the rubric.
Pro tip Prefer situations where the ambiguity was real (no clear owner, no clear success metric) over merely hard-but-well-defined problems.
- 2
Axis one — did they impose structure and a path forward?
Look for a candidate who did not just observe that they were swimming in ambiguity but actually put structure on it and charted a way forward. Absence of a path is the primary fail.
Pro tip Ask what the structure was concretely — a framing, a segmentation, a sequence of bets. Vagueness here means they narrated rather than led.
Watch out Beware the candidate whose 'structure' is just a retelling of what their manager decided.
- 3
Axis two — did they seek inputs?
Look for people actively seeking help and gathering inputs, rather than asserting 'yep, this is the way, this is very clear.' Certainty out of the gate is a red flag, not confidence.
Pro tip Probe who they went to and what changed as a result. A real input-seeker can name a view that shifted.
Watch out Do not confuse decisiveness with input-seeking. You want both; a candidate who only has the first will drive confidently off a cliff.
- 4
Axis three — did they define milestones?
Ask what the little milestones were that would tell them whether it was working or not working — the checkpoints that would prompt them to make a different decision. This is where most candidates fall down.
Pro tip The strongest signal is a candidate who names a milestone that fired negatively and describes the decision they changed as a result.
- 5
Grade the loop, not the outcome
Because the first path is so rarely correct, a candidate whose plan failed but who detected it early and corrected can outscore one whose plan happened to work. Score the navigation loop: structure, inputs, milestones, correction.
Pro tip Explicitly tell yourself the outcome is confounded by luck before you score. It stops halo effects from strong-sounding results.
In the wild
Zhang contrasts two archetypes. One candidate describes the ambiguity vividly and stops there — the answer is essentially 'oh no, we're swimming in ambiguity.' The other takes the same fog and lays out a path, explains how they learned their way into it, and names the checkpoints that would tell them to change course.
→ The second candidate passes on all three axes; the first fails on axis one regardless of how articulate the description of the chaos was.
Zhang's stated reason for weighting milestones so heavily is that the chance any charted path is right the first time is 'so rare.' The rubric therefore rewards the machinery of correction over the elegance of the initial plan.
→ Candidates who can articulate their working/not-working checkpoints get through; those with a single confident plan and no feedback loop do not.
Common mistakes
Asking the question without a rubric
'How do you handle ambiguity?' with no scoring axes just rewards the best storyteller. Without structure/inputs/milestones as explicit checks, different interviewers grade different things and the signal is noise.
Rewarding confident certainty
A candidate who says 'this is clear, this is the way' can read as decisive and strong, but Zhang treats it as a negative signal — it means they will not gather inputs and will not notice when the path is wrong.
Scoring the outcome instead of the loop
Because first paths are rarely right, a successful outcome may just mean the candidate got lucky. Grading on the result imports that luck straight into your hiring decision.
Is it for you?
Best for
Product, growth, and general-management hiring where the role is defined by ambiguity and cannot be specified on paper
Not ideal for
Well-defined execution roles with fixed specs, or highly technical screens where the primary risk is skill depth rather than navigation
From the transcript
“good answers are people who put structure and and a way forward through the ambiguity like that's what you look for”
“what are the little Milestones that make you say hey is this working is this not working”
From the episode
My favorite interview questions from 100+ guests