Feature Prioritization

Core Philosophy

Prioritization is the most consequential activity in product management because it determines how limited resources are allocated. Every yes to one initiative is an implicit no to everything else. Effective prioritization replaces gut feeling and political influence with structured evaluation against consistent criteria. The goal is not to build everything but to build the right things in the right order.

Key Techniques

• RICE Scoring: Score initiatives on Reach (how many users affected), Impact (how much each user benefits), Confidence (how sure you are), and Effort (how much work required). Produces a comparable score across diverse initiatives.
• Impact/Effort Matrix: Plot initiatives on a 2x2 grid. Quick wins (high impact, low effort) go first; big bets (high impact, high effort) need strategic alignment; fill-ins go last; time sinks get cut.
• Weighted Scoring: Define criteria (strategic alignment, revenue impact, customer satisfaction, technical risk) with weights and score each initiative against them.
• Opportunity Scoring: Survey users on importance and satisfaction for each need. High importance plus low satisfaction reveals underserved opportunities.
• Cost of Delay: Estimate the economic cost of not building something now — lost revenue, churn, competitive disadvantage — to create urgency-based ordering.
• MoSCoW Method: Classify items as Must-have, Should-have, Could-have, or Won't-have to establish a minimum viable scope for each release.

Best Practices

• Use a consistent framework rather than ad hoc decision-making. Consistency makes tradeoffs explicit and debatable.
• Include diverse perspectives — engineering, design, sales, support — to avoid blind spots in evaluation.
• Re-prioritize regularly as new information emerges. Priorities based on outdated assumptions waste resources.
• Separate prioritization decisions from estimation. First decide what matters most, then determine what is feasible.
• Document the rationale for major prioritization decisions so the reasoning survives personnel changes.
• Stack-rank rather than categorizing into priority tiers. Tiers create ambiguity about ordering within each tier.

Common Patterns

• Two-Way Door Decisions: For easily reversible decisions, prioritize speed over analysis. Reserve deep prioritization effort for one-way doors.
• Customer Advisory Board Input: Use structured feedback from key customers as one input into prioritization without letting any single customer dictate.
• Tech Debt Allocation: Reserve a consistent percentage (15-20%) of capacity for technical debt reduction, prioritized separately by engineering.
• Theme-Based Allocation: Allocate capacity percentages to strategic themes first, then prioritize within each theme.

Anti-Patterns

• HiPPO (Highest Paid Person's Opinion) overriding structured prioritization.
• Prioritizing only by customer requests, biasing toward existing users over new markets or strategic investments.
• Analysis paralysis from over-scoring and over-debating low-stakes decisions.
• Treating all items as equal priority, which is the same as having no priorities.
• Ignoring technical debt until it becomes a crisis that blocks all feature work.
• Sunk cost bias — continuing to invest in low-performing initiatives because of past investment rather than future potential.