Back to Details

research-synthesis

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/research-synthesis

/research-synthesis

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Synthesize user research data into actionable insights. See the user-research skill for research methods, interview guides, and analysis frameworks.
如果看到不熟悉的占位符或需要查看已连接的工具，请参阅CONNECTORS.md。
将用户研究数据转化为可执行的洞察。如需了解研究方法、访谈指南和分析框架，请查看user-research技能。

Usage

使用方法

/research-synthesis $ARGUMENTS
/research-synthesis $ARGUMENTS

What I Accept

支持的输入类型

  • Interview transcripts or notes
  • Survey results (CSV, pasted data)
  • Usability test recordings or notes
  • Support tickets or feedback
  • NPS/CSAT responses
  • App store reviews
  • 访谈记录或笔记
  • 调查结果（CSV格式或粘贴的数据）
  • 可用性测试录制内容或笔记
  • 支持工单或反馈
  • NPS/CSAT反馈
  • 应用商店评论

Output

输出格式

markdown
undefined
markdown
undefined

Research Synthesis: [Study Name]

研究合成报告：[研究名称]

Method: [Interviews / Survey / Usability Test] | Participants: [X] Date: [Date range] | Researcher: [Name]
研究方法： [访谈 / 调研 / 可用性测试] | 参与人数： [X] 研究日期： [日期范围] | 研究员： [姓名]

Executive Summary

执行摘要

[3-4 sentence overview of key findings]
[3-4句话概括关键发现]

Key Themes

核心主题

Theme 1: [Name]

主题1：[主题名称]

Prevalence: [X of Y participants] Summary: [What this theme is about] Supporting Evidence:
  • "[Quote]" — P[X]
  • "[Quote]" — P[X] Implication: [What this means for the product]
普遍性： [Y位参与者中的X位] 主题概述： [主题内容简介] 支撑证据：
  • "[引用内容]" — 参与者[X]
  • "[引用内容]" — 参与者[X] 对产品的意义： [该主题对产品的影响]

Theme 2: [Name]

主题2：[主题名称]

[Same format]
[相同格式]

Insights → Opportunities

洞察→机遇

InsightOpportunityImpactEffort
[What we learned][What we could do]High/Med/LowHigh/Med/Low
洞察机遇影响程度实施难度
[我们的发现][可采取的行动]高/中/低高/中/低

User Segments Identified

识别出的用户细分群体

SegmentCharacteristicsNeedsSize
[Name][Description][Key needs][Rough %]
细分群体特征核心需求规模占比
[群体名称][特征描述][核心需求][大致占比]

Recommendations

建议

  1. [High priority] — [Why, based on which findings]
  2. [Medium priority] — [Why]
  3. [Lower priority] — [Why]
  1. [高优先级] — [依据哪些发现提出此建议]
  2. [中优先级] — [建议理由]
  3. [低优先级] — [建议理由]

Questions for Further Research

后续研究待解决问题

  • [What we still don't know]
  • [我们仍未明确的问题]

Methodology Notes

研究方法说明

[How the research was conducted, any limitations or biases to note]
undefined
[研究开展方式，需注意的局限性或偏差]
undefined

If Connectors Available

当已连接相关工具时

If ~~user feedback is connected:
  • Pull support tickets, feature requests, and NPS responses to supplement research data
  • Cross-reference themes with real user complaints and requests
If ~~product analytics is connected:
  • Validate qualitative findings with usage data and behavioral metrics
  • Quantify the impact of identified pain points
If ~~knowledge base is connected:
  • Search for prior research studies and findings to compare against
  • Publish the synthesis to your research repository
如果已连接~~user feedback：
  • 拉取支持工单、功能请求和NPS反馈以补充研究数据
  • 将主题与真实用户的投诉和请求进行交叉对比
如果已连接~~product analytics：
  • 用使用数据和行为指标验证定性研究发现
  • 量化已识别痛点的影响程度
如果已连接~~knowledge base：
  • 搜索过往研究报告和发现进行对比
  • 将合成报告发布到你的研究知识库

Tips

小贴士

  1. Include raw quotes — Direct participant quotes make insights credible and memorable.
  2. Separate observations from interpretations — "5 of 8 users clicked the wrong button" is an observation. "The button placement is confusing" is an interpretation.
  3. Quantify where possible — "Most users" is vague. "7 of 10 users" is specific.
  1. 包含原始引用——直接引用参与者的原话能让洞察更可信、更易记。
  2. 区分观察结果与解读——"8位用户中有5位点击了错误按钮"是观察结果。"按钮位置设计令人困惑"是解读。
  3. 尽可能量化——"大多数用户"表述模糊。"10位用户中有7位"则更具体。