PRODUCT DISCOVERY RESEARCH · Workflow idea

Use community questions as research leads, not proof that a market is waiting.

For an approved product-research project, review a limited set of public community posts that describe recurring problems and organize them with potential solution ideas. Respect community rules, avoid retaining usernames or personal details, keep examples linked to their context, and validate demand and existing alternatives independently before treating an idea as a business opportunity.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A researcher defines a problem area to explore
Produces
A research sheet with de-identified post context, problem themes, concept hypotheses, and review notes.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

Public discussion available for a permitted, clearly scoped research purpose

“Find possible unmet needs without misrepresenting contributors or presenting generated concepts as validated businesses.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps entrepreneurs organize community discussions into problem statements and early solution concepts.

  1. Define the problem area and research scope

    Choose relevant communities, topics, and a proportionate collection period.

  2. Review public posts under source rules

    Keep enough context to understand the problem without retaining unnecessary identifiers.

  3. Describe the underlying need

    Separate what contributors actually said from a researcher’s interpretation.

  4. Develop solution hypotheses

    Treat possible products, users, and implementation ideas as starting points for validation.

  5. Check alternatives and validate with people

    Research existing options and seek appropriate user feedback before drawing conclusions.

03 / The result

Something useful.
Something to build on.

A research sheet with de-identified post context, problem themes, concept hypotheses, and review notes.

AmbactiWorkflow folio · 5 steps

Review community startup opportunities

Reviews & approvals · Example outcome

The handoff

A research sheet with de-identified post context, problem themes, concept hypotheses, and review notes.

Keep in mind

A few public posts do not establish market size, demand, or a lack of alternatives. Follow community rules and source terms, remove unnecessary identifiers, check existing solutions, and talk to potential users before making product or investment decisions.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Confirm community rules and permitted use

Respect source terms, access limits, and the context in which posts were shared.

Minimize contributor information

Avoid storing usernames, profile details, or personal information not needed for the study.

Keep hypotheses distinct from findings

Label concepts and market assumptions as unvalidated ideas.

Plan independent demand validation

Require user research and alternatives analysis before investing or making claims.

Keep exploring

Review public product profiles

Organize details from a selected public product page into a readable research brief, with a person checking the original before relying on or sharing it.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗