Sam Rivera

Product Management should have a starter file audit before this source set is treated as finished. The attached Product Management source review worksheet is the working document: fill it out against Opportunity solution tree guide, then keep or reject the claim in the product management playbooks folio.

The audit fields are reader problem, source checked, claim to verify, decision affected, missing context, and next test. They force the post to name the user problem, the checked source, and the next test before anyone saves the idea as a template, tracker, checklist, or worksheet.

Opportunity solution tree guide anchors the audit. The practical check is whether it changes a concrete product management decision, checklist item, tracker row, worksheet field, or template example.

Continuous discovery overview is the cross-check. If it changes the conclusion, the worksheet should preserve the disagreement instead of hiding it in a clean paragraph.

GitLab product handbook is the artifact source. It should give the post a document, dataset, repository, guide, API, checklist, or worked-example angle that a reader can reuse.

Video cross-check: Lenny's Podcast video archive should be used for workflow texture, not as the only citation. Watch for the exact screen, demo, route, pattern, cut setting, session step, or process moment that would change the audit.

Two sources to open first: producttalk.org/opportunity-solution-tree/ and youtube.com/@Lennyspodcast/videos. File the note under product-management, product-discovery, roadmaps, product-metrics, then use the attached document to record which claim each source supports, which claim remains opinion, and which detail should be removed if nobody can verify it.

The strongest reply would improve one field in the document. A better source, clearer caveat, stronger example, or missing beginner trap is more valuable than a broad reaction.