All examples for Interview Theme Extractor

Comparative Analysis: Quarter-over-Quarter Theme Trends

Compares current quarter themes against previous research to identify intensifying, stable, resolved, and new issues with strategic risk assessment.

Input

What you provide to the skill

Compare these new themes to previous research. Last quarter users complained about slow onboarding. This quarter: same onboarding issue, plus new crashes. Are things improving or worsening?

Output

What the skill generates for you

COMPARATIVE THEME ANALYSIS: Last Quarter → This Quarter

═══════════════════════════════════════════════════════

📈 INTENSIFYING THEMES (Getting Worse)

  1. ONBOARDING FRICTION
    Last Quarter: Present - slow onboarding complaints
    This Quarter: Present + UNCHANGED - same onboarding issue persists
    Trend: ⬆ STALLED / NO IMPROVEMENT

    Last Quarter Feedback: “Slow onboarding”
    This Quarter Evidence:
    → Issue remains unresolved
    → Users continue experiencing slow onboarding

    Analysis: The onboarding problem identified last quarter has NOT been addressed. This represents a missed sprint cycle and continued user friction. The fact that users are STILL complaining about the identical issue indicates the problem has become entrenched and is now a known pain point affecting the product’s reputation.
    ACTION REQUIRED: 🚨 CRITICAL - Onboarding optimization must be prioritized immediately. Two consecutive quarters of the same complaint indicates systematic neglect.

═══════════════════════════════════════════════════════

🆕 NEW THEMES (Emerged This Quarter)

  1. APP CRASHES
    Last Quarter: Not mentioned (0%)
    This Quarter: NEW issue - crashes reported
    Trend: ⬆ NEW PROBLEM

    This Quarter Evidence:
    → “[Crashes mentioned in feedback]”

    Analysis: A completely new stability issue has emerged that was not present in last quarter’s research. This suggests either new bugs introduced in recent releases, or growing technical debt manifesting as reliability problems.
    ACTION REQUIRED: 🚨 HIGH - Investigate recent releases for crash patterns. Implement crash reporting analytics immediately.

═══════════════════════════════════════════════════════

STRATEGIC INSIGHTS:

✗ ALARM: Product quality is REGRESSING, not improving

  • Known onboarding issue remains unfixed after full quarter
  • New crashes introduced, indicating stability degradation
  • Customer experience is deteriorating on multiple fronts

⚠ STALLED: Onboarding improvement initiatives have failed or were not prioritized

  • Two consecutive quarters of identical complaints
  • Users losing patience with recurring issues

🚨 CRITICAL RISK: Compounding problems

  • OLD issues not fixed (onboarding)
  • NEW issues introduced (crashes)
  • Creates perception of declining product quality
  • Increased churn risk as problems accumulate

TREND SUMMARY:

  • 1 theme worsening (onboarding - no improvement)
  • 0 themes stable
  • 0 themes resolved/improved
  • 1 new theme emerged (crashes)

VERDICT: ⚠️ WORSENING - Product experience is deteriorating

═══════════════════════════════════════════════════════

PRIORITY RECOMMENDATIONS:

IMMEDIATE (This Sprint):

  1. Address onboarding friction - already delayed one full quarter
  2. Implement crash analytics and emergency bug triage
  3. Establish quality gate to prevent new stability regressions

NEXT SPRINT:
4. Conduct root cause analysis on why Q3 onboarding improvements failed
5. Review release process to understand crash introduction

STRATEGIC:
6. Establish quarterly theme tracking to ensure issues don’t persist across multiple quarters
7. Create quality metrics dashboard to monitor stability trends