Leon Wirth·
Synthesized 14 interviews plus survey data into two crisp personas and the real reason setup drops off
Synthesize qualitative user research from multiple sources into actionable personas, journey maps, and prioritized opportunity areas.
User Research Insight Synthesis & Pattern Extractor
You are a principal user researcher at a top product company. Synthesize my raw user research into structured, actionable insights.\n\nPRODUCT/SERVICE: {{product_or_service_name}}\nRESEARCH OBJECTIVE: {{what_you_wanted_to_learn}}\nTARGET USERS: {{user_profile}}\nRESEARCH METHODS USED: {{methods — e.g., 'Interviews, usability tests, survey, analytics review'}}\nNUMBER OF PARTICIPANTS/SOURCES: {{sample_size}}\n\nRAW RESEARCH DATA (paste interview notes, survey responses, observation notes, support tickets, analytics insights):\n{{research_data}}\n\nOUTPUT — User Research Synthesis Report:\n\n## 1. RESEARCH SNAPSHOT\n- Study summary (3 sentences)\n- Confidence level: [High / Medium / Low] with rationale\n- Key limitations of the research\n\n## 2. USER SEGMENT PROFILES\nIdentify 2-4 distinct user segments from the data:\n\n**Segment: [Name]**\n- **Description**: Who they are, their context, their goals\n- **Representative quote**: "..."\n- **Frequency in sample**: X of N participants\n- **Top 3 needs**: 1. [ ] 2. [ ] 3. [ ]\n- **Top 3 pain points**: 1. [ ] 2. [ ] 3. [ ]\n- **Behavioral signature**: What they DO (not just what they say)\n- **Tech proficiency**: [Power user / Comfortable / Basic / Struggles]\n- **Willingness to pay**: [High / Medium / Low / Not assessed]\n\n## 3. CROSS-CUTTING THEMES\nSynthesize across all participants to identify 5-7 thematic patterns:\n\n| Theme | Description | Supporting Evidence | Frequency | Severity | Opportunity? |\n|-------|-------------|-------------------|-----------|----------|-------------|\n\nEach theme should:\n- Be named as a user need or problem (not a solution)\n- Include at least 3 pieces of supporting evidence (quotes, observations, data points)\n- Have severity rated as: [Critical / Major / Minor / Nice-to-have]\n\n## 4. JOURNEY MAP — CURRENT STATE\nMap the typical user journey across key stages:\n\n| Stage | User Actions | Thoughts | Pain Points | Emotion | Opportunities |\n|-------|-------------|----------|-------------|---------|---------------|\n\nStages to cover (customize to {{product_or_service_name}}):\n1. Awareness/Discovery\n2. Consideration/Sign-up\n3. Onboarding/First Use\n4. Regular Use\n5. Advanced Use\n6. Support/Problem Resolution\n7. Renewal/Upgrade/Churn\n\n## 5. TOP INSIGHTS (Ranked)\n\n**INSIGHT #1: [Provocative statement]**\n- Evidence: 3-5 supporting data points/quotes\n- Counter-evidence: Any data that contradicts this? Address it.\n- Implication: What should we do differently?\n- Confidence: [High / Medium / Low]\n\n(Repeat for top 5-7 insights)\n\n## 6. PRIORITIZED OPPORTUNITY MATRIX\n| Opportunity | User Impact | Business Value | Feasibility | Evidence Strength | Priority | Hypothesis to Test |\n|-------------|-------------|----------------|-------------|------------------|----------|--------------------|\n(8-12 opportunities, ranked by Impact × Evidence Strength)\n\n## 7. RECOMMENDED NEXT STEPS\n- Immediate actions (this week): 2-3 items\n- Short-term research (next 30 days): 2-3 follow-up studies to run\n- Design implications: 3-5 specific changes to consider\n- Questions still unanswered: List of known unknowns\n\n## 8. RESEARCH REPOSITORY\n- Tagging structure for future reference\n- Participant anonymization notes\n- Raw data indexing system
Ergebnisse
# User Research Synthesis — Onboarding for a Personal Finance App
**Product:** budgeting app for young professionals. **Objective:** why do users abandon during setup? **Methods:** 14 interviews + 600 survey responses + funnel analytics. **Confidence:** Medium-High.
## 1. Snapshot
Two clear segments emerged; the drop-off is concentrated at bank-linking, and it's as much emotional (trust) as functional.
## 2. Segments
**"Anxious First-Timer" (8/14)** — never budgeted before, low tech confidence, top need: reassurance. Quote: "I almost didn't connect my bank — felt like handing over my keys."
**"Spreadsheet Graduate" (4/14)** — already DIY-budgets, wants control and export. Top pain: rigid categories.
## 3. Cross-Cutting Themes
| Theme | Evidence | Severity | Opportunity? |
|-------|----------|----------|--------------|
| Bank-linking fear | 9 mentions, 41% survey | Critical | Yes |
| Category rigidity | 6 mentions | Major | Yes |
| Unclear value before setup | 5 mentions | Major | Yes |
## 4. Journey (current state, abbreviated)
| Stage | Pain | Emotion | Opportunity |
|-------|------|---------|-------------|
| Sign-up | Asked to link bank too early | Anxious | Show value first |
| First use | Categories don't match life | Frustrated | Editable categories |
## 5. Top Insight
**"Users won't connect a bank to an app that hasn't earned trust yet."** Implication: delay bank-linking until after a value demo. Confidence: High.
## 6. Opportunity Matrix (top 3)
1. "Try before you link" demo mode — High impact, strong evidence.
2. Editable categories at setup — High impact, medium effort.
3. Trust cues (encryption badge, read-only copy) at the link step — quick win.
## 7. Next Steps
This week: add read-only reassurance copy to the link screen. Next 30 days: prototype demo mode, usability-test with 5 Anxious First-Timers.
Modell: Claude Sonnet 4
8 Likes2 SavesScore: 6