Product Validation Report Prompt
Consolidate the whole validation into one shareable report — the success metric, the evidence, the hit / partial / miss verdict, and the iterate / pivot / scale decision, in a form the team and stakeholders can act on.
Overview
The metric, the measurement plan, the categorized evidence, and the decision are worth little scattered across four artifacts. This prompt consolidates them into a single Validation Report: what success was defined as, what the evidence showed against the target, the verdict, and the iterate / pivot / scale recommendation with its reasoning — structured so a stakeholder can read the call in the first section and a builder can act on it. It is the primary deliverable of a product-validation pass and the seed of the next planning cycle.
Workflow
-
Feed it the finished pieces
Supply the metric, evidence, verdict, and decision from the prior steps — this report consolidates them, it does not re-derive them.
-
Check the verdict is on top
The hit/partial/miss and the decision belong in the first sections; a report that buries the answer won't get read.
-
Hand the Next Cycle section to planning
The reusable metric, plan, and open questions are the input to the next round — route them there, don't let them die in the doc.
Why This Works
- Leading with the verdict and decision gives stakeholders the answer before the detail
- Keeping evidence and recommendation separate makes the call auditable against the data
- The Next Cycle section turns a one-off report into the start of the next planning loop
Best for
- Sharing a validation outcome with people who weren't in the data
- Closing the loop on a shipped product with a written verdict
- Carrying the metric and plan forward into the next iteration
Not for
- Making the iterate/pivot/scale decision itself — that is the Product Validation Decision Framework Prompt
- Planning what to measure — that is the Product Validation Measurement Plan Prompt
- A deployment runbook or release note — this reports the outcome, not the rollout
Use cases
- Writing up a post-launch validation result for stakeholders
- Bundling the metric, evidence, verdict, and decision into one artifact
- Producing the document that feeds the next planning cycle