How to turn your competitor’s worst reviews into your strongest design argument

One of the hardest parts of being a designer isn’t knowing what’s broken. It’s convincing someone who wasn’t in the research session, hasn’t read the reports, and has a different opinion backed by seniority.

What changes that isn’t better arguments: it’s better evidence.

We’re often taught to generate evidence from our users: recruit users, do testing, and synthesize findings. However, sometimes you don’t have time or resources to do that, especially if you’re trying to change an opinion on a limited time.

But sometimes, your competitors have already done the research. Their users are telling anyone who will listen exactly what’s broken. You just have to know where to look.

A lot of people roll their eyes at competitive research because it’s been taught as a biased comparison exercise.

As Dscout notes, it often lands on someone’s plate because no one else wants to do it. When it does, the default is to compare and contrast visuals.

You might be beating your competitor on visual design, but that’s because you’re targeting B2C customers who expect beauty, and they’re targeting B2B customers who care about functionality. That doesn’t tell you much.

Nielsen Norman Group puts it plainly: competitive evaluations exist to help teams base decisions on data rather than opinions or popular trends. But in practice, that means walking through a competitor’s experience with no context into their market or their users.

The more useful direction is the one most designers skip: the negative review.

Most designers who do competitive research look at what competitors are doing well. That’s the weaker argument.

When you compare screenshots of us against a polished competitor, you’re giving the argument of “look how good they are compared to us.” That might motivate a team, but it won’t persuade a stakeholder.

Negative reviews flip that entirely. Instead of pointing at someone else’s strengths, you’re pointing at their gaps.

If their users are consistently frustrated by something your product handles well, you’re not arguing pixels: you’re making a business case. Fix it on your side, and you give their frustrated users a reason to switch.

The goal is to identify those gaps, represented as complaint clusters. The same frustration, described in the same words, by people who don’t know each other.

As Invesp describes, this kind of review mining surfaces the challenges customers have experienced and points directly to where your product can outperform the competition.

The fastest place to start is Reddit. Search "[App name]" Reddit in Google and you’ll find threads where users are far more candid than any star rating.

You can also google other search strings like “Competitor X frustrating”, “Competitor X vs your product”, “Should I buy Company X”.

You can also try sites like G2 or Trustpilot, which let people filter and view 1–2-star reviews in aggregate.

Start mapping the negative landscape and see whether things break.

When you first dive in, you might be skeptical. Some 1-star reviews are more about people’s personal lives than a specific product.

There’s also a temptation is to read each complaint as a one-off. One person who had a bad day. One edge case that doesn’t matter. Resist that.

One person’s frustration with onboarding is just an opinion. Five people describing the same friction in the same words? That’s a pattern you want to take note of.

What you’re looking for is clusters of language. When you see the same complaint surface repeatedly, you’ve found something real. Not just what’s broken for them, but how users think and talk about what’s broken. And where your product has room to do better.

“It’s easy to stand behind something you want to suggest if the numbers are easy to translate.” — Head of Design, Silicon Valley Startup

That vocabulary matters. “I can never find where to change my notifications” tells you more about the mental model than any heuristic evaluation report.

Diving into negativity can ruin your afternoon, so set a few guidelines.

Time-box it. Give yourself 30 minutes. Set a timer. You’re not trying to read everything. You’re looking for frequency.

Filter hard. Go straight to one and two-star reviews. Everything else is noise for this exercise.

Count, don’t curate. Set a small, arbitrary threshold. If something gets mentioned five or more times, write it down. You’re not building a research report, you’re building a complaint cluster.

Note the exact words people use. Not your interpretation: their words. That language will show up again when you’re writing tooltips, error messages, and onboarding copy.

The complaint cluster is useful on its own, and is all the evidence you need. But if you want to make it harder to argue with, take one more step.

Once you have your complaint clusters, put them in a spreadsheet and count frequency. Even a simple bar chart showing the most common complaints turns a qualitative observation into something that reads as data in a meeting.

You’re not running sentiment analysis software. You’re counting, sorting, and presenting. Anyone can do this in 30 minutes with a spreadsheet and a basic chart.

The point isn’t precision: it’s a pattern. A chart that shows onboarding complaints outnumber every other category three to one makes the argument for you before you say a word.

When you have that, you have something you can actually use, not just for your own awareness, but in a room full of stakeholders.

The difference between “I don’t think this new onboarding direction is right” and “the single most common complaint in one-star reviews is onboarding, and this direction doesn’t address it” is the difference between opinion and evidence

That’s how you bring proof and argue a point of view with something behind it.

This is for designers who have a meeting in two hours and need to walk in with something real. The sources are free. The method takes less time than a standup.

And the output, a pattern of real user frustration in their own words, is exactly the kind of evidence that moves a conversation forward.

Kai Wong is a Design Storytelling Coach who helps Designers advance their careers through storytelling.