[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GZWCK4VMZJ7CCG4ETSWSA":3,"skill-same:01M70GZWCK4VMZJ7CCG4ETSWSA":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70GZWCK4VMZJ7CCG4ETSWSA","user-research",null,"User interview techniques, persona creation, journey mapping, and research synthesis patterns. Use when planning research studies, conducting interviews, creating personas, or translating research findings into actionable design recommendations.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-research\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"research","user","user research","when","design","user interview","techniques","interviews","actionable","mapping","creation","recommendations","journey mapping","journey","patterns","personas","use","interview","persona","planning","2026-11-10 10:12:30",false,"---\nname: user-research\ndescription: User interview techniques, persona creation, journey mapping, and research synthesis patterns. Use when planning research studies, conducting interviews, creating personas, or translating research findings into actionable design recommendations.\n---\n\n# User Research Methodology\n\nSystematic approaches for understanding user needs, behaviors, and motivations to inform product decisions.\n\n## When to Activate\n\n- Planning user research studies\n- Conducting user interviews\n- Creating personas and journey maps\n- Synthesizing research findings\n- Translating insights into design recommendations\n- Validating product concepts with users\n\n## Research Methods\n\n### Method Selection Guide\n\n| Method | Best For | Sample Size | Time Investment |\n|--------|----------|-------------|-----------------|\n| **User Interviews** | Deep understanding, \"why\" | 5-12 users | 2-3 weeks |\n| **Contextual Inquiry** | Understanding environment | 3-6 users | 1-2 weeks |\n| **Usability Testing** | Interface validation | 5 users | 1 week |\n| **Surveys** | Quantitative validation | 100+ users | 1-2 weeks |\n| **Card Sorting** | Information architecture | 15-30 users | 1 week |\n| **Diary Studies** | Longitudinal behavior | 10-15 users | 2-4 weeks |\n\n### User Interviews\n\nOne-on-one conversations to understand user perspectives.\n\n#### Interview Structure (60 min)\n\n```\n1. INTRODUCTION (5 min)\n   - Thank them for participating\n   - Explain purpose (learning, not testing)\n   - Request permission to record\n   - Emphasize no right\u002Fwrong answers\n\n2. WARM-UP (5 min)\n   - Easy, open questions\n   - Build rapport\n   - \"Tell me about your role...\"\n\n3. CONTEXT (10 min)\n   - Current situation\n   - Tools and processes\n   - Goals and challenges\n   - \"Walk me through a typical day...\"\n\n4. DEEP DIVE (30 min)\n   - Specific experiences\n   - Pain points in detail\n   - Workarounds and adaptations\n   - \"Tell me about a time when...\"\n\n5. EXPLORATION (5 min)\n   - Reactions to concepts (if applicable)\n   - Ideal scenarios\n   - \"If you could wave a magic wand...\"\n\n6. WRAP-UP (5 min)\n   - Summary of key points\n   - Anything else to add\n   - Thank you and next steps\n```\n\n#### Question Techniques\n\n| Technique | Purpose | Example |\n|-----------|---------|---------|\n| **Open-ended** | Encourage stories | \"Tell me about...\" |\n| **Follow-up** | Dig deeper | \"Can you say more about that?\" |\n| **Clarification** | Ensure understanding | \"When you say X, what do you mean?\" |\n| **Contrast** | Explore differences | \"How does that compare to...?\" |\n| **Projection** | Uncover desires | \"What would ideal look like?\" |\n| **Silence** | Let them think | [Wait 5-10 seconds after answers] |\n\n#### Questions to Avoid\n\n| Avoid | Problem | Better |\n|-------|---------|--------|\n| \"Do you like...?\" | Yes\u002Fno answer | \"How do you feel about...?\" |\n| \"Would you use...?\" | Hypothetical behavior ≠ real | \"When did you last...?\" |\n| \"Don't you think...?\" | Leading | \"What do you think about...?\" |\n| \"What features...?\" | Solution-focused | \"What problems do you face?\" |\n\n### Contextual Inquiry\n\nObserve users in their natural environment.\n\n#### Protocol\n\n```\nPREPARATION:\n- Define focus areas\n- Prepare observation guide\n- Get necessary permissions\n- Test recording equipment\n\nDURING OBSERVATION:\n1. Arrive early, set up quietly\n2. Start with brief introduction\n3. Observe first, ask questions after\n4. Note everything (actions, environment, emotions)\n5. Use \"teach me\" framing\n\nOBSERVATION GUIDE:\n- What are they trying to accomplish?\n- What tools are they using?\n- What workarounds do they employ?\n- What frustrates them?\n- What's in their physical environment?\n- Who do they interact with?\n\nDEBRIEF:\n- Review observations with participant\n- Ask clarifying questions\n- Confirm interpretations\n```\n\n#### Observation Notes Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ Participant: [ID]     Date: [Date]     Location: [Where]    │\n├─────────────────────────────────────────────────────────────┤\n│ Task: [What they were doing]                                │\n│ Time: [How long it took]                                    │\n├─────────────────────────────────────────────────────────────┤\n│ Actions Observed:                                           │\n│ - [Step 1]                                                  │\n│ - [Step 2]                                                  │\n├─────────────────────────────────────────────────────────────┤\n│ Tools Used:                                                 │\n│ - [Tool 1]: [How used]                                      │\n│ - [Tool 2]: [How used]                                      │\n├─────────────────────────────────────────────────────────────┤\n│ Pain Points:                                                │\n│ - [Frustration observed]                                    │\n├─────────────────────────────────────────────────────────────┤\n│ Quotes:                                                     │\n│ - \"[Direct quote]\"                                          │\n├─────────────────────────────────────────────────────────────┤\n│ Opportunities:                                              │\n│ - [Potential improvement]                                   │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Think-Aloud Protocol\n\nHave users verbalize thoughts while performing tasks.\n\n```\nSETUP:\n\"I'd like you to complete some tasks while telling me what you're\nthinking. There are no wrong answers - I'm testing the design,\nnot you. Please say out loud whatever you're looking at, thinking,\nor feeling as you go through.\"\n\nPROMPTS DURING SESSION:\n- \"What are you thinking right now?\"\n- \"What do you expect to happen?\"\n- \"What are you looking for?\"\n- \"Why did you click there?\"\n- \"How does this compare to what you expected?\"\n\nAVOID:\n- Helping them complete tasks\n- Confirming if they're right\u002Fwrong\n- Explaining how things work\n- Interrupting their flow too much\n```\n\n## Research Synthesis\n\n### Affinity Mapping\n\nGroup observations to find patterns.\n\n```\nPROCESS:\n\n1. CAPTURE (Individual)\n   - Write one observation per sticky note\n   - Use participant quotes\n   - Include source identifier\n\n2. CLUSTER (Group)\n   - Spread all notes on wall\u002Fboard\n   - Group by similarity\n   - Don't pre-define categories\n   - Move notes until clusters emerge\n\n3. NAME (Group)\n   - Label each cluster\n   - Labels should describe the theme\n   - Not too broad, not too specific\n\n4. PRIORITIZE\n   - Which themes appear most frequently?\n   - Which have highest impact?\n   - Which are most actionable?\n\nEXAMPLE CLUSTERS:\n┌─────────────┐ ┌─────────────┐ ┌─────────────┐\n│ Trust       │ │ Efficiency  │ │ Support     │\n│ Concerns    │ │ Pain Points │ │ Needs       │\n├─────────────┤ ├─────────────┤ ├─────────────┤\n│ \"I don't    │ │ \"Takes too  │ │ \"Wish I     │\n│ know if     │ │ many clicks\"│ │ could ask   │\n│ it's safe\"  │ │             │ │ someone\"    │\n│             │ │ \"Have to    │ │             │\n│ \"Where's    │ │ enter same  │ │ \"Help docs  │\n│ my data?\"   │ │ info twice\" │ │ are useless\"│\n└─────────────┘ └─────────────┘ └─────────────┘\n```\n\n### Insight Generation\n\nTransform observations into actionable insights.\n\n```\nINSIGHT FORMULA:\n\n[User group] needs [need] because [motivation\u002Fcontext],\nbut currently [pain point], which means [consequence].\n\nEXAMPLE:\n\nFirst-time users need clear guidance during setup because\nthey're unfamiliar with the product, but currently the\nonboarding is overwhelming with too many options, which\nmeans they abandon before experiencing value.\n\nVALIDATION CHECKLIST:\n- [ ] Based on evidence from multiple participants\n- [ ] Identifies a real need (not a solution)\n- [ ] Explains the underlying motivation\n- [ ] Connects to business impact\n- [ ] Is actionable\n```\n\n## Personas\n\n### Persona Creation\n\nResearch-based archetypes representing user segments.\n\n#### Persona Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ [PHOTO PLACEHOLDER]                                          │\n│                                                              │\n│ NAME: [Fictional name]                                       │\n│ TITLE: [Role\u002Fcontext]                                        │\n│ ARCHETYPE: [2-3 word descriptor]                            │\n├─────────────────────────────────────────────────────────────┤\n│ QUOTE:                                                       │\n│ \"[Characteristic quote from research]\"                       │\n├─────────────────────────────────────────────────────────────┤\n│ DEMOGRAPHICS:                                                │\n│ Age: [Range]     Experience: [Level]                        │\n│ Context: [Work\u002Fhome environment]                            │\n├─────────────────────────────────────────────────────────────┤\n│ GOALS:                                                       │\n│ - Primary: [Main objective]                                  │\n│ - Secondary: [Supporting objective]                          │\n├─────────────────────────────────────────────────────────────┤\n│ PAIN POINTS:                                                 │\n│ - [Frustration 1]                                           │\n│ - [Frustration 2]                                           │\n│ - [Frustration 3]                                           │\n├─────────────────────────────────────────────────────────────┤\n│ BEHAVIORS:                                                   │\n│ - [How they approach problems]                              │\n│ - [Tools\u002Fresources they use]                                │\n│ - [Decision-making patterns]                                │\n├─────────────────────────────────────────────────────────────┤\n│ SCENARIO:                                                    │\n│ [Brief story of them using your product]                    │\n└─────────────────────────────────────────────────────────────┘\n```\n\n#### Persona Development Process\n\n```\n1. IDENTIFY VARIABLES\n   - What attributes differentiate users?\n   - Goals, behaviors, pain points, context\n\n2. ANALYZE PATTERNS\n   - Cluster research participants\n   - Find natural groupings\n   - Validate with quantitative data if available\n\n3. CREATE PERSONAS\n   - 3-5 personas is typical\n   - Each represents a distinct segment\n   - Include primary, secondary, negative persona\n\n4. VALIDATE\n   - Review with stakeholders\n   - Check against additional research\n   - Refine based on feedback\n\n5. ACTIVATE\n   - Share widely\n   - Reference in design discussions\n   - Update as you learn more\n```\n\n#### Persona Types\n\n| Type | Purpose | When to Create |\n|------|---------|----------------|\n| **Primary** | Main design target | Always |\n| **Secondary** | Important but not primary focus | When segments differ significantly |\n| **Negative** | Who we're NOT designing for | When edge cases distract |\n| **Proto-persona** | Hypothesis before research | Early exploration |\n\n## Journey Mapping\n\n### Journey Map Structure\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ JOURNEY MAP: [User Type] - [Scenario]                       │\n├─────────────────────────────────────────────────────────────┤\n│ STAGE      │ Awareness │ Consider │ Purchase │ Use │ Renew │\n├─────────────────────────────────────────────────────────────┤\n│ ACTIONS    │           │          │          │     │       │\n│ What they  │ • Sees ad │ • Visits │ • Selects│     │       │\n│ do         │ • Asks    │   site   │   plan   │     │       │\n│            │   friend  │ • Reads  │ • Enters │     │       │\n│            │           │   reviews│   payment│     │       │\n├─────────────────────────────────────────────────────────────┤\n│ THOUGHTS   │           │          │          │     │       │\n│ What they  │ \"I need   │ \"Is this │ \"This    │     │       │\n│ think      │ to solve  │ the right│ better be│     │       │\n│            │ this      │ choice?\" │ worth it\"│     │       │\n│            │ problem\"  │          │          │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ EMOTIONS   │    😊     │    😐    │    😟    │     │       │\n│ How they   │ Hopeful   │ Confused │ Anxious  │     │       │\n│ feel       │           │          │          │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ TOUCH-     │ Social    │ Website  │ Checkout │     │       │\n│ POINTS     │ media     │ Reviews  │ Email    │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ PAIN       │           │ Too many │ Payment  │     │       │\n│ POINTS     │           │ options  │ issues   │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ OPPORT-    │           │ Compare  │ Guest    │     │       │\n│ UNITIES    │           │ feature  │ checkout │     │       │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Journey Mapping Process\n\n```\n1. DEFINE SCOPE\n   - Which persona?\n   - Which scenario?\n   - Start and end points?\n\n2. GATHER DATA\n   - Interview transcripts\n   - Analytics data\n   - Support tickets\n   - Observation notes\n\n3. MAP THE STAGES\n   - What are the major phases?\n   - What triggers transitions?\n\n4. FILL IN LAYERS\n   - Actions at each stage\n   - Thoughts and questions\n   - Emotional state\n   - Touchpoints\n\n5. IDENTIFY OPPORTUNITIES\n   - Where are the pain points?\n   - Where can we improve?\n   - What's the priority?\n\n6. VALIDATE & SHARE\n   - Review with stakeholders\n   - Share findings\n   - Define action items\n```\n\n## Research Planning\n\n### Research Plan Template\n\n```markdown\n# Research Plan: [Study Name]\n\n## Objectives\n- Primary: [Main question to answer]\n- Secondary: [Additional questions]\n\n## Participants\n- Target: [User segment]\n- Sample size: [Number]\n- Recruitment: [How to find them]\n- Screener criteria: [Inclusion\u002Fexclusion]\n\n## Methodology\n- Method: [Interview\u002Fobservation\u002Ftesting]\n- Duration: [Session length]\n- Location: [Remote\u002Fin-person]\n- Facilitator: [Who]\n\n## Discussion Guide\n- [Link to guide]\n\n## Timeline\n| Phase | Dates |\n|-------|-------|\n| Recruitment | [Dates] |\n| Sessions | [Dates] |\n| Analysis | [Dates] |\n| Reporting | [Date] |\n\n## Deliverables\n- [ ] Raw notes\n- [ ] Synthesis document\n- [ ] Presentation\n- [ ] Recommendations\n```\n\n## Reporting Research\n\n### Research Report Structure\n\n```markdown\n# Research Findings: [Study Name]\n\n## Executive Summary\n[1-paragraph overview for stakeholders who won't read details]\n\n## Background\n- Objectives\n- Methodology\n- Participants (demographics, no PII)\n\n## Key Findings\n\n### Finding 1: [Headline]\n**Evidence**: [3+ supporting data points]\n**Impact**: [Why this matters]\n**Recommendation**: [What to do]\n\n### Finding 2: [Headline]\n...\n\n## Detailed Observations\n[Supporting details, quotes, examples]\n\n## Recommendations Summary\n| Priority | Finding | Recommendation | Effort |\n|----------|---------|----------------|--------|\n| 1 | [Finding] | [Action] | [Est.] |\n\n## Appendix\n- Screener\n- Discussion guide\n- Participant list (anonymized)\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **Confirmation Bias** | Seeking data that confirms beliefs | Ask open questions, look for disconfirming evidence |\n| **Leading Questions** | Influencing responses | Review questions for bias |\n| **Recency Effect** | Overweighting last interview | Synthesize across all participants |\n| **Sample Bias** | Wrong participants | Carefully screen, diverse recruitment |\n| **Hypothetical Questions** | \"Would you...?\" | Ask about past behavior instead |\n| **Shelf Research** | No action on findings | Include action items, follow up |\n\n## Best Practices\n\n1. **Observe behavior, not just words** - What people do matters more than what they say\n2. **Ask about the past** - \"When did you last...\" not \"Would you...\"\n3. **Follow the emotion** - Pain points reveal opportunities\n4. **Triangulate** - Validate findings across methods\n5. **Share broadly** - Research only has value if it influences decisions\n\n## References\n\n- [Interview Question Bank](examples\u002Finterview-questions.md) - Sample questions by topic\n- [Persona Examples](examples\u002Fpersonas.md) - Well-crafted persona examples\n","# User Research Methodology\n\nSystematic approaches for understanding user needs, behaviors, and motivations to inform product decisions.\n\n## When to Activate\n\n- Planning user research studies\n- Conducting user interviews\n- Creating personas and journey maps\n- Synthesizing research findings\n- Translating insights into design recommendations\n- Validating product concepts with users\n\n## Research Methods\n\n### Method Selection Guide\n\n| Method | Best For | Sample Size | Time Investment |\n|--------|----------|-------------|-----------------|\n| **User Interviews** | Deep understanding, \"why\" | 5-12 users | 2-3 weeks |\n| **Contextual Inquiry** | Understanding environment | 3-6 users | 1-2 weeks |\n| **Usability Testing** | Interface validation | 5 users | 1 week |\n| **Surveys** | Quantitative validation | 100+ users | 1-2 weeks |\n| **Card Sorting** | Information architecture | 15-30 users | 1 week |\n| **Diary Studies** | Longitudinal behavior | 10-15 users | 2-4 weeks |\n\n### User Interviews\n\nOne-on-one conversations to understand user perspectives.\n\n#### Interview Structure (60 min)\n\n```\n1. INTRODUCTION (5 min)\n   - Thank them for participating\n   - Explain purpose (learning, not testing)\n   - Request permission to record\n   - Emphasize no right\u002Fwrong answers\n\n2. WARM-UP (5 min)\n   - Easy, open questions\n   - Build rapport\n   - \"Tell me about your role...\"\n\n3. CONTEXT (10 min)\n   - Current situation\n   - Tools and processes\n   - Goals and challenges\n   - \"Walk me through a typical day...\"\n\n4. DEEP DIVE (30 min)\n   - Specific experiences\n   - Pain points in detail\n   - Workarounds and adaptations\n   - \"Tell me about a time when...\"\n\n5. EXPLORATION (5 min)\n   - Reactions to concepts (if applicable)\n   - Ideal scenarios\n   - \"If you could wave a magic wand...\"\n\n6. WRAP-UP (5 min)\n   - Summary of key points\n   - Anything else to add\n   - Thank you and next steps\n```\n\n#### Question Techniques\n\n| Technique | Purpose | Example |\n|-----------|---------|---------|\n| **Open-ended** | Encourage stories | \"Tell me about...\" |\n| **Follow-up** | Dig deeper | \"Can you say more about that?\" |\n| **Clarification** | Ensure understanding | \"When you say X, what do you mean?\" |\n| **Contrast** | Explore differences | \"How does that compare to...?\" |\n| **Projection** | Uncover desires | \"What would ideal look like?\" |\n| **Silence** | Let them think | [Wait 5-10 seconds after answers] |\n\n#### Questions to Avoid\n\n| Avoid | Problem | Better |\n|-------|---------|--------|\n| \"Do you like...?\" | Yes\u002Fno answer | \"How do you feel about...?\" |\n| \"Would you use...?\" | Hypothetical behavior ≠ real | \"When did you last...?\" |\n| \"Don't you think...?\" | Leading | \"What do you think about...?\" |\n| \"What features...?\" | Solution-focused | \"What problems do you face?\" |\n\n### Contextual Inquiry\n\nObserve users in their natural environment.\n\n#### Protocol\n\n```\nPREPARATION:\n- Define focus areas\n- Prepare observation guide\n- Get necessary permissions\n- Test recording equipment\n\nDURING OBSERVATION:\n1. Arrive early, set up quietly\n2. Start with brief introduction\n3. Observe first, ask questions after\n4. Note everything (actions, environment, emotions)\n5. Use \"teach me\" framing\n\nOBSERVATION GUIDE:\n- What are they trying to accomplish?\n- What tools are they using?\n- What workarounds do they employ?\n- What frustrates them?\n- What's in their physical environment?\n- Who do they interact with?\n\nDEBRIEF:\n- Review observations with participant\n- Ask clarifying questions\n- Confirm interpretations\n```\n\n#### Observation Notes Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ Participant: [ID]     Date: [Date]     Location: [Where]    │\n├─────────────────────────────────────────────────────────────┤\n│ Task: [What they were doing]                                │\n│ Time: [How long it took]                                    │\n├─────────────────────────────────────────────────────────────┤\n│ Actions Observed:                                           │\n│ - [Step 1]                                                  │\n│ - [Step 2]                                                  │\n├─────────────────────────────────────────────────────────────┤\n│ Tools Used:                                                 │\n│ - [Tool 1]: [How used]                                      │\n│ - [Tool 2]: [How used]                                      │\n├─────────────────────────────────────────────────────────────┤\n│ Pain Points:                                                │\n│ - [Frustration observed]                                    │\n├─────────────────────────────────────────────────────────────┤\n│ Quotes:                                                     │\n│ - \"[Direct quote]\"                                          │\n├─────────────────────────────────────────────────────────────┤\n│ Opportunities:                                              │\n│ - [Potential improvement]                                   │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Think-Aloud Protocol\n\nHave users verbalize thoughts while performing tasks.\n\n```\nSETUP:\n\"I'd like you to complete some tasks while telling me what you're\nthinking. There are no wrong answers - I'm testing the design,\nnot you. Please say out loud whatever you're looking at, thinking,\nor feeling as you go through.\"\n\nPROMPTS DURING SESSION:\n- \"What are you thinking right now?\"\n- \"What do you expect to happen?\"\n- \"What are you looking for?\"\n- \"Why did you click there?\"\n- \"How does this compare to what you expected?\"\n\nAVOID:\n- Helping them complete tasks\n- Confirming if they're right\u002Fwrong\n- Explaining how things work\n- Interrupting their flow too much\n```\n\n## Research Synthesis\n\n### Affinity Mapping\n\nGroup observations to find patterns.\n\n```\nPROCESS:\n\n1. CAPTURE (Individual)\n   - Write one observation per sticky note\n   - Use participant quotes\n   - Include source identifier\n\n2. CLUSTER (Group)\n   - Spread all notes on wall\u002Fboard\n   - Group by similarity\n   - Don't pre-define categories\n   - Move notes until clusters emerge\n\n3. NAME (Group)\n   - Label each cluster\n   - Labels should describe the theme\n   - Not too broad, not too specific\n\n4. PRIORITIZE\n   - Which themes appear most frequently?\n   - Which have highest impact?\n   - Which are most actionable?\n\nEXAMPLE CLUSTERS:\n┌─────────────┐ ┌─────────────┐ ┌─────────────┐\n│ Trust       │ │ Efficiency  │ │ Support     │\n│ Concerns    │ │ Pain Points │ │ Needs       │\n├─────────────┤ ├─────────────┤ ├─────────────┤\n│ \"I don't    │ │ \"Takes too  │ │ \"Wish I     │\n│ know if     │ │ many clicks\"│ │ could ask   │\n│ it's safe\"  │ │             │ │ someone\"    │\n│             │ │ \"Have to    │ │             │\n│ \"Where's    │ │ enter same  │ │ \"Help docs  │\n│ my data?\"   │ │ info twice\" │ │ are useless\"│\n└─────────────┘ └─────────────┘ └─────────────┘\n```\n\n### Insight Generation\n\nTransform observations into actionable insights.\n\n```\nINSIGHT FORMULA:\n\n[User group] needs [need] because [motivation\u002Fcontext],\nbut currently [pain point], which means [consequence].\n\nEXAMPLE:\n\nFirst-time users need clear guidance during setup because\nthey're unfamiliar with the product, but currently the\nonboarding is overwhelming with too many options, which\nmeans they abandon before experiencing value.\n\nVALIDATION CHECKLIST:\n- [ ] Based on evidence from multiple participants\n- [ ] Identifies a real need (not a solution)\n- [ ] Explains the underlying motivation\n- [ ] Connects to business impact\n- [ ] Is actionable\n```\n\n## Personas\n\n### Persona Creation\n\nResearch-based archetypes representing user segments.\n\n#### Persona Template\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ [PHOTO PLACEHOLDER]                                          │\n│                                                              │\n│ NAME: [Fictional name]                                       │\n│ TITLE: [Role\u002Fcontext]                                        │\n│ ARCHETYPE: [2-3 word descriptor]                            │\n├─────────────────────────────────────────────────────────────┤\n│ QUOTE:                                                       │\n│ \"[Characteristic quote from research]\"                       │\n├─────────────────────────────────────────────────────────────┤\n│ DEMOGRAPHICS:                                                │\n│ Age: [Range]     Experience: [Level]                        │\n│ Context: [Work\u002Fhome environment]                            │\n├─────────────────────────────────────────────────────────────┤\n│ GOALS:                                                       │\n│ - Primary: [Main objective]                                  │\n│ - Secondary: [Supporting objective]                          │\n├─────────────────────────────────────────────────────────────┤\n│ PAIN POINTS:                                                 │\n│ - [Frustration 1]                                           │\n│ - [Frustration 2]                                           │\n│ - [Frustration 3]                                           │\n├─────────────────────────────────────────────────────────────┤\n│ BEHAVIORS:                                                   │\n│ - [How they approach problems]                              │\n│ - [Tools\u002Fresources they use]                                │\n│ - [Decision-making patterns]                                │\n├─────────────────────────────────────────────────────────────┤\n│ SCENARIO:                                                    │\n│ [Brief story of them using your product]                    │\n└─────────────────────────────────────────────────────────────┘\n```\n\n#### Persona Development Process\n\n```\n1. IDENTIFY VARIABLES\n   - What attributes differentiate users?\n   - Goals, behaviors, pain points, context\n\n2. ANALYZE PATTERNS\n   - Cluster research participants\n   - Find natural groupings\n   - Validate with quantitative data if available\n\n3. CREATE PERSONAS\n   - 3-5 personas is typical\n   - Each represents a distinct segment\n   - Include primary, secondary, negative persona\n\n4. VALIDATE\n   - Review with stakeholders\n   - Check against additional research\n   - Refine based on feedback\n\n5. ACTIVATE\n   - Share widely\n   - Reference in design discussions\n   - Update as you learn more\n```\n\n#### Persona Types\n\n| Type | Purpose | When to Create |\n|------|---------|----------------|\n| **Primary** | Main design target | Always |\n| **Secondary** | Important but not primary focus | When segments differ significantly |\n| **Negative** | Who we're NOT designing for | When edge cases distract |\n| **Proto-persona** | Hypothesis before research | Early exploration |\n\n## Journey Mapping\n\n### Journey Map Structure\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ JOURNEY MAP: [User Type] - [Scenario]                       │\n├─────────────────────────────────────────────────────────────┤\n│ STAGE      │ Awareness │ Consider │ Purchase │ Use │ Renew │\n├─────────────────────────────────────────────────────────────┤\n│ ACTIONS    │           │          │          │     │       │\n│ What they  │ • Sees ad │ • Visits │ • Selects│     │       │\n│ do         │ • Asks    │   site   │   plan   │     │       │\n│            │   friend  │ • Reads  │ • Enters │     │       │\n│            │           │   reviews│   payment│     │       │\n├─────────────────────────────────────────────────────────────┤\n│ THOUGHTS   │           │          │          │     │       │\n│ What they  │ \"I need   │ \"Is this │ \"This    │     │       │\n│ think      │ to solve  │ the right│ better be│     │       │\n│            │ this      │ choice?\" │ worth it\"│     │       │\n│            │ problem\"  │          │          │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ EMOTIONS   │    😊     │    😐    │    😟    │     │       │\n│ How they   │ Hopeful   │ Confused │ Anxious  │     │       │\n│ feel       │           │          │          │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ TOUCH-     │ Social    │ Website  │ Checkout │     │       │\n│ POINTS     │ media     │ Reviews  │ Email    │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ PAIN       │           │ Too many │ Payment  │     │       │\n│ POINTS     │           │ options  │ issues   │     │       │\n├─────────────────────────────────────────────────────────────┤\n│ OPPORT-    │           │ Compare  │ Guest    │     │       │\n│ UNITIES    │           │ feature  │ checkout │     │       │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Journey Mapping Process\n\n```\n1. DEFINE SCOPE\n   - Which persona?\n   - Which scenario?\n   - Start and end points?\n\n2. GATHER DATA\n   - Interview transcripts\n   - Analytics data\n   - Support tickets\n   - Observation notes\n\n3. MAP THE STAGES\n   - What are the major phases?\n   - What triggers transitions?\n\n4. FILL IN LAYERS\n   - Actions at each stage\n   - Thoughts and questions\n   - Emotional state\n   - Touchpoints\n\n5. IDENTIFY OPPORTUNITIES\n   - Where are the pain points?\n   - Where can we improve?\n   - What's the priority?\n\n6. VALIDATE & SHARE\n   - Review with stakeholders\n   - Share findings\n   - Define action items\n```\n\n## Research Planning\n\n### Research Plan Template\n\n```markdown\n# Research Plan: [Study Name]\n\n## Objectives\n- Primary: [Main question to answer]\n- Secondary: [Additional questions]\n\n## Participants\n- Target: [User segment]\n- Sample size: [Number]\n- Recruitment: [How to find them]\n- Screener criteria: [Inclusion\u002Fexclusion]\n\n## Methodology\n- Method: [Interview\u002Fobservation\u002Ftesting]\n- Duration: [Session length]\n- Location: [Remote\u002Fin-person]\n- Facilitator: [Who]\n\n## Discussion Guide\n- [Link to guide]\n\n## Timeline\n| Phase | Dates |\n|-------|-------|\n| Recruitment | [Dates] |\n| Sessions | [Dates] |\n| Analysis | [Dates] |\n| Reporting | [Date] |\n\n## Deliverables\n- [ ] Raw notes\n- [ ] Synthesis document\n- [ ] Presentation\n- [ ] Recommendations\n```\n\n## Reporting Research\n\n### Research Report Structure\n\n```markdown\n# Research Findings: [Study Name]\n\n## Executive Summary\n[1-paragraph overview for stakeholders who won't read details]\n\n## Background\n- Objectives\n- Methodology\n- Participants (demographics, no PII)\n\n## Key Findings\n\n### Finding 1: [Headline]\n**Evidence**: [3+ supporting data points]\n**Impact**: [Why this matters]\n**Recommendation**: [What to do]\n\n### Finding 2: [Headline]\n...\n\n## Detailed Observations\n[Supporting details, quotes, examples]\n\n## Recommendations Summary\n| Priority | Finding | Recommendation | Effort |\n|----------|---------|----------------|--------|\n| 1 | [Finding] | [Action] | [Est.] |\n\n## Appendix\n- Screener\n- Discussion guide\n- Participant list (anonymized)\n```\n\n## Anti-Patterns\n\n| Anti-Pattern | Problem | Solution |\n|--------------|---------|----------|\n| **Confirmation Bias** | Seeking data that confirms beliefs | Ask open questions, look for disconfirming evidence |\n| **Leading Questions** | Influencing responses | Review questions for bias |\n| **Recency Effect** | Overweighting last interview | Synthesize across all participants |\n| **Sample Bias** | Wrong participants | Carefully screen, diverse recruitment |\n| **Hypothetical Questions** | \"Would you...?\" | Ask about past behavior instead |\n| **Shelf Research** | No action on findings | Include action items, follow up |\n\n## Best Practices\n\n1. **Observe behavior, not just words** - What people do matters more than what they say\n2. **Ask about the past** - \"When did you last...\" not \"Would you...\"\n3. **Follow the emotion** - Pain points reveal opportunities\n4. **Triangulate** - Validate findings across methods\n5. **Share broadly** - Research only has value if it influences decisions\n\n## References\n\n- [Interview Question Bank](examples\u002Finterview-questions.md) - Sample questions by topic\n- [Persona Examples](examples\u002Fpersonas.md) - Well-crafted persona examples\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-research",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-research",{"tool":65,"command":66},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-research",{"tool":68,"command":69},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill user-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fdesign\u002Fuser-research\u002FSKILL.md",true,[],[74,91,125,149,171,191],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":83,"publishedAt":44},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[84,85,86,87,88,89,90],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":105,"publishedAt":44},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[97,100],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[93,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":135,"publishedAt":44},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[131,132],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000036","内容创作者",[127,25,136,137,138,139,140,141,114,142,143,144,27,40,145,146,147,148],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":44},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[155],{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,127,159,160,147,161,162,163,164,165,166,167,168,112,169,27,40,106,170],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":181,"publishedAt":44},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[177,178,179,180],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":133,"categoryName":134,"taxonomyType":103,"taxonomyTypeDesc":104},[182,89,183,184,185,186,122,27,40,187,188,189,190],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":199,"publishedAt":44},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[197,198],{"categoryNo":81,"categoryName":82,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":133,"categoryName":134,"taxonomyType":103,"taxonomyTypeDesc":104},[200,89,201,110,202,188,27,183,186,40,189],"Rules","writing rules","project rules"]