Don't Panic: Product Prioritization

Product prioritization is the disciplined answer to a familiar problem: there are more plausible things to do than there is capacity to do them. It does not discover a magical queue hidden in the product. It makes a choice for one goal, one horizon, and one evidence set, which is considerably less mystical and rather more useful.

Start with the goal, meaning the outcome the product should advance. Then collect candidates at one decision level. Problems compete with problems. Roadmap initiatives compete with roadmap initiatives. A strategy, a feature, and a bug in the same ranking are not a portfolio. They are an argument wearing a table as a hat.

Next comes evidence. Reach says who is affected during a named period. Impact says how much the change is expected to matter. Confidence admits how much support those estimates have. Effort counts the work across the people needed to deliver it. RICE combines those ideas as reach times impact times confidence, divided by effort. It is a comparison tool, not a tiny executive with a calculator.

Before scores, identify constraints. A legal obligation, security repair, dependency, or fixed deadline can make an order infeasible. Do not inflate an impact number until the required item wins. Record why it has to happen. The score can remain honest while the plan remains possible.

Different questions need different tools. An impact-and-effort matrix helps with fast triage. Weighted scoring makes strategy criteria explicit. WSJF compares relative cost of delay with job duration. MoSCoW protects scope inside a fixed horizon. Kano describes how attributes affect satisfaction, but does not decide delivery order. No framework has volunteered to take responsibility for the decision. It is waiting for a named owner.

The surprising part is that a score is not a commitment. A ranking still has to meet capacity, dependencies, portfolio balance, and the evidence behind it. When judgment changes the order, write the override down. Altering the inputs after seeing the result only teaches the spreadsheet to nod more enthusiastically.

Read the intro for the full decision system and the limits of each method. Use the slides when you need the map of levels, constraints, scores, and review. Keep the cheatsheet nearby for formula contracts and diagnostic signals. Then use the practice reference and exercise to make one decision record that can survive the next piece of evidence without requiring ceremonial smoke.