Skip to content

Feature request research

Turn public product suggestions into a source-linked problem list without treating a loud thread as a representative roadmap vote.

Use cases

Which requests describe the same underlying problem?

Feature research is more useful when it captures the task someone cannot complete, not just the solution they propose. A request for an integration, a workaround in a tutorial and a repeated question can point to one problem. Use public evidence to develop hypotheses for product interviews; it cannot replace private customer context or determine a roadmap by itself.

Example product research prompt
Find public requests about exporting reports in our selected watchlist. Group by the task people cannot complete, distinguish bugs from new capabilities, and cite original wording. Do not infer whether authors are paying customers.
01 / Use cases

Collect a narrowly defined problem area

Start with a product capability or workflow, a few relevant public accounts or communities, and a date range. Include words people use for the task as well as the feature name. Exclude job advertisements, unrelated products and promotional repetitions. Inspect source coverage before interpreting an empty response as evidence that nobody needs the feature.

02 / Use cases

Preserve the request and its context

Keep the original wording, source URL and stated use case for each useful record. Distinguish a request, a bug report and a question about an existing capability. If the public record does not establish whether the person is a customer, say so. Do not invent company size, buying authority or account value from a profile.

03 / Use cases

Group by job, not just keyword

Combine records that describe the same blocked outcome while retaining the examples behind each grouping. Count distinct authors separately from messages, and identify copied or cross-posted requests. Show contradictory evidence too: a workaround may solve the issue for one workflow but fail for another. Treat group labels as an analyst's interpretation.

04 / Use cases

Write questions for validation

Deliver a problem statement, representative quotations and follow-up questions for your product team. State which uncertainties require interviews or product telemetry. A useful output is a research backlog with traceable evidence, not a fabricated priority score. Revisit saved evidence deliberately so a changing conversation does not silently rewrite the original rationale.

Keep the boundaries clear.

  • Repeated messages are not independent votes.
  • Public evidence supports hypotheses, not automatic roadmap prioritization.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage