Activity⚡ Medium

Competitive Analysis

Understand the landscape your users already know before you design into it. Competitive analysis reveals the conventions users expect, the gaps competitors have left, and the consistent failures worth exploiting.

Product StrategyFeature ScopingUX BenchmarkingOnboarding DesignPricing StrategyNavigation Design

01 — TL;DR

Two sentences.

Competitive analysis examines how other products design the experiences your users will compare yours to — revealing conventions users have learned, gaps competitors have left, and the floor of expectation your product must meet or exceed. It is not copying what competitors built; it is understanding what users already know and expect before your design asks them to learn something new.

Applied specifically to user experience rather than market positioning, it examines how competitors structure onboarding, handle errors, design navigation, and where their flows break down. For design teams, it calibrates the baseline — the minimum usability and convention compliance users bring as an expectation.

02 — When to Use

Apply this when…

→You are designing in a category where users already have expectations shaped by other products

→A new flow is being designed and the team needs to understand which conventions to follow or break

→A redesign needs a benchmark — what should the current design improve beyond?

→Stakeholders request competitor features — you need evidence for whether they are well-executed or consistently poorly designed

→The team suspects the product is falling behind the category on a specific dimension

When NOT to apply it

Skip it in genuinely novel categories with no close analogues, when the goal is copying rather than understanding, when findings are older than six months in fast-moving categories, or when the team lacks access to the competitor products being analysed.

03 — How It Works

The mechanism

Competitive analysis builds a structured, comparable picture of how different products approach the same user problems — identifying patterns, gaps, and outliers. Without structure, it devolves into sharing favourite competitor features.

Jakob's Law and the cost of violating conventions

Users spend most of their time on other products and expect yours to work similarly. Patterns appearing consistently across a category are learned expectations your design must either meet (reducing cognitive load) or consciously break (accepting the teaching cost). Competitive analysis identifies which patterns have become conventions.

Direct, indirect, and analogous competitors serve different purposes

Direct competitors reveal category conventions. Indirect competitors reveal mental models from adjacent tools. Analogous competitors reveal innovations not yet adopted in your category. Limiting analysis to direct competitors shows the floor; including all three shows the ceiling.

Find what is consistently wrong, not just consistently done

Teams document what competitors do and use it as a template — meeting the floor but not exceeding it. The more valuable insight: what competitors consistently do poorly. A consistent failure across the category is not a template — it is a differentiation opportunity. Categories reward innovation most where conventions exist because of copying, not optimality.

Feature matrices, heuristic scoring, and UX benchmarking

Feature matrices show what exists. Heuristic scoring shows how well it is executed. UX benchmarking measures specific metrics (task time, error rate) across products. The most actionable analyses combine all three: what exists, how good it is, and how it performs.

A snapshot, not a permanent truth

A product category can change significantly in six to twelve months. Findings older than six months in fast-moving categories may mislead. The most effective teams treat competitive analysis as a living document updated quarterly, not a one-time research phase.

04 — Real Example

Notion's competitive analysis and the bet against feature parity

When Notion launched in 2016, the note-taking category was dominated by Evernote, OneNote, and Keep. A naive competitive analysis would have produced a feature gap list. Notion studied where users consistently complained rather than what features competitors offered.

The consistent failure: every major competitor used a predetermined schema (notebooks, notes, tags) that constrained user organisation. Users were working around note-taking constraints using spreadsheets, wikis, and Trello. Notion redesigned around blocks — a structural departure that allowed any organisational schema. That decision came from analysing consistent failures, not feature gaps.

Notion · 2016 · Category Entry

Competitive analysis of consistent failures reveals structural differentiation

Consistent failure → structural differentiation

05 — In the Wild

Test yourself & see real examples

No examples yet — be the first.

Spotted a product that understood the competitive landscape — or one that copied patterns without examining whether they served users? Submit what you observed.

✓ Reviewed before publishing✓ Your name on every example you submit✓ Violation or fix — both welcome

Seen Competitive Analysis skipped in a real product? Help grow the evidence base.

06 — Common Mistakes

Where teams go wrong

✗Documenting features rather than analysing experiences. A spreadsheet of which features exist is market intelligence, not UX analysis. Add functional evaluation: how does the feature work, how is it discovered, where does it break down?

✗Analysing only direct competitors. Limiting to your immediate competitive set produces an analysis of the floor. The most valuable insights come from indirect and analogous competitors — the conventions users bring from every product they use.

✗Using analysis to justify decisions already made. Running competitive analysis after a design decision and using competitor precedent to validate it is process performance. The time to run it is before decisions are made, so patterns inform rather than confirm.

✗Treating every competitor pattern as a best practice. Conventions may exist from market inertia, not user optimality. Is the pattern consistent because it works well, or because everyone copied the same early entrant? User research alongside competitive analysis is the only way to distinguish.

07 — Variations & Related Principles

Connected ideas

Competitive analysis sits at the intersection of product strategy and UX research.

The most important pairing is competitive analysis with user interviews. Competitive analysis reveals what users have been given; interviews reveal what they actually need. Together they produce the complete picture: existing solutions, the expectations they have created, and the gaps between what the market offers and what users need.

08 — 10-Min Exercise

Run it right now

⏱ 10 minutes · Solo · No prep

The Convention Inventory

1. Pick one core flow in your product. Open two or three direct competitors and navigate the equivalent flow. Look for what is the same across all of them.

2. Write three to five patterns that appear consistently. Label each as structural, visual, or behavioural.

3. For each, ask: does this exist because it works well for users, or because everyone copied the same early pattern? If you cannot answer, it is a research gap.

4. Write one thing every competitor does poorly in this flow — a consistent usability failure. That failure is either a differentiation opportunity or evidence of accepted convention that does not serve users.

10 minutes