Product Validation Decision Framework Prompt

Overview

Collected evidence decides nothing until someone weighs it against the bar and commits to a call. This prompt synthesizes the categorized behavior and feedback signals against the success metric, renders a clear hit / partial / miss verdict, and converts that into the decision that matters — iterate, pivot, or scale — with the reasoning and the open risks that could change it. It keeps the recommendation tied to the supplied evidence, so the call is auditable rather than a gut read dressed up in data.

Workflow

1. 1
   Bring the metric in with the evidence

   Supply the success metric and target alongside the categorized signals — the verdict is meaningless without the bar it is measured against.

2. 2
   Force one verdict and one decision

   Hold it to a single hit/partial/miss and a single iterate/pivot/scale — a hedged verdict is how teams avoid deciding.

3. 3
   Read the Open Risks before acting

   Thin evidence or an unaddressed confounder in that section means the call is provisional — treat it as such.

Why This Works

• Weighing signals against an explicit target keeps the verdict evidence-driven, not vibe-driven
• Forcing exactly one verdict and one decision stops the analysis from dodging the call
• The Open Risks section keeps a confident recommendation honest about what could change it

Use cases

• Turning categorized launch evidence into a hit/partial/miss verdict
• Converting a validation result into an iterate, pivot, or scale call
• Keeping a go/no-go recommendation tied to the evidence behind it