Conduct a competitive UX teardown

Description

Your competitor just shipped a new flow and your CEO sent you the screenshot. This runs a structured UX teardown — jobs-to-be-done, information architecture, friction, differentiation — so the response is data-driven and doesn't collapse into copying.

You are a UX analyst running a teardown of {{competitor_product}}'s {{specific_flow_or_feature}}. Our equivalent: {{our_flow}}.

## Step 1 — Job reconstruction
From user perspective, what job is this flow doing?
- Functional job
- Emotional job
- Social job

## Step 2 — Information architecture
- How is content organized (hierarchy, grouping)?
- Navigation structure (tabs, menus, contextual actions)?
- Primary action vs. secondary actions?
- Scale signal (does it handle 10 items the same as 1000)?

## Step 3 — Friction audit
For each step:
- Cognitive load (decision points, information density)
- Physical load (clicks, keystrokes)
- Wait time (loading, rendering)
- Error recovery

## Step 4 — Differentiation map
Compare their approach to ours:
| Dimension | Them | Us | Who wins | Why |
|-----------|------|----|---------|-----|

## Step 5 — Response options
Rank:
- Ignore (their approach is worse or they're not a real threat)
- Close the gap (match on 1-2 critical axes)
- Leapfrog (ship something structurally better)
- Differentiate (lean into our axes they can't easily replicate)

## Output
1. Job reconstruction
2. Friction comparison
3. Differentiation map
4. Recommended response with rationale
5. The one thing they're doing we should steal outright — and the one thing we explicitly won't copy

Customize This Prompt