Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-discover/skills/research-synthesis

research-synthesis

Verified

Turn raw interview notes and feedback into themes, insights, and opportunity statements. Use when you have a pile of research and need to know what it says before deciding anything.

FileKindSize
SKILL.mdskill md13.8 KB
examples/sample-industrial.mdmarkdown2.3 KB
examples/sample.mdmarkdown2.5 KB
template.mdmarkdown1.8 KB

examples/sample-industrial.md

View on GitHub
# Research Synthesis Example: Industrial

**Research:** notes from 6 plant visits and 3 phone calls with maintenance engineers (Northfield Automation)
**Question:** what stops plants from replacing aging controllers, even when parts are scarce?
**Hypothesis going in:** "It's the price."

**Why this example exists:** industrial research is smaller and slower, so strength of signal and
sampling honesty matter more. It also shows two sources disagreeing.

---

```markdown
## Research frame
9 sources (6 on-site, 3 calls), recruited through 3 partners, so skewed to partner-served plants.
Hypothesis held: price blocks replacement. [FROM YOU]

## Themes
| Theme | Sources | N |
|---|---|---|
| "We can't give up a weekend of production" | V1, V2, V4, V5, V6, C2 | 6 of 9 |
| "Nobody else understands our program" | V1, V3, V5, C1, C3 | 5 of 9 |
| Price mentioned as the main blocker | V6 | 1 of 9 |

## Insights
| # | Insight | Evidence | N | Confidence |
|---|---|---|---|---|
| 1 | The barrier is downtime and program risk, not price | V1 "...a weekend we don't have"; V5 "...one engineer knows that code" | 6 and 5 of 9 | Suggestive (partner-skewed sample) |

## Opportunity statements
| # | "I need to..." | From | Ideas heard |
|---|---|---|---|
| 1 | "...swap the controller inside a shift we already have." | 1 | "Pre-wire the bracket" (V4) |
| 2 | "...keep my existing program working without rewriting it." | 1 | "Import tool" (C1) |

## Contradictions
V6, the only plant citing price, runs the oldest controllers and is nearest to failure.
Price may matter once downtime is already unavoidable. That's a hypothesis, not a finding.
The partner calls (C1-C3) were more technical than the on-site visits: partners may see program
risk more than plant managers do.

## What the research does not show
- No procurement or finance interviews (price may live there)
- No plants that already replaced their controllers (the opposite case)
- Sample came through partners, so direct-served plants are unrepresented
```

## What to learn from this

- **The team's hypothesis was mostly absent from the data,** and the skill said so plainly.
- **One outlier was kept, not dismissed,** with a hypothesis for why it differs.
- **The gaps list names who holds the price story** (procurement), so the next round targets them.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall