PRODUCT RESEARCH · Workflow idea

Listen for recurring problems before deciding what might be worth building.

For a defined product research purpose, review a limited sample of public discussion posts from communities whose rules permit the access and use. Keep original links and context, remove usernames and unnecessary personal details, and treat suggested pain points and business ideas as hypotheses—not proof of demand. Respect platform terms and community expectations, and validate any opportunity with independent research before making product, investment, or outreach decisions.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A researcher defines a market question
Produces
A source-linked research sheet with tentative problem themes, possible ideas, and sample limitations.
Category
Commerce

01 / The starting point

A clear request.
A useful direction.

A permitted public discussion source, focused topic, and documented research purpose

“Find useful themes in public conversations without presenting a small sample as representative demand.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Collects selected public discussion posts, organizes recurring concerns, and prepares tentative product ideas in a reviewable table.

  1. Define the topic and permitted communities

    Set a clear research question and use only sources whose access and reuse rules allow the review.

  2. Collect a bounded set of public posts

    Keep source links and dates while avoiding unnecessary usernames or personal details.

  3. Group possible problems and ideas

    Describe patterns cautiously and distinguish what people said from an interpretation or proposed solution.

  4. Check sample size and discussion context

    Review original posts and note bias, missing perspectives, and limits on representativeness.

  5. Validate before acting on an idea

    Use independent customer research and require an owner to approve outreach or business decisions.

03 / The result

Something useful.
Something to build on.

A source-linked research sheet with tentative problem themes, possible ideas, and sample limitations.

AmbactiWorkflow folio · 5 steps

Review public discussions for product ideas

Commerce · Example outcome

The handoff

A source-linked research sheet with tentative problem themes, possible ideas, and sample limitations.

Keep in mind

A post may be ironic, unrepresentative, or written for a context that a summary misses. Follow community rules, minimize personal data, avoid quoting or targeting individual contributors without permission, and verify ideas with broader evidence.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Document source rules and research purpose

Check platform terms and community expectations before collecting or reusing discussions.

Set sample and personal-data limits

Keep collection proportionate and remove identifiers not needed for analysis.

Preserve links and interpretation caveats

Record dates, selection criteria, sample size, and known biases beside each theme.

Require human validation before decisions

Treat ideas as hypotheses and confirm demand through appropriate, consent-aware research.

Keep exploring

Review product comparisons

Turn a product brief into a source-linked comparison of possible options for a shopper to assess.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗