How to group feature requests around the same underlying need
Grouping feature requests helps a product team see repeated needs without treating every wording variation as a separate idea. It also makes the differences between superficially similar requests easier to discuss.
Start with the right material.
- What you provide
- a visible feature-request list.
- The intended result
- Cluster requests by desired outcome and retain links to each original request.
How the workflow works.
Compare the user goal, affected workflow and requested outcome. Keep source references for every group, and explain why requests belong together rather than merging them solely because they mention the same feature.
What to check in the result.
Review the proposed groups with the original requests available. A request count is a signal from the selected feedback, not a commitment to build or a complete measure of market demand.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Cluster, Request, Source reference. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.