1. Frame a decision, not a vague topic

Avoid asking, "What is wrong with this product?" Define the product, variation, rating range, time window, and decision you are evaluating. A useful question is: "Which durability complaints recur in verified one- to three-star reviews for the largest size, and which appear to trigger returns?"

2. Build a focused sample

Export a consistent scope. Start with lower ratings to discover failure modes, then compare them with four- and five-star reviews to understand what successful use looks like. Keep variations separate when fit, dimensions, color, bundle size, or model can change the experience.

The extension limit is 100 accessible reviews per export. Treat the file as a research sample, not a complete census of all customers.

3. Classify complaints consistently

  • Product area: material, fit, mechanism, packaging, instructions, durability.
  • Failure mode: breaks, leaks, does not fit, overheats, arrives damaged, confuses users.
  • Severity: inconvenience, reduced value, return trigger, safety concern.
  • Actionability: product change, quality control, packaging, instructions, listing clarity.
  • Evidence: review ID, exact customer language, rating, date, variation, verified status.

Define categories before tagging the full dataset. Test them on 10 to 15 reviews, merge overlapping labels, and write a one-sentence definition for each category so the classification remains consistent.

4. Prioritize patterns, not anecdotes

Frequency matters, but it is not enough. Combine occurrence, severity, recency, concentration in a variation, specificity, and whether the issue is addressable. A rare safety concern may deserve more attention than a common cosmetic complaint. A frequent delivery complaint may not justify redesigning the product itself.

Keep product defects separate from packaging damage, incorrect customer expectations, listing ambiguity, seller service, and carrier problems. This prevents the research brief from recommending the wrong intervention.

5. Validate before committing resources

  • Read source rows behind every high-priority claim.
  • Compare at least one direct competitor and one adjacent solution.
  • Check whether the pattern persists in recent reviews.
  • Verify dimensions, safety, legal, and compliance questions independently.
  • Use interviews, returns data, support tickets, or testing when available.

Reviews are observational evidence and may be manipulated or unrepresentative. They can reveal hypotheses and customer language, but they do not prove market size, technical feasibility, safety, or demand.