Competitive UX Audit Template for User Research

Once per quarter for lightweight audits (checking specific features or recent releases). Once or twice per year for full audits across multiple workflows. Set up alerts (competitor blogs, Product Hunt, G2 reviews) to catch major UX changes between formal audits. The market moves fast, but your competitive position changes gradually.

Yes, always include at least one. Indirect competitors show you what users experience in adjacent categories. A project management PM should audit Notion (horizontal tool) or Figma (collaboration model). Users compare your experience to everything they use daily, not just your direct competitors. The [competitive analysis](/glossary/competitive-analysis) glossary entry covers more on selecting the right competitive set.

Have someone outside the product team audit your product using the same protocol. Internal teams cannot help but be generous with their own product. If that is not possible, audit your product first (before competitors) so you are not anchored by competitor scores. Be honest about friction you have normalized.

Prioritize gaps using the [RICE framework](/frameworks/rice-framework). Table stakes gaps (features every competitor has that you lack) usually get highest priority because they create switching barriers. Market-wide gaps (weaknesses across all competitors) are your biggest differentiation opportunities but require more investment. Present findings to stakeholders with screenshots: visual evidence is more persuasive than scores alone.

Three to five workflows per audit. Fewer than three gives you an incomplete picture. More than five becomes a multi-week project. Choose workflows that matter most to your target users and where you suspect competitive pressure. Start with workflows mentioned in customer churn interviews or feature requests. ---