discover-interview-synthesis

Name: discover-interview-synthesis
Author: product-on-purpose

486stars64forks

How to install discover-interview-synthesis?

product-on-purpose/pm-skills/discover-interview-synthesis

$npx -y skills add product-on-purpose/pm-skills --skill discover-interview-synthesis

Installs into the current project.

Summary

Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings across participants. Distinct from foundation-meeting-recap, which summari

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Interview Synthesis
3
4	An interview synthesis transforms raw user research data into structured insights that drive product decisions. Rather than simply listing what participants said, a good synthesis identifies patterns across conversations, connects observations to underlying user needs, and translates findings into actionable recommendations.
5
6	## When to Use
7
8	- After completing a round of user interviews (typically 5+ participants)
9	- Following customer discovery calls or sales feedback sessions
10	- After usability testing sessions to consolidate observations
11	- When stakeholders need a summary of research findings
12	- Before ideation sessions to ground the team in user reality
13
14	## When NOT to Use
15
16	- You are summarizing one internal meeting for its attendees -> use `foundation-meeting-recap`
17	- You need patterns across multiple meetings over time -> use `foundation-meeting-synthesize`
18	- Your data is survey responses rather than interviews -> use `measure-survey-analysis`
19	- The findings are synthesized and you are ready to frame the problem -> use `define-problem-statement`
20	- You have synthesized findings and want to map them onto a customer's journey across stages and touchpoints -> use `discover-journey-map`
21
22	## Instructions
23
24	When asked to synthesize interview findings, follow these steps:
25
26	1. Gather the Raw Material
27	Collect all interview notes, transcripts, or recordings. Ensure you have data from at least 3 participants to identify meaningful patterns. Note the research objective and methodology used.
28
29	2. Create Participant Profiles
30	Document each participant with relevant context: their role, segment, tenure, and any notable characteristics. This helps readers assess the representativeness of findings.
31
32	3. Identify Recurring Themes
33	Read through all notes and tag observations by topic. Look for themes that appear across multiple participants (ideally 3+). Distinguish between frequently mentioned topics and one-off comments.
34
35	4. Extract Meaningful Quotes
36	Capture 3-5 verbatim quotes per theme that powerfully illustrate the insight. Good quotes are specific, emotional, or particularly articulate. Always attribute quotes to participant IDs.
37
38	5. Synthesize into Insights
39	Transform themes into insight statements. An insight goes beyond observation ("users mentioned X") to interpretation ("users need Y because of Z"). Connect what you heard to why it matters.
40
41	6. Formulate Recommendations
42	Based on the insights, propose prioritized actions. Each recommendation should tie directly to an insight. Note confidence level based on strength of evidence.
43
44	7. Document Limitations
45	Acknowledge what you didn't learn, sample biases, or areas needing further research. Honest limitations increase credibility.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete synthesis fills every template section: Research Overview; Key Themes; Notable Quotes; Insights; Recommendations; and Appendix.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] Themes are supported by evidence from 3+ participants
56	- [ ] Quotes are verbatim and attributed to participant IDs
57	- [ ] Insights explain "why" not just "what"
58	- [ ] Recommendations are specific and actionable
59	- [ ] Participant identities are protected (no PII)
60	- [ ] Limitations and biases are acknowledged
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type

discover-interview-synthesis

486stars64forks

View on GitHub

How to install discover-interview-synthesis?

product-on-purpose/pm-skills/discover-interview-synthesis

$npx -y skills add product-on-purpose/pm-skills --skill discover-interview-synthesis

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Interview Synthesis
3
4	An interview synthesis transforms raw user research data into structured insights that drive product decisions. Rather than simply listing what participants said, a good synthesis identifies patterns across conversations, connects observations to underlying user needs, and translates findings into actionable recommendations.
5
6	## When to Use
7
8	- After completing a round of user interviews (typically 5+ participants)
9	- Following customer discovery calls or sales feedback sessions
10	- After usability testing sessions to consolidate observations
11	- When stakeholders need a summary of research findings
12	- Before ideation sessions to ground the team in user reality
13
14	## When NOT to Use
15
16	- You are summarizing one internal meeting for its attendees -> use `foundation-meeting-recap`
17	- You need patterns across multiple meetings over time -> use `foundation-meeting-synthesize`
18	- Your data is survey responses rather than interviews -> use `measure-survey-analysis`
19	- The findings are synthesized and you are ready to frame the problem -> use `define-problem-statement`
20	- You have synthesized findings and want to map them onto a customer's journey across stages and touchpoints -> use `discover-journey-map`
21
22	## Instructions
23
24	When asked to synthesize interview findings, follow these steps:
25
26	1. Gather the Raw Material
27	Collect all interview notes, transcripts, or recordings. Ensure you have data from at least 3 participants to identify meaningful patterns. Note the research objective and methodology used.
28
29	2. Create Participant Profiles
30	Document each participant with relevant context: their role, segment, tenure, and any notable characteristics. This helps readers assess the representativeness of findings.
31
32	3. Identify Recurring Themes
33	Read through all notes and tag observations by topic. Look for themes that appear across multiple participants (ideally 3+). Distinguish between frequently mentioned topics and one-off comments.
34
35	4. Extract Meaningful Quotes
36	Capture 3-5 verbatim quotes per theme that powerfully illustrate the insight. Good quotes are specific, emotional, or particularly articulate. Always attribute quotes to participant IDs.
37
38	5. Synthesize into Insights
39	Transform themes into insight statements. An insight goes beyond observation ("users mentioned X") to interpretation ("users need Y because of Z"). Connect what you heard to why it matters.
40
41	6. Formulate Recommendations
42	Based on the insights, propose prioritized actions. Each recommendation should tie directly to an insight. Note confidence level based on strength of evidence.
43
44	7. Document Limitations
45	Acknowledge what you didn't learn, sample biases, or areas needing further research. Honest limitations increase credibility.
46
47	## Output Format
48
49	Use the template in `references/TEMPLATE.md` to structure the output. A complete synthesis fills every template section: Research Overview; Key Themes; Notable Quotes; Insights; Recommendations; and Appendix.
50
51	## Quality Checklist
52
53	Before finalizing, verify:
54
55	- [ ] Themes are supported by evidence from 3+ participants
56	- [ ] Quotes are verbatim and attributed to participant IDs
57	- [ ] Insights explain "why" not just "what"
58	- [ ] Recommendations are specific and actionable
59	- [ ] Participant identities are protected (no PII)
60	- [ ] Limitations and biases are acknowledged
61
62	## Examples
63
64	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type