PRODUCT OPPORTUNITY RESEARCH · Workflow idea
For an approved product-research purpose, organize permitted reviews, public discussions, and competitor feature information to identify possible unmet needs. Preserve source context and attribution, minimize personal details, and treat clustered themes as hypotheses rather than validated demand. A product researcher should check representative examples, test assumptions with customers who have consented to participate, and approve any roadmap or marketing decision.
01 / The starting point
Permitted public research sources and feedback the organization is authorized to use
“Prepare evidence-linked product hypotheses without overstating the size or certainty of demand.”
02 / The work
Helps product teams organize market signals into ideas they can investigate and validate.
Use only sources and information approved for this purpose.
Remove unnecessary identifiers and keep links to original context.
Record evidence and mark each proposed gap as an untested hypothesis.
Review original material and note whose voices may be missing.
Have a product owner plan consent-based research or other verification.
03 / The result
A research brief of possible needs, source examples, limitations, and validation steps.
Commerce · Example outcome
A research brief of possible needs, source examples, limitations, and validation steps.
Online comments and competitor features are incomplete evidence and may not represent a target market. Follow source terms, respect user privacy, preserve attribution, and validate demand with appropriate research before committing resources or making public claims.
04 / Make it yours
A few choices shape the work around your team.
Define sources, audience, topics, and permissible uses in advance.
Minimize identifiers and avoid sensitive personal inferences.
Keep original links and distinguish observations from hypotheses.
Require human validation before roadmap or public decisions.