A folder full of interview notes is not yet a clear explanation of a problem. Analysis examines the details, while synthesis connects them into a useful account. Feedback from customers, support and colleagues can contribute, but the source and context still matter.
Keep the evidence traceable
Separate what happened from what you think it means. “Three participants opened Help before finding the invoice” is an observation from a particular study. “Customers need clearer billing navigation” is an interpretation to discuss.
Keep a link to the supporting material using appropriate access controls. Remove unnecessary personal details when sharing findings. A memorable quotation should not become impossible to check.
Group patterns without losing differences
Compare observations about the same task or situation. Look for recurring difficulties, exceptions and possible explanations. Do not treat a pile of similar sticky notes as proof of importance.
Customer requests also need interpretation. Several people asking for an export button may have different needs: sharing a report, keeping a record or moving data elsewhere. Those needs can lead to different solutions.
Example: feedback about missing receipts
Support labels a set of messages as “receipt problems.” Reading them shows two separate issues: some customers cannot find a receipt, while others receive one with the wrong billing name.
The team creates distinct findings and connects each to its evidence. Navigation changes can address the first problem; editing billing details may address the second. Merging both into one feature request would hide part of the work.
Close the loop with a decision
For each finding, record its consequence, the uncertainty that remains and the next action.
- Keep research findings separate from proposed solutions.
- Assign an owner for follow-up.
- Record whether a change was tested or released.
- Revisit the finding when new evidence disagrees.
Feedback management should make learning easier, not turn every comment into a promised feature.
Frequently asked questions
Key takeaways
- Separate observations, interpretations and solutions.
- Preserve enough context to check a finding.
- Investigate the need behind a feature request.
- Connect findings to decisions and follow-up evidence.