How to Present a Competitive UX Analysis

A competitive UX analysis tells you where your product's experience stands relative to alternatives users might choose. Presenting it well gives the product and design team a clear picture of where to compete hard and where the category is setting user expectations you need to meet.

Presenting it poorly produces a round of "we're better than them on this, they're better than us on that" with no actionable conclusion.

Define the Scope Before You Start

A competitive UX analysis needs clear boundaries:

Which competitors to include: Direct competitors (same product category, same user problem) and one or two alternative approaches (different product category, same user job). Including too many competitors creates noise. Three to five is usually the right number.

Which flows to evaluate: Don't try to evaluate the entire product experience. Choose the 2–4 flows most critical to your users' core jobs. Onboarding, core task completion, and a common recovery flow (error state, empty state, or search with no results) are often the most revealing.

Which criteria to use: Define evaluation criteria before analysis, not after. Post-hoc criteria selection introduces confirmation bias. Standard heuristic sets (Nielsen's 10 heuristics, or a domain-specific set) provide a defensible foundation.

Slide Structure

Slide 1: Analysis Scope

Competitors evaluated, flows analyzed, evaluation methodology, and the team member or UX expert who conducted the analysis. If real users were involved in any part of the evaluation (comparative testing, preference testing), include that here.

Slide 2: Evaluation Criteria

The heuristics or criteria used to evaluate each flow. Define each criterion in plain language. "Learnability: can a new user understand what to do without instruction?" is useful. A long academic definition is not.

Show the scoring scale. A 3-point scale (Below Standard / Meets Standard / Above Standard) is usually more meaningful than a 10-point scale that implies false precision.

Slide 3: Overview Scorecard

A comparison table: competitors across the top, evaluation criteria down the side. Color-code by rating. This single slide gives stakeholders the full picture at a glance and surfaces the categories where your product leads or lags most clearly.

Slides 4–7: Flow-by-Flow Comparison

For each evaluated flow, one slide showing:

Screenshots side by side: The same step in each competitor's product. Visual comparison is more compelling than text description.

Observations: What each competitor does differently at this step and the UX implications.

Who does it best: An explicit call-out of the strongest approach and why. Be willing to say a competitor does something better than your product if the evidence supports it.

What sets user expectations: If most competitors handle a step in a similar way, users have a baseline expectation. Deviating significantly from category norms requires strong justification.

Slide 8: Strengths by Competitor

What does each competitor do notably well from a UX standpoint? This is not a competitor feature list — it's specific UX patterns or design decisions that represent genuine strengths worth understanding and potentially learning from.

Slide 9: Category Standards

What does every competitor in this category do? These are the table stakes. If your product doesn't meet these standards, that's the highest-priority gap. Examples: all SaaS products of this type show empty state illustrations with a clear call to action, or all e-commerce checkouts allow guest purchase. If your product doesn't, that's not a strategic opportunity — it's a deficit.

Slide 10: Differentiation Opportunities

Where is the competitive UX experience weak across the board? These are the areas where your product can genuinely differentiate on experience, not just on features. A flow that every competitor handles poorly is an opportunity to set a new standard that becomes a reason customers prefer you.

Slide 11: Your Product's Position

An honest assessment of where your product stands. Where do you lead the category? Where do you meet the standard? Where do you fall below it?

This is the slide that will generate the most discussion. Be direct. Stakeholders who see only positive assessments of the product's competitive position will not take the analysis seriously.

Slide 12: Priority Recommendations

Three to five specific design improvements ordered by the combination of user impact and competitive gap. Each recommendation should connect to a specific observation from the analysis.

Presenting to a Skeptical Audience

Product and leadership teams sometimes resist competitive analysis findings that show the product in a negative light. The most effective response is to anchor the discussion on user expectations, not on competitor ratings.

"Users who have used [competitor] come to our product expecting [pattern]. When they don't find it, research shows they [behavior]" is harder to dismiss than "competitor does this better than us."

What to Avoid

Cherry-picking flows where you perform well. If you choose only the flows where your product looks favorable, the analysis is advocacy, not research. Include flows that are unflattering to get honest recommendations.

Evaluating competitors without actually using them. Screenshots and marketing copy are not sufficient for UX analysis. Use the actual product, complete real tasks, and experience the friction firsthand.

Over-relying on heuristic scores. Scores are useful for pattern-spotting, not for making direct decisions. A competitor that scores higher on a heuristic in a specific flow doesn't automatically mean you should copy their approach — it means you should understand why their approach works and whether the underlying UX reasoning applies to your context.