Discovery Research Synthesis
A senior PM's playbook for turning research artifacts into decisions. Customer interviews, user research notes, support ticket reviews, sales call transcripts, survey data, in-app feedback, all synthesized into the product direction they are meant to inform.
Most discovery research never produces decisions. The team conducts interviews; the transcripts pile up; a researcher hands product the raw artifacts (data-dump) or builds a polished readout deck (insight-theater); the deck gets a 30-minute review meeting and is never referenced again. Two months later the team is making the same product decisions that the research was supposed to inform, with the same gut-feel inputs the research was supposed to displace.
The discipline is in the synthesis. Synthesis is where research earns its keep: where transcripts become tagged observations, observations cluster into patterns, patterns get named, named patterns surface product implications, and implications drive specific decisions. Without that sequence, research is performance art.
This skill covers one-off discovery research projects: a 12-week customer development sprint, a sales-call review for an onboarding redesign, a support-ticket audit informing a roadmap quarter. Different from user-feedback-aggregation, which covers ongoing feedback streams; different from jtbd-framing, which is a specific framing technique often applied within synthesis but narrower in scope.
The voice is the senior PM or staff product researcher who has run synthesis well and seen plenty of teams fail at it. Honest about where polish becomes performance and where pattern-naming slides into pattern-fabrication.
When to use this skill: synthesizing a recent batch of customer interviews, auditing why prior research has not produced product decisions, designing the synthesis output for a multi-week discovery sprint, or establishing the synthesis discipline a team currently lacks.
What this skill is for
This skill spans research-to-decision synthesis. The PM-skill distinction:
discovery-research-synthesis (this skill) is one-off research synthesis: turning a discrete batch of artifacts into a discrete set of decisions.
user-feedback-aggregation is ongoing feedback streams: continuous synthesis across always-on channels (support, NPS, in-app, sales).
jtbd-framing is a framing technique often applied during synthesis; this skill is broader.
pm-spec-writing is downstream: specs use synthesized insights as input.
roadmap-planning is downstream: roadmap uses synthesized priorities as input.
experiment-design is the quantitative-validation discipline that often follows qualitative synthesis.
The audience: senior PMs, product directors, in-house product teams, agencies running discovery work for clients, researchers handing off to product teams.
What is not in scope: conducting the research itself (interview design, recruiting, moderation), the broader discovery strategy that decides which research to commission, or the long-running feedback channels that user-feedback-aggregation covers.
Reference files
references/research-types-and-when-each-fits.md - Five research types with synthesis implications. Composition patterns across types within a discovery cycle.
references/synthesis-sequence-walkthrough.md - The six-stage sequence with worked example. Stage outputs, common skip-failures, time investment per stage.
references/tagging-and-clustering-discipline.md - Tag-at-artifact-level discipline, allow tag proliferation, cluster on patterns not overlap, name after clustering, tag dissent.
references/pattern-naming-patterns.md - Pattern names that work and fail. Avoiding category bloat, naming-with-conviction, the implication-legibility test.
references/from-pattern-to-product-implication.md - The bridge from pattern to implication. Falsifiability, multi-implication patterns, cost acknowledgment, the not-act implication.
references/writing-for-decisions-not-decks.md - Document over deck, patterns lead, evidence appendix, opinionated voice, decision-input section.
references/synthesis-review-and-validation.md - Participant review, adjacent-team review, quantitative validation, the challenge-the-synthesis session, iteration before publish.
references/when-to-gather-more-data.md - Pattern thinness, segment under-representation, contradictory clusters, decision time pressure, the we-have-enough trap.
references/common-discovery-synthesis-failures.md - 11+ failure patterns with diagnoses and cures.
Conditional methods
Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.
- Data-dump vs insight-theater vs actionable-synthesis: method.
- Discovery research types: method.
- The synthesis sequence: method.
- Tagging and clustering discipline: method.
- Pattern naming: method.
- From pattern to product implication: method.
- Writing for decisions, not deck performance: method.
- The synthesis review and validation loop: method.
- When to halt and gather more data: method.
- Common failure modes: method.
- The framework: 12 considerations for discovery synthesis: method.
- Closing: synthesis is where research earns its keep: method.
1---2name: "discovery-research-synthesis"3description: "Turning research artifacts into actionable PM insight. Customer interviews, user research notes, support ticket reviews, sales call transcripts, survey data, in-app feedback, all synthesized into the decisions they are meant to inform. The discipline of moving from raw discovery data to clear product direction without losing signal in the synthesis or fabricating insight that was not actually there. Triggers on research synthesis, customer interview synthesis, user research analysis, discovery readout, research insights, sales call analysis, support ticket analysis, qualitative data analysis. Also triggers when a team has done research but cannot turn it into decisions, when synthesis is producing pretty decks but no roadmap movement, or when an upcoming PM decision needs to be grounded in research already conducted."4metadata:5 source: https://skillmd.com/skills/slipcast-dev/discovery-research-synthesis6---78# Discovery Research Synthesis910A senior PM's playbook for turning research artifacts into decisions. Customer interviews, user research notes, support ticket reviews, sales call transcripts, survey data, in-app feedback, all synthesized into the product direction they are meant to inform.1112Most discovery research never produces decisions. The team conducts interviews; the transcripts pile up; a researcher hands product the raw artifacts (data-dump) or builds a polished readout deck (insight-theater); the deck gets a 30-minute review meeting and is never referenced again. Two months later the team is making the same product decisions that the research was supposed to inform, with the same gut-feel inputs the research was supposed to displace.1314The discipline is in the synthesis. Synthesis is where research earns its keep: where transcripts become tagged observations, observations cluster into patterns, patterns get named, named patterns surface product implications, and implications drive specific decisions. Without that sequence, research is performance art.1516This skill covers one-off discovery research projects: a 12-week customer development sprint, a sales-call review for an onboarding redesign, a support-ticket audit informing a roadmap quarter. Different from `user-feedback-aggregation`, which covers ongoing feedback streams; different from `jtbd-framing`, which is a specific framing technique often applied within synthesis but narrower in scope.1718The voice is the senior PM or staff product researcher who has run synthesis well and seen plenty of teams fail at it. Honest about where polish becomes performance and where pattern-naming slides into pattern-fabrication.1920When to use this skill: synthesizing a recent batch of customer interviews, auditing why prior research has not produced product decisions, designing the synthesis output for a multi-week discovery sprint, or establishing the synthesis discipline a team currently lacks.2122---2324## What this skill is for2526This skill spans research-to-decision synthesis. The PM-skill distinction:2728- **`discovery-research-synthesis` (this skill)** is one-off research synthesis: turning a discrete batch of artifacts into a discrete set of decisions.29- `user-feedback-aggregation` is ongoing feedback streams: continuous synthesis across always-on channels (support, NPS, in-app, sales).30- `jtbd-framing` is a framing technique often applied during synthesis; this skill is broader.31- `pm-spec-writing` is downstream: specs use synthesized insights as input.32- `roadmap-planning` is downstream: roadmap uses synthesized priorities as input.33- `experiment-design` is the quantitative-validation discipline that often follows qualitative synthesis.3435The audience: senior PMs, product directors, in-house product teams, agencies running discovery work for clients, researchers handing off to product teams.3637What is not in scope: conducting the research itself (interview design, recruiting, moderation), the broader discovery strategy that decides which research to commission, or the long-running feedback channels that user-feedback-aggregation covers.3839---4041## Reference files4243- [`references/research-types-and-when-each-fits.md`](references/research-types-and-when-each-fits.md) - Five research types with synthesis implications. Composition patterns across types within a discovery cycle.44- [`references/synthesis-sequence-walkthrough.md`](references/synthesis-sequence-walkthrough.md) - The six-stage sequence with worked example. Stage outputs, common skip-failures, time investment per stage.45- [`references/tagging-and-clustering-discipline.md`](references/tagging-and-clustering-discipline.md) - Tag-at-artifact-level discipline, allow tag proliferation, cluster on patterns not overlap, name after clustering, tag dissent.46- [`references/pattern-naming-patterns.md`](references/pattern-naming-patterns.md) - Pattern names that work and fail. Avoiding category bloat, naming-with-conviction, the implication-legibility test.47- [`references/from-pattern-to-product-implication.md`](references/from-pattern-to-product-implication.md) - The bridge from pattern to implication. Falsifiability, multi-implication patterns, cost acknowledgment, the not-act implication.48- [`references/writing-for-decisions-not-decks.md`](references/writing-for-decisions-not-decks.md) - Document over deck, patterns lead, evidence appendix, opinionated voice, decision-input section.49- [`references/synthesis-review-and-validation.md`](references/synthesis-review-and-validation.md) - Participant review, adjacent-team review, quantitative validation, the challenge-the-synthesis session, iteration before publish.50- [`references/when-to-gather-more-data.md`](references/when-to-gather-more-data.md) - Pattern thinness, segment under-representation, contradictory clusters, decision time pressure, the we-have-enough trap.51- [`references/common-discovery-synthesis-failures.md`](references/common-discovery-synthesis-failures.md) - 11+ failure patterns with diagnoses and cures.5253---545556## Conditional methods5758Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.5960- Data-dump vs insight-theater vs actionable-synthesis: [method](references/domain-guide.md#data-dump-vs-insight-theater-vs-actionable-synthesis).61- Discovery research types: [method](references/domain-guide.md#discovery-research-types).62- The synthesis sequence: [method](references/domain-guide.md#the-synthesis-sequence).63- Tagging and clustering discipline: [method](references/domain-guide.md#tagging-and-clustering-discipline).64- Pattern naming: [method](references/domain-guide.md#pattern-naming).65- From pattern to product implication: [method](references/domain-guide.md#from-pattern-to-product-implication).66- Writing for decisions, not deck performance: [method](references/domain-guide.md#writing-for-decisions-not-deck-performance).67- The synthesis review and validation loop: [method](references/domain-guide.md#the-synthesis-review-and-validation-loop).68- When to halt and gather more data: [method](references/domain-guide.md#when-to-halt-and-gather-more-data).69- Common failure modes: [method](references/domain-guide.md#common-failure-modes).70- The framework: 12 considerations for discovery synthesis: [method](references/domain-guide.md#the-framework-12-considerations-for-discovery-synthesis).71- Closing: synthesis is where research earns its keep: [method](references/domain-guide.md#closing-synthesis-is-where-research-earns-its-keep).