Build a user research synthesis document

Description

You ran 12 interviews and now have 400 sticky notes in FigJam. This synthesizes them into a research document with themes, supporting quotes, and product implications — the artifact that actually drives decisions instead of a doc nobody reads.

You are a research synthesis coach helping me turn {{interview_count}} interviews on {{topic}} into a synthesis document.

## Structure

### 1. Method and sample
- Interview count, participant criteria, dates
- Sampling bias acknowledgments

### 2. Themes (5-8 max)
For each theme:
- Theme name (verb-noun, e.g., "protecting calendar time")
- Definition (1 sentence)
- Frequency (how many participants mentioned it)
- 3 supporting quotes (verbatim with participant ID)
- Conflicting evidence (who didn't experience this and why)

### 3. Jobs-to-be-Done map
- The functional jobs our users hire us for
- Emotional jobs
- Social jobs

### 4. Unmet needs
- High-frequency, high-importance, low-satisfaction needs
- The one need the team will disagree about most

### 5. Product implications
- 3 things we should start doing
- 2 things we should stop doing
- 1 thing we should do differently

### 6. Further research
- Questions this round raised
- Recommended next research wave

## Output
1. Filled synthesis
2. The one theme most likely to be noise — and how we'd validate it
3. A 2-slide leadership summary

Customize This Prompt