Find your next step.
Agree on the input and goal
Imagine a product team receiving customer feedback every week. The goal is not to let an agent decide the product roadmap. It is to help the team see recurring themes and open questions sooner. This is an illustrative workflow, not a real customer case study.
The input could be a table with the feedback date, original wording and related feature. Before starting, remove personal information that is irrelevant to the analysis and define the permitted use of the material.
Organise records without losing differences
Flag exact duplicates while retaining differences in how people describe their experience. Two records using similar words do not necessarily describe the same problem.
During preparation, separate categorised records from those that need human judgement. This makes uncertainty visible instead of hiding it inside a tidy-looking table.
Move from themes to suggestions
Attach original records to each theme so the basis for the summary is visible. Frame recommendations as ideas to validate, such as improving onboarding guidance or moving a help link, rather than presenting unverified root causes.
Separate what users said, what the team suspects and what should be tested next. This keeps the discussion focused.
Let the team decide what happens next
The final deliverable can include a theme summary, supporting records, open questions and a suggested owner. The team then sets priorities using its product plans, likely impact and available resources.
You can explore this process in the Workspace demo. It uses fixed data to illustrate collaboration steps, rather than automatically analysing real customer records.
Choose a task with clear boundaries. Understand the workflow, then refine it step by step.
Try the task demo