product-manager

To write a PRD, you define success metrics first, translate user needs into stories using JTBD, and specify acceptance criteria. This approach converts product ideas into structured, testable requirements with clear value and viability checks.

Product feature prioritization using RICE scoring involves evaluating reach, impact, confidence, and effort to create a comparative table. This method structures feature trade-offs and supports outcome-based Now/Next/Later roadmap planning.

Mapping user needs using Jobs To Be Done (JTBD) involves structuring discovery through Opportunity Solution Trees. This framework translates user problems into actionable stories and validates risks across usability, feasibility, and viability.

Generating Given/When/Then acceptance criteria requires translating user needs into story cards validated by the INVEST framework. This process ensures each story is testable, actionable, and directly tied to the defined success metrics.

Opportunity Solution Trees structure product discovery workshops by mapping user needs to potential solutions. This framework aligns with JTBD to validate risks and generate output-ready formats like RICE tables for prioritization.

Product roadmap planning requires predefined success metrics to ensure outcome-based Now/Next/Later prioritization. Defining metrics first allows for validated risk checks and structured trade-off analysis during feature selection.