Keep observation separate from interpretation
A participant saying “I cannot tell what this does” is an observation about their experience. “We need a different brand name” is one possible interpretation. Record what happened before deciding how to respond. That separation stops a team jumping to an expensive solution before understanding the problem.
Find the reason behind a reaction
If someone calls packaging expensive-looking, ask what gave that impression. It could be the material, the colour, the amount of text or a comparison with another brand. The detail matters because it tells you which element might be doing useful work, and which one may need changing.
Consider patterns and exceptions
Group comments into themes such as clarity, usability, value and appeal. Note where views recur and where they differ. A repeated concern deserves attention, but one specific usability issue can also matter. Keep the participant context visible, and do not turn the number of comments in a small session into a market-wide percentage.
Choose an action you can test
Translate a finding into a proposed change and a question for the next test. If people misunderstand the product’s purpose, a clearer front label may be worth testing before redesigning the whole pack. If two messages appeal to different audiences, investigate who each message reaches rather than averaging the reactions together.
Build a short decision record
For each priority, write down the finding, the evidence behind it, the proposed action and who will own it. Identify anything still uncertain. A useful research report should help a team decide what to do next and where further evidence is needed. It should preserve awkward feedback as well as encouraging reactions: both can help improve the product before a wider launch.