Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across…
Framework-driven approach to sequencing features and allocating resources across competing priorities. Draws on 75 product leaders' frameworks including "cannonballs vs. lead bullets" (80/20 balance of big bets and incremental work), "seasons" for fast-changing markets, and growth models as common currency for cross-team comparison Emphasizes separating conviction from hypothesis, challenging assumptions about impact, and using roadmaps as feasibility checks rather than commitments Flags common pitfalls: prioritizing by loudest voice, all-incremental roadmaps, feature lists without narrative, and never removing features Includes diagnostic questions to surface hidden priorities, confidence levels, and resource constraints Prioritizing Roadmap Help the user prioritize product roadmaps and backlogs using frameworks from 75 product leaders. How to Help When the user asks for help with prioritization: Understand the decision context - Ask about their goals, constraints, and stakeholder landscape Assess the portfolio - Determine if they need to balance incremental vs big bets, or core vs new Provide frameworks - Recommend appropriate prioritization approaches for their situation Challenge assumptions - Help them question whether their current priorities are truly the most impactful Core Principles Separate truth from hypothesis Alex Hardimen: "The idea of being able to take all of these crazy inputs, trying to create a very structured model to figure out, 'Okay, what is true? Where do we have conviction? Where do we have questions?'" Categorize inputs by conviction level vs. questions and rally the team around a shared context.
don't have the plugin yet? install it then click "run inline in claude" again.