Product Manager
Prioritisation questions
186 questions on Prioritisation for product managers, easiest first.
Easy 51
- MoSCoW prioritisationeasy
- Why refine the backlogeasy
- What RICE stands foreasy
- Reach needs a time periodeasy
- Confidence in RICEeasy
- Effort in RICEeasy
- The quick wins quadranteasy
- Low value, high efforteasy
- A Kano must-be featureeasy
- A Kano performance featureeasy
- A Kano indifferent featureeasy
- A Kano reverse featureeasy
- What WSJF stands foreasy
- Job size in WSJFeasy
- A fixed-date deadlineeasy
- Urgent but not importanteasy
- Opportunity costeasy
- Roadmap columns without dateseasy
- Outcomes on a roadmapeasy
- Saying no to a requesteasy
- Agreeing criteria firsteasy
- When everything is P1easy
- Stack ranking a backlogeasy
- Bug severity and priorityeasy
- Technical debteasy
- Cutting scope for an MVPeasy
- A first filter for ideaseasy
- Limiting work in progresseasy
- A story map's first sliceeasy
- High power, high interesteasy
- The riskiest assumptioneasy
- Keep-the-lights-on workeasy
- Ready to be picked upeasy
- What a P0 meanseasy
- Timeboxing a taskeasy
- Using one scoring scaleeasy
- Jira rank and priority fieldeasy
- Old items in the backlogeasy
- Tasks on the critical patheasy
- Finish-to-starteasy
- Only picking easy itemseasy
- A decision logeasy
- Jobs to be doneeasy
- Tracing to a business objectiveeasy
- "We need it by Friday"easy
- Risk in a scoring modeleasy
- A payment bug and a typoeasy
- Prioritisation is never one-offeasy
- A Kano delightereasy
- The MoSCoW methodeasy
- Quick wins on a value–effort grideasy
Medium 79
- Comparing features with RICEmedium
- A big client demands a custom featuremedium
- Kano model categoriesmedium
- Working out RICE scoresmedium
- Working out ICE scoresmedium
- Working out WSJFmedium
- Cost of delaymedium
- Kano categories change over timemedium
- Weighted scoringmedium
- A RICE score with 50% confidencemedium
- When effort doublesmedium
- The RICE impact scalemedium
- How ICE differs from RICEmedium
- Ranking jobs by WSJFmedium
- Cost of delay divided by durationmedium
- How a Kano survey asksmedium
- Liked if present, fine if absentmedium
- Expected if present, disliked if absentmedium
- Work with a hidden cost of delaymedium
- Relative effort estimatesmedium
- Opportunity score from a surveymedium
- The Buy a Feature gamemedium
- The 100-dollar testmedium
- Jobs of the same sizemedium
- Mixing units for reachmedium
- Confidence for a hunchmedium
- What a score is formedium
- Shrinking a job to raise WSJFmedium
- Who gives which estimatemedium
- Arabic support before a UAE launchmedium
- Rare crash or common glitchmedium
- Splitting capacity into bucketsmedium
- Prioritising with OKRsmedium
- The HiPPO problemmedium
- A prospect wants one featuremedium
- Opportunity solution treesmedium
- A partner team is bookedmedium
- A regulator sets a datemedium
- Sizing an opportunitymedium
- A security hole is foundmedium
- Two items with the same scoremedium
- Weighting requests by revenuemedium
- Matching every competitor featuremedium
- A time-boxed spikemedium
- Promising dates on a roadmapmedium
- Switching mid-waymedium
- A few bugs cause most ticketsmedium
- Retiring a costly niche featuremedium
- Platform work with no direct usersmedium
- Scoring with three weighted criteriamedium
- Items stuck in progressmedium
- Finding the critical pathmedium
- Slack on a taskmedium
- Adding people to finish soonermedium
- Fast-tracking a projectmedium
- Which risk to tackle firstmedium
- New scope in a fixed-price dealmedium
- Ranking with a pairwise matrixmedium
- Classes of servicemedium
- Too many expedite itemsmedium
- Defects found in UATmedium
- Splitting a big itemmedium
- Deciding between themesmedium
- Sales made a promisemedium
- Ordering work to learn earlymedium
- Paying down debt with featuresmedium
- How often to review prioritiesmedium
- Waiting for sign-offmedium
- Expected cost of non-compliancemedium
- Working out reach from trafficmedium
- A feature that annoysmedium
- Yesterday's delightermedium
- Working out a RICE scoremedium
- Comparing two ideas with RICEmedium
- Working out an ICE scoremedium
- Weighted shortest job firstmedium
- Value lost by shipping latemedium
- The hidden cost of saying yesmedium
- The highest-paid person's opinionmedium
Hard 56
- The CEO's urgent featurehard
- Engineers want time for tech debthard
- Build, buy or partnerhard
- Reversible and irreversible decisionshard
- Total cost of two ordershard
- Time criticality near a deadlinehard
- Everyone's ideas score highhard
- Kano results split by segmenthard
- A small weight change flips the orderhard
- Big bets never get pickedhard
- A high scorer needs a low scorerhard
- A feature for the Diwali salehard
- Risky big bet or safe small onehard
- Testing before a big buildhard
- Improving a feature againhard
- Six months already spenthard
- Kano satisfaction coefficientshard
- How many pairwise comparisonshard
- Working out a weekly cost of delayhard
- Two VPs want different thingshard
- One team's metric versus the company'shard
- Estimates are often offhard
- Many custom enterprise askshard
- Which experiment to run firsthard
- When value per effort misleadshard
- The true cost of a client featurehard
- A vendor ends supporthard
- Accessibility as a requirementhard
- Too many projects at oncehard
- Three projects in parallelhard
- Only current customers askhard
- An internal tool to save ops timehard
- After a big outagehard
- How much to bet on new ideashard
- Running the team at 100%hard
- Two criteria that measure the same thinghard
- Deciding without all the datahard
- Two groups, two sets of mustshard
- Reading Fibonacci estimateshard
- A forecast with a rangehard
- Holding finished work for a big releasehard
- Why smaller batches pay offhard
- Value now or value laterhard
- A rule change or a revenue featurehard
- Shipping part of a featurehard
- "It is just a small change"hard
- Who has the final sayhard
- Scores from six months agohard
- A must-be item with no deadlinehard
- Ordering three jobs by CD3hard
- Ranking problems by how often they come uphard
- Marketing a feature everyone hashard
- A real problem, but not worth solvinghard
- Two segments, one roadmap slothard
- A year in, the bet is not workinghard
- Everyone rates confidence 100%hard