Research

Competitive Analysis

A systematic evaluation of competing products to understand industry conventions, gaps, and opportunities before making design decisions.

#competitive analysis#competitor research#benchmarking#heuristic evaluation#market analysis#ux audit

What is it?

Competitive analysis in UX is a structured process of evaluating competing or analogous products to understand what they do well, where they fall short, and what conventions they have established. It goes beyond a feature comparison spreadsheet — it examines UX patterns, information architecture, interaction design, onboarding flows, error handling, and emotional tone. The goal is to build on industry knowledge rather than reinvent it, and to identify gaps your product can genuinely fill.

Why it matters

Users come to your product with expectations shaped by every competitor they've used before (Jakob's Law). If your competitors have established a convention — such as a sidebar filter on e-commerce listings — breaking it requires a very strong reason. Competitive analysis reveals what those conventions are, which ones users have been trained to expect, and which ones are genuinely broken and present an opportunity. It also prevents you from investing in building features that competing products have already proven don't work.

Best Practices

Analyse direct competitors (same category, same user need), indirect competitors (different category, same user goal), and analogous products (different category, similar interaction patterns).
Structure your analysis with consistent evaluation criteria: onboarding, navigation patterns, key flows (sign-up, checkout, search), error handling, and empty states.
Use screenshots and video recordings to build an evidence base. Memory is unreliable; artefacts are not.
Map convention frequency: if 4 out of 5 competitors put the cart icon in the top-right, your users expect it there. Convention frequency equals user expectation strength.
Identify patterns that are universal (logo top-left) vs. patterns that are product-specific (a particular filter UI). Universal patterns should generally be followed; product-specific ones are areas of potential differentiation.
Look for patterns that multiple competitors have but that are broken or frustrating — these are genuine UX opportunities.
Evaluate competitors as a first-time user would: go through the actual sign-up, onboarding, and core flows rather than examining a logged-in state only.
Document findings in a format that is shareable with non-UX stakeholders — annotated screenshots beat prose descriptions.
Update competitive analysis regularly — the UX landscape shifts constantly and 12-month-old findings can mislead.

Common Mistakes

Only analysing direct competitors and missing analogous products where innovative patterns often emerge first (e.g., studying fintech apps for onboarding inspiration when designing an enterprise product).
Treating competitive analysis as a feature comparison ("they have X, we need X") rather than a UX patterns comparison.
Using competitive analysis to justify copying a competitor's design wholesale — understanding their patterns is not the same as duplicating them.
Analysing competitors from a business or marketing perspective rather than a UX perspective.
Conducting the analysis from an expert user perspective rather than a first-time user perspective.
Not documenting findings — competitive analysis done in someone's head is not a research asset.

Checklist

Direct, indirect, and analogous competitors are included in the analysis

Evaluation criteria are consistent across all products being analysed

Core flows (sign-up, onboarding, primary task) are evaluated as a first-time user

Findings include screenshots or recordings as evidence

Convention frequency is mapped (how many competitors use each pattern)

Genuine gaps and opportunities are explicitly called out, not just observations

Findings are documented and shareable with the full team

A date is recorded — competitive analysis has a shelf life

Research & Theory

Jakob's Law (Nielsen Norman Group)

Users spend most of their time on other products, building strong expectations about how things should work. Competitive analysis identifies exactly what those expectations are.

Why it's relevant

The practical argument for competitive analysis: if you don't know what your users are trained to expect, you cannot make informed decisions about when to follow convention and when to break it.

Convention and Innovation Trade-offs (Tidwell, 2010)

Jenifer Tidwell's research on UI patterns shows that conventions reduce the cognitive cost of learning new interfaces, while innovation can provide genuine advantages but carries a higher learning cost.

Why it's relevant

Competitive analysis maps the convention landscape. Once mapped, teams can make deliberate choices about where to follow and where to innovate, rather than making those choices blindly.

Real-World Examples

Notion

Before launch, Notion conducted extensive competitive analysis of Evernote, Confluence, and Google Docs — identifying that all three had strong structure but poor block-level flexibility. The gap informed Notion's block-based content model.

Figma

Analysed Sketch's collaboration limitations before building. The finding that designers emailed files instead of collaborating live became Figma's core product hypothesis and competitive advantage.

Duolingo

Studied Rosetta Stone and traditional language learning apps, finding that all used long, session-based learning. The gap for short, gamified micro-lessons became Duolingo's defining UX differentiation.