research-synthesis
把訪談、問卷等使用者研究整理成主題與建議
中文翻譯
--- name: research-synthesis description: 把使用者研究整理成主題、洞察與建議。手上有訪談逐字稿、問卷結果、可用性測試筆記、客服工單或 NPS 回覆，需要提煉成模式、使用者分群和有優先順序的下一步時使用。 argument-hint: "<research data, transcripts, or survey results>" --- # /research-synthesis > 如果看到不認識的 placeholder，或需要確認目前連接了哪些工具，請看 [CONNECTORS.md](../../CONNECTORS.md)。 把使用者研究資料整理成可以行動的洞察。研究方法、訪談指南和分析框架請看 **user-research** skill。 ## 用法 ``` /research-synthesis $ARGUMENTS ``` ## 我接受的輸入 - 訪談逐字稿或筆記 - 問卷結果（CSV、貼上的資料） - 可用性測試錄影或筆記 - 客服工單或回饋 - NPS/CSAT 回覆 - App store 評論 ## 輸出 ```markdown ## Research Synthesis: [研究名稱] **Method:** [Interviews / Survey / Usability Test] | **Participants:** [X] **Date:** [日期範圍] | **Researcher:** [姓名] ### Executive Summary [3 到 4 句話概述主要發現] ### Key Themes #### Theme 1: [名稱] **Prevalence:** [Y 位參與者中的 X 位] **Summary:** [這個主題在講什麼] **Supporting Evidence:** - "[引言]" — P[X] - "[引言]" — P[X] **Implication:** [這對產品代表什麼] #### Theme 2: [名稱] [格式相同] ### Insights → Opportunities | Insight | Opportunity | Impact | Effort | |---------|-------------|--------|--------| | [我們學到什麼] | [我們可以做什麼] | High/Med/Low | High/Med/Low | ### User Segments Identified | Segment | Characteristics | Needs | Size | |---------|----------------|-------|------| | [名稱] | [描述] | [主要需求] | [大約佔比 %] | ### Recommendations 1. **[高優先]** — [為什麼，依據哪些發現] 2. **[中優先]** — [為什麼] 3. **[低優先]** — [為什麼] ### Questions for Further Research - [我們還不知道的事] ### Methodology Notes [研究是怎麼進行的，有哪些限制或偏誤要註明] ``` ## 如果有連接 Connector 如果有連接 **~~user feedback**： - 拉出客服工單、功能需求和 NPS 回覆來補充研究資料 - 把主題和真實的使用者抱怨與需求交叉比對 如果有連接 **~~product analytics**： - 用使用量資料和行為指標驗證質性發現 - 量化已找出的痛點影響 如果有連接 **~~knowledge base**： - 搜尋過去的研究與發現來比對 - 把這份整理發布到你的研究資料庫 ## 小提醒 1. **放進原始引言**：直接引用參與者的話，會讓洞察更可信、更令人印象深刻。 2. **把觀察和詮釋分開**：「8 位使用者中有 5 位點錯按鈕」是觀察。「按鈕位置讓人困惑」是詮釋。 3. **能量化就量化**：「大部分使用者」很模糊。「10 位使用者中有 7 位」才具體。
英文原文
--- name: research-synthesis description: Synthesize user research into themes, insights, and recommendations. Use when you have interview transcripts, survey results, usability test notes, support tickets, or NPS responses that need to be distilled into patterns, user segments, and prioritized next steps. argument-hint: "<research data, transcripts, or survey results>" --- # /research-synthesis > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Synthesize user research data into actionable insights. See the **user-research** skill for research methods, interview guides, and analysis frameworks. ## Usage ``` /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 ## Output ```markdown ## Research Synthesis: [Study Name] **Method:** [Interviews / Survey / Usability Test] | **Participants:** [X] **Date:** [Date range] | **Researcher:** [Name] ### Executive Summary [3-4 sentence overview of key findings] ### Key Themes #### Theme 1: [Name] **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] #### Theme 2: [Name] [Same format] ### Insights → Opportunities | Insight | Opportunity | Impact | Effort | |---------|-------------|--------|--------| | [What we learned] | [What we could do] | High/Med/Low | High/Med/Low | ### User Segments Identified | Segment | Characteristics | Needs | Size | |---------|----------------|-------|------| | [Name] | [Description] | [Key needs] | [Rough %] | ### Recommendations 1. **[High priority]** — [Why, based on which findings] 2. **[Medium priority]** — [Why] 3. **[Lower priority]** — [Why] ### Questions for Further Research - [What we still don't know] ### Methodology Notes [How the research was conducted, any limitations or biases to note] ``` ## 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 ## 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.