Prioritization interview questions
Prioritization questions a Product manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.
A useful-sounding feature does not serve this quarter’s bet. What do you say?
The strongest answer: No, here is the bet, and here is a place to park the idea — I do not smile-yes and starve the team
Why it works: Exactly. A clear no plus a parking lot. Smile-yes is how roadmaps become luggage.
- Say no against the bet.
- Park the idea.
- Do not smile-yes.
- Do not no without a reason.
A team labels a release with MoSCoW. What do the four labels mean, and which one does the work?
The strongest answer: Must, Should, Could and Won’t-this-time. Must means the release is not worth shipping without it, and the label that does the work is Won’t, because it is a decision written down
Why it works: Exactly — if Must is not “the release fails without this”, the method is a ranked list with nicer words.
- Must: the release fails without it.
- Should: painful, not fatal.
- Could: the first thing dropped.
- Won’t: agreed, written, this release.
The date is real; the list is not. What do you cut with?
The strongest answer: The outcome: what must be true for the user that day — I cut the rest in the open, I do not silently hope
Why it works: Exactly. Outcome-first cuts, visible. Tests, comms, and unpaid nights are how you ship a surprise.
- Cut against the day’s outcome.
- Cut in the open.
- Do not cut tests as the default.
- Nights are not a plan.
A peer wants to rank the backlog with RICE and ship the top number. Pushback?
The strongest answer: RICE is a conversation starter — the scores are guesses I will not treat as a law, and I will not invent reach
Why it works: Exactly. A prompt, not a court. Fake reach and vibe-only are two other courts.
- RICE starts a talk; it is not law.
- Scores are guesses.
- Do not invent reach.
- Do not hide in vibe-only either.
The team has plotted thirty ideas on an impact–effort matrix and wants to spend the quarter on the quick-wins corner.
What do you say?
The strongest answer: Take some quick wins, but both axes are guesses — impact is our belief and effort is one estimate. A quarter of only cheap wins means the bet that mattered never starts
Why it works: Right — the matrix starts a conversation. Sorting by cheapness is how a team stays busy and moves nothing.
- Both axes are guesses.
- Say which impact is tested.
- Reserve room for the big bet.
- The matrix informs; you decide.
The sprint is already full. A “small” ask arrives. What do you do?
The strongest answer: Name what comes out if this goes in — I do not smile and keep the old promise
Why it works: Exactly. In means out. Small-is-free and hidden flexibility are how sprints become fiction.
- If it goes in, something comes out.
- Small ≠ free.
- Do not keep two demo lists.
- Do not hide the trade.
A decision is cheap to reverse. How should that change the process?
The strongest answer: Move faster and write a lighter record — I do not run a steering committee for a copy change
Why it works: Exactly. Door type sets the process. Committees and fake-irreversible are how you stall the cheap ones.
- Two-way doors get a lighter process.
- Do not committee a copy change.
- Do not wait for perfect research.
- Do not fake irreversible to look careful.
The backlog is 400 tickets. What do you do first?
The strongest answer: Kill or park anything older than a written age, then order the rest by the bet — I do not groom 400 as a lifestyle
Why it works: Exactly. Age out, then order. 400-as-demand is a museum.
- Age-out, then order by the bet.
- Do not groom 400 as a ritual.
- Keeping everything hides the bet.
- Volume ≠ demand.
How do you talk about several bets without fake expected-value math?
The strongest answer: What each is for, what would kill it, and how much attention it gets — I do not invent an EV spreadsheet
Why it works: Exactly. Purpose, kill, attention. Invented NPV and little-all are how you starve the real bet.
- Purpose, kill rule, attention.
- No invented EV/NPV.
- Do not rank by slide beauty.
- Do not sprinkle all bets equally.
How does opportunity scoring work, and what is it good for that a RICE score is not?
The strongest answer: You ask customers how important an outcome is and how satisfied they are with it today; the gap between the two is the opportunity. It ranks unmet needs rather than our own feature ideas
Why it works: Right — important and badly served is the interesting quadrant, and scoring outcomes can point at a need nobody has proposed a feature for.
- Importance minus satisfaction is the gap.
- Score outcomes, not features.
- Chase important and badly served.
- It is survey data — judge it.
You pick bet A. What do you say about B?
The strongest answer: What we will not learn, and who we will disappoint — I do not pretend A is free
Why it works: Exactly. Cost in the open. Silence, smears, and later-lullabies are how B returns as a ghost.
- Say what A costs: learning and people.
- A is not free.
- Do not smear B.
- Do not lullaby “later.”
Platform wants six months; a feature wants six weeks. How do you decide?
The strongest answer: Which stuck jobs the platform actually unblocks, and a thinner slice if the six months is a novel — I do not fund a platform with no user in the sentence
Why it works: Exactly. Jobs and a thinner slice. Always-either and 50/50 smiles skip the sentence with a user.
- Name the jobs a platform unblocks.
- Prefer a thinner slice to a novel.
- No user in the sentence → do not fund.
- Do not 50/50 to buy peace.