Use this when you need to evaluate how competitors or comparators handle similar user flows, extract reusable UX patterns, and identify where your product can differentiate through better experience design. This is a UX-focused complement to market-positioning competitive analysis.
Related skills: Use
/competitive-analysisfor market positioning analysis. Pair with/ux-auditfor your own product's assessment. Feed patterns into/funnel-analysisfor conversion benchmarking.
Process
Step 1: Gather inputs
Ask the user to provide:
- Your product -- what it does, who it's for, the flows you want to benchmark
- Competitors/comparators -- 2-4 products to evaluate (direct competitors, adjacent products, or best-in-class examples from other industries)
- Flows to compare -- the specific user tasks to walk through on each product (e.g., onboarding, search, checkout, settings)
- Evaluation focus -- what matters most? (Speed, simplicity, delight, accessibility, mobile experience, information density)
Step 2: Flow walkthrough
For each competitor, walk through each target flow and document:
## Flow Walkthrough: {{Flow name}}
### {{Competitor A}}
- **Steps to complete:** (count)
- **Time to complete:** (estimate)
- **Friction points:** (where the user hesitates, errors, or backtracks)
- **Delight moments:** (where the experience exceeds expectations)
- **Notable patterns:** (interaction patterns, copy patterns, visual patterns worth studying)
- **Screenshots/evidence:** (reference specific screens or interactions)
### {{Competitor B}}
(same structure)
Step 3: Heuristic comparison
Score each product across UX dimensions for the target flows:
## Heuristic Comparison
| Dimension | Your Product | Competitor A | Competitor B | Competitor C |
|-----------|-------------|-------------|-------------|-------------|
| **Task completion speed** (fewer steps = better) | (score 1-5) | (score) | (score) | (score) |
| **Error prevention & recovery** | (score 1-5) | (score) | (score) | (score) |
| **First-time usability** (no training needed) | (score 1-5) | (score) | (score) | (score) |
| **Information clarity** (labels, hierarchy, copy) | (score 1-5) | (score) | (score) | (score) |
| **Visual consistency** (design system coherence) | (score 1-5) | (score) | (score) | (score) |
| **Mobile/responsive quality** | (score 1-5) | (score) | (score) | (score) |
| **Accessibility signals** (visible a11y effort) | (score 1-5) | (score) | (score) | (score) |
| **Delight & polish** (microinteractions, feedback) | (score 1-5) | (score) | (score) | (score) |
Step 4: Pattern extraction
Identify reusable patterns and anti-patterns across competitors:
## Patterns Worth Adopting
| Pattern | Seen in | What it solves | Adaptation for your product |
|---------|---------|---------------|----------------------------|
| (e.g., inline validation with positive feedback) | Competitor A, B | Reduces form errors by 30-40% | (how to apply it) |
## Anti-Patterns to Avoid
| Anti-pattern | Seen in | Why it fails | Your product's risk |
|-------------|---------|-------------|-------------------|
| (e.g., modal confirmation for non-destructive actions) | Competitor C | Interrupts flow, increases abandonment | (are you doing this?) |
Step 5: Gap and opportunity analysis
## Where You're Behind
| Area | Gap | Who does it better | Impact |
|------|-----|-------------------|--------|
| (area) | (what's missing) | (competitor) | High / Medium / Low |
## Where You're Ahead
| Area | Your advantage | Competitors' weakness | How to protect |
|------|---------------|---------------------|----------------|
| (area) | (what you do well) | (what they do poorly) | (how to maintain the edge) |
## Differentiation Opportunities
| Opportunity | Why no one does this well | Effort | Impact |
|-------------|--------------------------|--------|--------|
| (opportunity) | (market gap) | High / Medium / Low | High / Medium / Low |
Step 6: Review
Ask the user:
- Are the competitor selections right? Anyone missing?
- Do the scores match your experience using these products?
- Which patterns are most relevant to your current roadmap?
- Should I create stories for the top opportunities using
/story-write?
Output location
Present the benchmark as formatted text in the conversation. The comparison table and pattern extraction are shareable with the design and product team.
Example Output
Input
- Your product: Forma — a benefits enrollment platform for HR teams and employees at mid-market companies (500–5,000 employees); flows to benchmark: new employee benefits enrollment and mid-year qualifying life event (QLE) changes
- Competitors/comparators: Benefitfocus, Rippling Benefits, Gusto Benefits, and Navia Benefit Solutions
- Flows to compare: First-time enrollment (employee selects health, dental, vision, FSA) and QLE change flow (marriage event → update dependents + re-elect health plan)
- Evaluation focus: First-time usability (employees have no training), task completion speed, and error prevention — HR teams report ~30% of enrollments require support tickets to resolve
Output (abbreviated)
UX Benchmark: Benefits Enrollment & QLE Change Flows
Product: Forma | Comparators: Benefitfocus, Rippling, Gusto, Navia
Flow Walkthrough: First-Time Benefits Enrollment
Rippling Benefits
- Steps to complete: 7 steps (welcome → eligibility confirm → health → dental → vision → FSA → review/submit)
- Time to complete: ~6–8 minutes
- Friction points: Plan comparison opens in a modal with no side-by-side cost calculator; employees must mentally track out-of-pocket maxima across tabs. FSA contribution screen has no annual vs. per-paycheck toggle — consistently cited in support forums as confusing.
- Delight moments: Animated progress bar with step labels persists throughout; "You're covered" confirmation screen with effective date prominently displayed creates genuine reassurance.
- Notable patterns: Smart defaults — pre-selects the most-enrolled plan tier with a "Most popular" badge. Waives spousal info unless user checks a "covering a spouse" checkbox, dramatically reducing form length for single employees.
Gusto Benefits
- Steps to complete: 11 steps
- Time to complete: ~12–15 minutes
- Friction points: Asks for dependent SSNs before the employee has chosen a plan — creates anxiety and drop-off before intent is established. No inline validation; errors surface only on "Submit."
- Delight moments: Contextual tooltips on insurance jargon ("What's a deductible?") reduce support burden. Plain-language copy throughout ("This plan works best if you rarely go to the doctor").
- Notable patterns: Glossary tooltips embedded in labels. Jargon-free tier naming ("Basic," "Standard," "Comprehensive" alongside carrier names).
Benefitfocus
- Steps to complete: 14 steps
- Time to complete: ~18–22 minutes
- Friction points: PDF plan documents open in new tabs with no summary layer; employees are expected to read 40-page SBCs. Forced account-password creation before enrollment begins causes 15–20% abandonment at that screen. Visual design is dated, creating trust issues on mobile.
- Delight moments: None observed.
- Notable patterns: Comprehensive audit trail visible to HR admin — strong compliance affordance even if employee UX suffers.
Navia Benefit Solutions
- Steps to complete: 9 steps (but FSA-only flow is best-in-class at 4 steps)
- Friction points: Navigation between plan types requires returning to a dashboard rather than a linear wizard — users lose context.
- Delight moments: FSA contribution estimator with healthcare spending sliders is genuinely useful and reduces over/under-contribution errors.
Flow Walkthrough: QLE Change (Marriage → Add Dependent → Re-elect Health Plan)
Rippling Benefits
- Steps to complete: 5 steps — event declaration, document upload, dependent add, plan re-election, confirm
- Friction points: Document upload (marriage certificate) is a blocking step with no "upload later" option, even though HR can verify asynchronously. Causes abandonment when employees are at work without files.
- Notable patterns: 30-day QLE window displayed prominently with countdown — creates urgency without panic.
Gusto Benefits
- Steps to complete: 8 steps
- Friction points: Dependent date-of-birth field uses three separate dropdowns (MM / DD / YYYY) with no date picker — a known mobile accessibility failure. Re-election requires re-entering the full enrollment wizard, not a focused diff view.
Heuristic Comparison
| Dimension | Forma | Rippling | Gusto | Benefitfocus | Navia |
|---|---|---|---|---|---|
| Task completion speed | 2 | 4 | 3 | 1 | 3 |
| Error prevention & recovery | 2 | 4 | 2 | 2 | 3 |
| First-time usability | 2 | 4 | 4 | 1 | 2 |
| Information clarity | 3 | 4 | 5 | 2 | 3 |
| Visual consistency | 3 | 5 | 4 | 1 | 2 |
| Mobile/responsive quality | 2 | 4 | 3 | 1 | 2 |
| Accessibility signals | 2 | 3 | 3 | 1 | 2 |
| Delight & polish | 2 | 4 | 3 | 1 | 2 |
| Total (40 max) | 18 | 32 | 27 | 10 | 19 |
Scores 1–5; higher = better. Forma scores based on current product walkthrough provided.
Patterns Worth Adopting
| Pattern | Seen in | What it solves | Adaptation for Forma |
|---|---|---|---|
| Smart plan default with "Most popular" badge | Rippling | Reduces decision paralysis; shortens enrollment time ~40% | Default to most-enrolled plan in each category within the employer's cohort; show badge with opt-out |
| Jargon tooltips embedded in field labels | Gusto | Cuts "what does this mean" support tickets; reduces enrollment errors | Add tooltip layer to deductible, OOP max, coinsurance, FSA eligible fields — no new screen required |
| Per-paycheck ↔ annual FSA toggle | Missing everywhere | Employees think in paychecks, not annual totals — mismatches cause regret | Add real-time toggle on FSA contribution input; show both figures simultaneously |
| QLE countdown timer | Rippling | Creates urgency; reduces deadline-miss support escalations | Surface 30-day window on dashboard banner and in enrollment header |
| Navia FSA estimator (spending sliders) | Navia | Reduces FSA over/under-contribution; reduces year-end forfeiture complaints | Build simplified estimator (3 sliders: prescriptions, doctor visits, anticipated procedures) before FSA contribution step |
Anti-Patterns to Avoid
| Anti-pattern | Seen in | Why it fails | Forma's current risk |
|---|---|---|---|
| Forced account creation before enrollment begins | Benefitfocus | Pre-intent friction causes 15–20% abandonment; employees feel punished before they've done anything | Active risk — Forma currently gates enrollment behind a password-reset prompt for first-time SSO users |
| Collect dependent SSN before plan selection | Gusto | Creates anxiety before purchase intent is established; abandonment spikes | Not currently an issue — but dependent info form order should be audited |
| Document upload as hard blocking step in QLE | Rippling | Employees at work rarely have marriage certificates on hand; causes incomplete QLE submissions | Active risk — Forma blocks QLE submission pending document; HR cannot unlock asynchronously |
| PDF plan docs with no summary layer | Benefitfocus | 40-page SBCs are unusable; employees guess or call HR | Active risk — Forma links raw carrier PDFs with no structured summary |
Where You're Behind
| Area | Gap | Who does it better | Impact |
|---|---|---|---|
| First-time enrollment step count | Forma requires 13 steps vs. Rippling's 7 | Rippling | High — directly tied to 30% support ticket rate |
| Plan comparison UX | No side-by-side view; no cost calculator | Rippling, Gusto | High |
| FSA contribution clarity | No per-paycheck toggle; no estimator | Navia | Medium |
| QLE document handling | Hard block prevents async completion | Rippling (partial) | High |