Back to Skills
Discovery

Research Synthesis Engine

Synthesize multiple research sources into coherent insights with clear evidence chains.

Now includes the former JTBD Extractor.

/research-synthesis-engine

Time Saved

8+ hrs → 1 hr

Compared to doing it manually

Slash Command

/research-synthesis-engine

Type this in Claude to run the skill

The Problem

Research insights live in scattered docs, slides, and people's heads. When you need evidence, you can't find it. Decisions get made without the full picture.

What You Get

  • ✓Cross-source pattern detection
  • ✓Theme clustering with evidence strength
  • ✓Convergence and contradiction analysis
  • ✓Research gaps identified
  • ✓Prioritized opportunity list
  • ✓Atomic insight database

How to use this skill

  1. 1Start your free trial — every skill is included
  2. 2Set up your company context with /welcome
  3. 3Type /research-synthesis-engine in Claude to run the skill

Best For

Research sprintsQuarterly reviewsBusiness casesStrategy development

Frequently Asked Questions

Yes. Ask for the jobs lens, or give it research about buying or switching decisions. It writes job stories ("When [situation], I want to [motivation], so I can [expected outcome]"), maps the four forces of progress (push, pull, anxiety, habit), and turns each feature request in your sources into the job behind it. This replaces the former JTBD Extractor skill.

JTBD is a framework that focuses on the underlying goal customers are trying to achieve, rather than their demographic or the features they request. It helps you understand the "job" your product is "hired" to do.

Research synthesis combines findings from multiple research activities (interviews, surveys, analytics) into coherent insights. It identifies patterns, contradictions, and key takeaways that inform product decisions.

Use affinity mapping: write insights on sticky notes, group related ones, identify themes. Look for patterns across sources. Distinguish between what users say, what they do, and what they need.

Lead with insights, not methodology. Use the format: "We learned [insight] which means [implication] so we should [recommendation]." Include supporting quotes but don't overwhelm with data.

Start free trialView Workflow →