product-manager-toolkit

RICE scoring ranks items by reach, impact, confidence, and effort. This Skill documents each factor's scale and basis before calculating, exposes uncertainty, and runs sensitivity checks when close scores determine the outcome.

A PRD should cover the problem, users, goals, non-goals, requirements, edge cases, dependencies, analytics, rollout plan, risks, and acceptance criteria. Detail should match the decision stage rather than disguising unresolved product choices as engineering requirements.

Define the hypothesis, target population, primary metric, guardrails, minimum meaningful effect, duration or stopping rule, and decision rule upfront. Consider prototypes or qualitative tests when they reduce uncertainty faster than production changes.

Outcome-oriented roadmaps fit when items lack real commitments or dependencies. Each item captures rationale, intended outcome, evidence, owner, confidence, and validation signals, with dates used only for genuine deadlines.

Scoring frameworks organize judgment but do not replace it. Scales must be defined before scoring, uncertainty must be exposed, and values should never be fabricated just to complete a comparison table.