CUSTOMER NEEDS RESEARCH · Workflow idea
For an approved product or support research purpose, review permitted public questions and discussions about defined topics and organize possible recurring issues for a team. Respect forum terms, avoid retaining usernames or personal stories unless necessary, distinguish a reported problem from a verified product defect, and include source links and uncertainty. Require a product or support owner to validate findings before contacting authors or changing customer-facing guidance.
01 / The starting point
Public support discussions accessible under approved source terms
“Identify possible recurring needs without treating individual posts as verified facts or representative evidence.”
02 / The work
Helps product teams organize public support discussions into issues for further review.
Use an approved research question and check source terms.
Keep source links and dates while minimizing usernames and personal details.
Distinguish reported experiences from confirmed product behavior.
Read source context and avoid claiming the forum represents all customers.
Have a team owner validate issues before updating guidance or contacting anyone.
03 / The result
A source-linked issue summary with sampling limits, privacy controls, and reviewer status.
Customer support · Example outcome
A source-linked issue summary with sampling limits, privacy controls, and reviewer status.
Forum posts may contain sensitive personal context and unverified claims. Confirm permitted collection, minimize identity data, preserve the original discussion for fact-checking, and do not contact authors or label a product defect without human review.
04 / Make it yours
A few choices shape the work around your team.
Record topic scope, permitted forums, and collection boundaries.
Avoid retaining account names or sensitive stories not needed for analysis.
Label findings as reported, observed, or independently verified.
Require human confirmation before customer contact or product conclusions.