Results for “risk-prioritization”

Rank a backlog of feature ideas by impact, effort, risk, and strategic alignment to identify the top 5 to pursue.

Run a pre-mortem risk analysis on a PRD or launch plan, categorizing risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifying by urgency and creating action plans.

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Design, prioritize, and evaluate product experiments with clear hypotheses and defensible decisions, including A/B testing, sample size estimation, and statistical interpretation.

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more.

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does, ranking failure modes by impact, likelihood, and cheapness to test.

Expert product strategy advisor for Senior PMs. Use this skill — proactively and without waiting to be asked — whenever defining a product vision, setting quarterly OKRs, building a roadmap, choosing between competing bets, entering a new product area, or when stakeholders disagree on direction. Also triggers for: "what should we prioritize", "we need a north star", "how do we choose between X and Y", "roadmap conflict", "what are our bets this quarter", "strategy alignment", "choosing what NOT to build", "three bets with trade-offs", "stakeholder misalignment on direction", "product direction for next quarter", "OKR planning". Produces a decision-focused strategy doc: North Star metric, Opportunity Tree, three bets with explicit trade-offs (including do nothing), and a recommended bet with its key assumption.

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Choose a prioritization framework based on product stage, team context, and stakeholder needs.

Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring. Use when a user needs help with project plans, project status reports, risk assessments, resource allocation, project roadmaps, milestone tracking, team capacity planning, portfolio health reviews, program management, or executive-level project reporting — especially for enterprise-scale initiatives with multiple workstreams, complex dependencies, or multi-million dollar budgets.

Turn assumptions, funnel opportunities, and product questions into a prioritised, feasibility-checked experiment backlog. Filters by traffic reality, metric latency, and method feasibility — not just ICE/RICE scoring. Maintains a living portfolio with status (idea → designed → running → readout → archived). Load when the user says "what should we test next", "build an experiment backlog", "prioritise our tests", "where should we experiment", "what's worth testing", or when the experimentation orchestrator routes here.

Turns a pile of bugs, issues, and error reports into a ranked, actionable plan with reproduction evidence. Ingests GitHub issues via gh, TODO/FIXME scans, error logs, or a pasted list; attempts to reproduce or classify every item; scores by impact, frequency, fix cost, and regression risk; clusters duplicates; and.