customer-feedback-analyzer

客户反馈分析器

收集、分析并确定用户反馈的优先级，为产品决策提供依据。

核心原则

绝不要收集你不会采取行动的反馈。 收集反馈会让用户期待你采取行动。如果你无法承诺审查并处理反馈，就不要征求反馈。否则会损害信任。

反馈渠道

1. 应用内反馈小组件

最适合：情境化反馈、低操作门槛

// Contextual feedback
<FeedbackWidget
  context={{
    page: 'dashboard',
    feature: 'export',
    user_action: 'clicked_export'
  }}
  placeholder="How can we improve exports?"
/>

优点：质量高（情境化）、即时 缺点：可能打断用户流程

2. NPS 调查

最适合：衡量整体满意度和忠诚度

Question: "How likely are you to recommend [Product] to a friend or colleague?"
Scale: 0-10

Scoring:
  Promoters (9-10): Love your product, will advocate
  Passives (7-8): Satisfied but not enthusiastic
  Detractors (0-6): Unhappy, will churn

NPS = % Promoters - % Detractors

Benchmarks:
  Excellent: ≥50
  Good: 30-49
  Needs Work: <30

后续问题：“你给出这个分数的主要原因是什么？”

3. 支持工单

最适合：识别反复出现的问题

Pattern Recognition:
  - Same issue reported 5+ times → UX problem, not edge case
  - Support time > 10 min per ticket → Needs better docs
  - Ticket volume spike → Recent deploy likely caused issue

4. 用户访谈

最适合：深入的定性洞察

Interview Structure:
  1. Background (5 min): Their role, use case
  2. Problem Discovery (10 min): Challenges they face
  3. Solution Validation (10 min): Show prototype, get reaction
  4. Wrap-up (5 min): Any other feedback?

Sample Size: 5-10 users per persona

5. 功能请求投票

最适合：确定路线图优先级

工具：Canny、ProductBoard、Upvoty

Benefits:
  - See most requested features
  - Reduce duplicate requests
  - Public roadmap transparency
  - Close the loop automatically

Avoid:
  - Building everything requested
  - Letting voters drive strategy

6. 流失用户访谈

最适合：了解用户流失的原因

Key Questions:
  - What made you decide to cancel?
  - What feature/change would have kept you?
  - What are you switching to?
  - What did we do well?

反馈分类

按类型

Bug: Something broken
  - "Export fails with >100 rows"
  - Priority: Fix immediately

Feature Request: New capability
  - "Add Slack integration"
  - Priority: Vote/validate

Enhancement: Improve existing feature
  - "Export should include timestamps"
  - Priority: Nice to have

Usability: Confusing UX
  - "Can't find where to invite team members"
  - Priority: High (friction)

Performance: Speed issue
  - "Dashboard loads slowly"
  - Priority: Depends on impact

按严重程度

Critical: Blocks core workflow
  - "Can't save projects"
  - Action: Hotfix immediately

High: Significant friction
  - "Onboarding confusing"
  - Action: Fix this sprint

Medium: Minor annoyance
  - "Button text unclear"
  - Action: Fix next quarter

Low: Edge case or cosmetic
  - "Spacing looks off on mobile"
  - Action: Backlog

按频率

Widespread: 50+ reports
  → High priority

Common: 10-50 reports
  → Medium priority

Occasional: 5-10 reports
  → Low priority, monitor

Rare: <5 reports
  → Likely edge case, document workaround

按用户细分

Power Users: High engagement, experienced
  → Actionable, technical feedback

New Users: Recently signed up
  → Onboarding issues, first impressions

Churned Users: Cancelled/inactive
  → Why did they leave?

Enterprise: Paying customers
  → Security, compliance, integrations

优先级框架

优先级评分公式

Score = Impact (1-5) × Frequency (1-5) × Strategic Alignment (1-5)

Score ≥ 40: High Priority (next sprint)
Score 20-39: Medium Priority (next quarter)
Score < 20: Low Priority (backlog or never)

示例：

Feedback: "Add Slack integration"
  Impact: 4 (significantly improves collaboration)
  Frequency: 5 (50+ requests)
  Strategic Alignment: 4 (fits roadmap)
  Score: 4 × 5 × 4 = 80

  Decision: HIGH PRIORITY - Build next sprint

Feedback: "Change button color"
  Impact: 1 (minor cosmetic)
  Frequency: 1 (1 person mentioned)
  Strategic Alignment: 1 (not strategic)
  Score: 1 × 1 × 1 = 1

  Decision: LOW PRIORITY - Backlog

闭合反馈环路

1. 确认收到

Email Template:

Subject: Thanks for your feedback!

Hi [Name],

Thanks for taking the time to share your thoughts on [topic].

We review all feedback and use it to prioritize our roadmap. I've shared
your input with the product team.

You can track feature requests on our public roadmap: [link]

Thanks for helping us improve!
[Your Name]

2. 采取行动

Decision Tree: Is it reported 10+ times?
  Yes → Add to roadmap
  No → Monitor

  Does it align with strategy?
  Yes → Prioritize
  No → Document why not

  Can we ship in 2 weeks?
  Yes → Quick win, do it
  No → Add to backlog

3. 通知提出请求的用户

Email Template:

Subject: You asked for [Feature] - it's live!

Hi [Name],

Remember when you asked us to add [feature]? Good news - it's live!

[Screenshot/GIF of feature]

Here's how it works:

1. [Step 1]
2. [Step 2]

Try it now: [Link]

Thanks for the feedback that made this happen.
[Your Name]

P.S. Have more ideas? Reply to this email.

4. 公开更新日志

## [Feature] is now live!

Requested by 47 users, [Feature] lets you [benefit].

How it works:

- [Key point 1]
- [Key point 2]

Try it: [Link]
Thanks to everyone who suggested this!

常见反馈模式

会叫的轮子综合征

Problem: Vocal minority ≠ Real need

Example:
  - 1 user emails daily about dark mode
  - Analytics show 2% use dark mode

Action: Validate with data before building

无声流失

Problem: Users leave without complaining

Example:
  - Retention drops from 40% to 30%
  - No feedback, no complaints

Action:
  - Proactive exit interviews
  - Check analytics for drop-off points
  - Run usability tests

功能膨胀风险

Problem: Building everything requested leads to bloat

Example:
  - 'Add Excel export'
  - 'Add CSV export'
  - 'Add JSON export'
  - 'Add PDF export'

Action: Build generic solution, not every variant

综合与报告

每周反馈摘要

feedback_summary:
  period: "2024-01-15 to 2024-01-22"
  total_items: 87

  top_themes:
    - theme: "Slack Integration"
      frequency: 23
      severity: high
      example_quotes:
        - "We need Slack notifications"
        - "Can't notify team without Slack"
      recommended_action: "Build Slack integration next sprint"

    - theme: "Slow Dashboard Load"
      frequency: 15
      severity: medium
      example_quotes:
        - "Dashboard takes 10+ seconds"
        - "Performance is terrible"
      recommended_action: "Optimize queries, add caching"

    - theme: "Mobile App Request"
      frequency: 8
      severity: low
      example_quotes:
        - "I want a mobile app"
      recommended_action: "Monitor, not enough demand yet"

  nps:
    score: 42
    detractor_reasons:
      - "Too expensive" (12 mentions)
      - "Missing features" (8 mentions)
      - "Slow performance" (5 mentions)

  prioritized_backlog:
    - feedback: "Add Slack integration"
      score: 80
      priority: high

    - feedback: "Optimize dashboard performance"
      score: 45
      priority: medium

    - feedback: "Mobile app"
      score: 16
      priority: low

工具与软件

Feedback Collection:
  - In-app: Canny, UserVoice, Intercom
  - Surveys: Typeform, SurveyMonkey, Delighted (NPS)
  - User Research: Calendly, Zoom, UserTesting.com

Analysis:
  - Qualitative: Dovetail, Notion, Airtable
  - Quantitative: Excel, Google Sheets, Tableau
  - Sentiment: MonkeyLearn, Lexalytics

Roadmap Transparency:
  - Public Roadmap: Canny, ProductBoard, Trello
  - Changelog: Headway, ReleaseNotes.io, Beamer

反馈节奏

Daily:
  - Review support tickets
  - Monitor in-app feedback

Weekly:
  - Synthesize themes
  - Share with product team
  - Prioritize top requests

Monthly:
  - Send NPS survey
  - Review feature requests
  - Update public roadmap

Quarterly:
  - User interviews (5-10)
  - Exit surveys for churned users
  - Competitive feedback analysis

快速入门清单

• 设置应用内反馈小组件
• 安排 NPS 调查（每月一次）
• 创建反馈跟踪电子表格
• 每周审查支持工单
• 进行 2-3 次用户访谈
• 设置公开路线图（可选）
• 创建用于确认收到反馈的电子邮件模板
• 记录反馈分类流程

常见误区

❌ 收集反馈却不采取行动：损害信任 ❌ 实现所有请求：导致功能膨胀 ❌ 不通过数据验证：少数大声发言者 ≠ 多数人 ❌ 忽视沉默的大多数：并非所有人都会提供反馈 ❌ 没有后续跟进：用户希望知道你听取了他们的意见

总结

优秀的反馈分析应做到：

• ✅ 使用多个渠道（调查、工单、访谈）
• ✅ 系统地分类并确定优先级
• ✅ 快速处理高优先级反馈
• ✅ 闭合反馈环路（通知用户）
• ✅ 在用户请求与产品战略之间取得平衡
• ✅ 与团队分享洞察