Conduct a competitive UX teardown

UX Teardowns Should Produce Decisions, Not Screenshots

Competitive UX teardowns that stop at screenshots become internal slide decks nobody uses. Nielsen Norman Group's UX analysis frameworks and Mind the Product's competitive analysis writing both argue that a teardown without a response decision is theater — the point is to choose between ignoring, closing the gap, leapfrogging, or differentiating.

How the Conduct a competitive UX teardown Prompt Works

The prompt reconstructs the job the competitor flow is doing, audits information architecture and friction, produces a differentiation map, and forces a four-way response decision with rationale. The "one thing we'll steal and one we won't" output is the honest check: copying isn't shameful, and refusing to copy a good pattern is strategic only when there's a reason.

When to Use It

• A competitor just shipped a flow and leadership wants a response.
• A sales rep lost a deal to a competitor's UX.
• A redesign is being scoped and competitive UX should inform it.
• A new entrant has differentiated on UX and a response is needed.
• A new PM wants to establish competitive analysis rigor.

Common Pitfalls

• Stopping at screenshots. Screenshots are data, not a decision. Produce a response recommendation.
• Copying on impulse. Copying what you can see misses the underlying job. Reconstruct the job first.
• Ignoring the friction axis. Lower friction is often the real differentiator, not feature presence.

Sources

• Usability Testing 101 — Nielsen Norman Group
• Which UX Research Methods — Nielsen Norman Group
• Mind the Product — Mind the Product
• First Round Review — First Round