hf-discovery-review

To review a product discovery draft for specification readiness, evaluate problem framing, user focus, wedge convergence, and evidence gaps against a fixed rubric to produce a formal verdict and actionable next steps.

A bridge-to-spec section in product discovery identifies which conclusions are ready to hand off to specification and which require further revision. You need it when a discovery draft is ready for formal review to determine hand-off readiness.

To separate facts from assumptions in a product discovery draft, apply a checklist-based review that systematically verifies evidence, identifies unresolved ambiguities, and outlines probe directions for further validation.

Yes, a discovery review rubric can check problem framing and user focus through a structured walkthrough that evaluates explicit requirements including why-now justification, wedge convergence, and evidence gaps.

The best way to prevent mixing discovery with design details is to follow a structured review workflow that provides a safe, auditable process enforcing separation between discovery conclusions and implementation specifications.

A discovery draft should be sent back for revision when the review rubric identifies unresolved ambiguities, missing user focus, insufficient evidence, or a weak bridge-to-spec section that fails to meet hand-off requirements.