[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792RCH85H1Z69MP6FCV2YJ7":3,"skill-same:01M792RCH85H1Z69MP6FCV2YJ7":61},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M792RCH85H1Z69MP6FCV2YJ7","customer-research",null,"Mine interviews, tickets, reviews and communities for the exact words customers use; output personas and JTBD. Use when mining customer voice, interview transcripts, or user pains.","poorvith-mp\u002Fskills-marketing","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792P4C4Z12T0V4B97Z9MNX3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fcustomer-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customer-research\nlast_reviewed: 2026-09-06\ngroup: Foundation\ndescription: >-\n  Mine interviews, tickets, reviews and communities for the exact words customers use; output\n  personas and JTBD. Use when mining customer voice, interview transcripts, or user pains.\n---\n\n# Customer Research\n\nCustomer research is extracting the unvarnished voice of the customer (VOC) to guide product development and marketing messaging. High-impact research uncovers Jobs to Be Done (JTBD), identifies switching triggers, isolates exact pain vocabulary, and turns qualitative interviews into structured persona dossiers.\n\n## 1. The Jobs to Be Done (JTBD) Interview Framework\nCustomers do not buy products; they \"hire\" them to make progress in a specific life or operational situation:\n- **The 4 Forces of Customer Progress (Bob Moesta Framework)**:\n  1. *Push of the Current Situation*: The pain, frustration, or inefficiency of the existing solution that makes staying intolerable.\n  2. *Pull of the New Solution*: The attractive promise of the new product and how it will improve their operational reality.\n  3. *Anxiety of the Unknown*: Fear that the new solution will break, fail to integrate, or cost too much time to learn.\n  4. *Habit & Inertia*: Comfort with the legacy routine and reluctance to change existing muscle memory.\n\n## 2. The 5 Golden Interview Questions\nWhen conducting customer discovery interviews (20–30 minutes), never ask hypothetical questions (\"Would you buy X?\"). Ask about past behaviors:\n1. *\"Take me back to the day you first started looking for a solution like this. What happened that day that made you say 'I need to fix this'?\"* (Identifies the switching trigger).\n2. *\"What other solutions did you try or consider before choosing us, and why did you rule them out?\"* (Identifies true competitors and trade-offs).\n3. *\"What was the hardest part about getting set up or convincing your team to use this?\"* (Identifies onboarding and adoption friction).\n4. *\"What can you do now that you couldn't do before?\"* (Isolates the core value proposition in the customer's exact words).\n5. *\"If you could no longer use this tomorrow, what would you replace it with?\"* (Identifies mission-critical dependencies).\n\n## 3. Review Mining & Digital Watering Hole Extraction\nMine unprompted customer discussions across public channels (Reddit, G2 reviews, Discord servers, support tickets):\n- **Pain Vocabulary Mining**: Copy verbatim phrases customers use to describe their frustration into a raw VOC spreadsheet.\n- **Feature Gap Identification**: Categorize complaints about incumbent competitors into actionable product roadmap inputs.\n- *Synthesis Rule*: When 5 distinct customers use the exact same phrase to describe their problem, adopt that exact phrase as your landing page headline.\n\n## 4. Structured Customer Persona Dossier\nSynthesize findings into actionable profiles, not cartoon demographic avatars:\n- **Role & Constraints**: Senior Backend Engineer; budget authority up to $5,000\u002Fyr; constrained by SOC 2 compliance and tight sprint deadlines.\n- **Core Job to Be Done**: \"Quickly deploy reliable background job queues in TypeScript without managing self-hosted Redis infrastructure.\"\n- **Objections & Hesitations**: \"Worried about API rate limits and bill shock from usage-based pricing.\"\n\n## Critical Rules\n1. Never ask customers what features you should build; ask what problems they are experiencing and what progress they are trying to make.\n2. Record and transcribe customer interviews to capture their exact vocabulary word-for-word.\n3. Disregard hypothetical customer feedback (\"I would definitely pay $50 for that\"); only count verified past actions and paid commitments.\n\n## Verification Checklist\n- [ ] Qualitative interviews conducted with at least 5 representative users from the target ICP.\n- [ ] Switching triggers and the 4 Forces of Progress documented.\n- [ ] Verbatim Voice of Customer (VOC) phrases extracted and tagged in a central repository.\n- [ ] Personas defined by jobs-to-be-done and operational constraints rather than demographics.\n- [ ] Findings synthesized and shared directly with product engineering and copywriting teams.\n\n## Anti-Patterns\n- NEVER lead the witness during interviews with suggestive questions (\"Don't you think our UI is much cleaner?\").\n- NEVER build buyer personas based on internal company assumptions without direct customer validation.\n- NEVER conduct research once and shelve it; interview at least 2 churned or won customers every month.\n","# Customer Research\n\nCustomer research is extracting the unvarnished voice of the customer (VOC) to guide product development and marketing messaging. High-impact research uncovers Jobs to Be Done (JTBD), identifies switching triggers, isolates exact pain vocabulary, and turns qualitative interviews into structured persona dossiers.\n\n## 1. The Jobs to Be Done (JTBD) Interview Framework\nCustomers do not buy products; they \"hire\" them to make progress in a specific life or operational situation:\n- **The 4 Forces of Customer Progress (Bob Moesta Framework)**:\n  1. *Push of the Current Situation*: The pain, frustration, or inefficiency of the existing solution that makes staying intolerable.\n  2. *Pull of the New Solution*: The attractive promise of the new product and how it will improve their operational reality.\n  3. *Anxiety of the Unknown*: Fear that the new solution will break, fail to integrate, or cost too much time to learn.\n  4. *Habit & Inertia*: Comfort with the legacy routine and reluctance to change existing muscle memory.\n\n## 2. The 5 Golden Interview Questions\nWhen conducting customer discovery interviews (20–30 minutes), never ask hypothetical questions (\"Would you buy X?\"). Ask about past behaviors:\n1. *\"Take me back to the day you first started looking for a solution like this. What happened that day that made you say 'I need to fix this'?\"* (Identifies the switching trigger).\n2. *\"What other solutions did you try or consider before choosing us, and why did you rule them out?\"* (Identifies true competitors and trade-offs).\n3. *\"What was the hardest part about getting set up or convincing your team to use this?\"* (Identifies onboarding and adoption friction).\n4. *\"What can you do now that you couldn't do before?\"* (Isolates the core value proposition in the customer's exact words).\n5. *\"If you could no longer use this tomorrow, what would you replace it with?\"* (Identifies mission-critical dependencies).\n\n## 3. Review Mining & Digital Watering Hole Extraction\nMine unprompted customer discussions across public channels (Reddit, G2 reviews, Discord servers, support tickets):\n- **Pain Vocabulary Mining**: Copy verbatim phrases customers use to describe their frustration into a raw VOC spreadsheet.\n- **Feature Gap Identification**: Categorize complaints about incumbent competitors into actionable product roadmap inputs.\n- *Synthesis Rule*: When 5 distinct customers use the exact same phrase to describe their problem, adopt that exact phrase as your landing page headline.\n\n## 4. Structured Customer Persona Dossier\nSynthesize findings into actionable profiles, not cartoon demographic avatars:\n- **Role & Constraints**: Senior Backend Engineer; budget authority up to $5,000\u002Fyr; constrained by SOC 2 compliance and tight sprint deadlines.\n- **Core Job to Be Done**: \"Quickly deploy reliable background job queues in TypeScript without managing self-hosted Redis infrastructure.\"\n- **Objections & Hesitations**: \"Worried about API rate limits and bill shock from usage-based pricing.\"\n\n## Critical Rules\n1. Never ask customers what features you should build; ask what problems they are experiencing and what progress they are trying to make.\n2. Record and transcribe customer interviews to capture their exact vocabulary word-for-word.\n3. Disregard hypothetical customer feedback (\"I would definitely pay $50 for that\"); only count verified past actions and paid commitments.\n\n## Verification Checklist\n- [ ] Qualitative interviews conducted with at least 5 representative users from the target ICP.\n- [ ] Switching triggers and the 4 Forces of Progress documented.\n- [ ] Verbatim Voice of Customer (VOC) phrases extracted and tagged in a central repository.\n- [ ] Personas defined by jobs-to-be-done and operational constraints rather than demographics.\n- [ ] Findings synthesized and shared directly with product engineering and copywriting teams.\n\n## Anti-Patterns\n- NEVER lead the witness during interviews with suggestive questions (\"Don't you think our UI is much cleaner?\").\n- NEVER build buyer personas based on internal company assumptions without direct customer validation.\n- NEVER conduct research once and shelve it; interview at least 2 churned or won customers every month.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Foundation",1788652800000,"main","e9ea1069b8d051ec6f88c3bdc4290183b8e68c94","skills\u002Fcustomer-research","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:44",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add poorvith-mp\u002Fskills-marketing --skill customer-research",{"tool":41,"command":42},"bunx","bunx skills add poorvith-mp\u002Fskills-marketing --skill customer-research",{"tool":44,"command":45},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-marketing --skill customer-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fcustomer-research\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"customer-research.skill","OTHER","其他",3038,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fcustomer-research\u002Fcustomer-research.skill",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Frouting.yaml","REFERENCE","参考文档",1000,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fcustomer-research\u002Fevals\u002Frouting.yaml",[62,69,75,81,88,94],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M792Y3WSAZ5ABHX58QPMWXMH","youtube-clipper","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M792Y1ABERS38QWQCJ9CKWJB","youtube-b-roll-maker","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-b-roll-maker\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":65,"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":80,"publishedAt":19},"01M792XZCWKZV16GNK3QQR9M2X","x-twitter-intelligence-analyst","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-intelligence-analyst\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M792XTYRW8ZSHPSPVMK301QW","visual-assets","Generate on-brand images: OG cards, blog heroes, social graphics and mockups. Use when creating Open Graph cards, hero visuals, or brand graphics.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-assets\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M792XR5BZ510MFZETMPAAJBW","viral-hook-generator","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fviral-hook-generator\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M792XPJB02Q3HQTKKYZTKJ8A","video-script-writer","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-marketing\u002Fblob\u002Fmain\u002Fskills\u002Fvideo-script-writer\u002FSKILL.md",[],[]]