gingiris-user-interview
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese⚠️ 2C 产品的渠道调整
⚠️ Channel Adjustment for 2C Products
本 skill 默认 dev / B2B 渠道。2C 消费品 / 教育 / 应用：获客主战场是 垂类社区 + 短视频 + 垂直 KOL，按地区公开数据选第一平台（如印尼/泰国短视频已反超 Facebook）。KOL 优先 nano / micro 垂类——粉丝越多互动率越低，micro > mega 性价比更高。完整 2C 渠道数据库 + 公开来源见 → 。
gingiris-seo-geo/references/2c-adaptation.mdThis skill defaults to dev / B2B channels. 2C Consumer Goods / Education / Apps: The main customer acquisition channels are vertical communities + short videos + vertical KOLs. Select the top platform based on regional public data (e.g., short videos have surpassed Facebook in Indonesia/Thailand). Prioritize nano / micro vertical KOLs—the more followers, the lower the engagement rate; micro KOLs offer higher cost-effectiveness than mega KOLs. Complete 2C channel database + public sources → .
gingiris-seo-geo/references/2c-adaptation.md用户访谈与冷启动运营实战手册
User Interview & Cold-Start Operations Practical Playbook
播客一手案例与引用边界：。
references/podcast-evidence.md🌍 Language / 语言: 中文 | Interview Guide | Cold-Start Ops
First-hand podcast cases and citation boundaries: .
references/podcast-evidence.md🌍 Language: Chinese | Interview Guide | Cold-Start Ops
核心原则
Core Principles
"产品的 founder，在刚开始的前半年都会密集的做大量的用户访谈。像 HeyGen 就是半年，founder 自己做了 937 场；Wisperflow 和 Higgsfield 都做了 500 场以上——就是不断做访谈，不断改。" —— 生姜iris
关键洞察：用户访谈不是调研工具，是 PMF 发现引擎。访谈频率与产品成功率正相关。
"Founders of products will conduct intensive user interviews in the first six months. For example, HeyGen's founder did 937 interviews in six months; Wisperflow and Higgsfield both did over 500 interviews—continuous interviews and iterations." —— Ginger Iris
Key Insight: User interviews are not just research tools, but PMF discovery engines. Interview frequency is positively correlated with product success rate.
Token Top10 访谈法（2026 招牌方法）
Token Top10 Interview Method (2026 Signature Method)
把访谈从"调研动作"变成"日常运营循环"的最短路径，已在多个 AI Agent 项目全线复用：
- 后台按 token 消耗 / 用量拉 Top10 用户 list（每周刷新）
- 约共享屏幕访谈，必须录屏——看真实操作 > 听口述
- Transcript 喂 AI，自动提取 feature request / bug 直接进 Linear（或任意 issue 工具）
- 次日回访：告知"你提的 X 已修/已排期"——反馈闭环本身就是留存杠杆
- 节奏：每天至少 2 场；访谈后截 5-10 分钟关键片段直接给产研
配套动作：
- 新访谈员先 mock interview + 全程录屏 + 复盘 highlight，再上真实用户
- KOL 访谈二合一：合作 YouTuber 顺便做用户访谈 + 可用性测试，一次合作拿两份价值；视频访谈 20-30 分钟 ROI 最高
- 访谈资产化：一场付费用户访谈可同时产出功能需求 + SEO 素材 + reseller 线索三件套
The shortest path to turn interviews from "research actions" into "daily operation cycles", fully reused in multiple AI Agent projects:
- Pull the Top10 user list from the backend based on token consumption / usage (refreshed weekly)
- Schedule shared-screen interviews, mandatory recording—observing real operations is better than listening to verbal descriptions
- Feed transcripts to AI, automatically extract feature requests / bugs and directly sync to Linear (or any issue tool)
- Follow up the next day: Notify users "Your request X has been fixed/scheduled"—feedback closure itself is a retention lever
- Rhythm: At least 2 interviews per day; after each interview, clip 5-10 minutes of key segments and send directly to product and R&D teams
Supporting Actions:
- New interviewers must first conduct mock interviews + full recording + highlight reviews before interviewing real users
- Two-in-one KOL interviews: Collaborate with YouTubers to conduct user interviews + usability testing simultaneously, getting two values from one collaboration; 20-30 minute video interviews offer the highest ROI
- Interview assetization: A paid user interview can simultaneously produce three outputs: functional requirements + SEO materials + reseller leads
邀约触达节奏（2026 更新）
Invitation Touchpoint Rhythm (2026 Update)
- 1/3/7/14 天四次触达：Day 1 首发 → Day 3 → Day 7 → Day 14 各跟进一次
- 双通道：邮件模板 + 邮箱反查 LinkedIn 私信；邮件无回复转 LinkedIn 补一轮
- 话术用宽泛理由（"团队早期想做用户访谈"），不暴露真实筛选原因，避免用户带着预设表演
- Four touchpoints on Day 1/3/7/14: First send on Day 1 → follow up on Day 3 → Day 7 → Day 14
- Two channels: Email template + LinkedIn private message via email reverse lookup; if no reply to email, send a follow-up on LinkedIn
- Use broad reasons in the script ("The team wants to conduct user interviews in the early stage"), do not expose the real screening criteria to avoid users performing with presuppositions
标杆锚点
Benchmark Anchors
Wisprflow：launch 前人工 onboard 前 500 名用户、逐个视频访谈，用积累的势能带 launch；HuggingFace：scale up 前 8 个月调研 + 500 场用户访谈。
2026-07 增补（播客一手提炼）：
- 据转述（AFFiNE 前 COO 口径）：Gamma / Notion / HeyGen 均在半年内做了约 1,000 场用户访谈，"用户提到的不好的点就真的去解"。
- Gamma / HeyGen / Lovable 等成功产品的共同路径：半年 500-1,000 场访谈打磨产品细节，才有资格谈增长——"大量的人忽视了前面这半年到一年脏活累活的过程"。
- 反例（匿名项目，reported）：跳过访谈打磨直接烧钱投放，单个注册成本高达几十美金、单个付费用户成本几百美金——"没有逻辑，但有钱"。
Wisprflow: Manually onboarded the first 500 users and conducted one-on-one video interviews before launch, leveraging accumulated momentum for launch; HuggingFace: Conducted research + 500 user interviews in the first 8 months before scaling up.
2026-07 Supplement (First-hand Podcast Extraction):
- According to the former COO of AFFiNE: Gamma / Notion / HeyGen all conducted about 1,000 user interviews within six months, "truly solving the pain points mentioned by users".
- Common path for successful products like Gamma / HeyGen / Lovable: Polish product details through 500-1,000 interviews in six months before talking about growth—"Many people ignore the dirty and tiring work in the first six months to a year".
- Counterexample (anonymous project, reported): Skipping interview polishing and directly spending money on user acquisition, resulting in a single registration cost of tens of dollars and a single paid user cost of hundreds of dollars—"No logic, but deep pockets".
用户访谈执行框架（5步）
User Interview Execution Framework (5 Steps)
Step 1：确定目标与筛选用户
Step 1: Define Goals and Screen Users
用户优先级：
| 优先级 | 用户类型 | 价值 |
|---|---|---|
| P0 | 付费用户 | 已验证付费意愿，最高价值 |
| P0 | 高频活跃用户 | 深度了解产品，反馈最有效 |
| P1 | 竞品用户 | 提供竞争视角 |
| P1 | 流失用户 | 暴露产品真实问题 |
| P2 | 注册未付费用户 | 转化障碍洞察 |
User Priority:
| Priority | User Type | Value |
|---|---|---|
| P0 | Paid Users | Verified willingness to pay, highest value |
| P0 | High-frequency Active Users | Deep product understanding, most effective feedback |
| P1 | Competitor Users | Provide competitive perspectives |
| P1 | Churned Users | Expose real product problems |
| P2 | Registered Non-paid Users | Insights into conversion barriers |
Step 2：邀约与排期
Step 2: Invitation and Scheduling
跟进节奏：Day 1 → Day 3 → Day 7 → Day 10（全渠道：LinkedIn/Email/Telegram/Discord）
邀约话术核心：说明目的 + 时长承诺（30分钟）+ 录屏说明 + 价值交换
Follow-up Rhythm: Day 1 → Day 3 → Day 7 → Day 10 (omnichannel: LinkedIn/Email/Telegram/Discord)
Core Invitation Script: Explain purpose + duration commitment (30 minutes) + recording explanation + value exchange
Step 3：访谈执行（30-45分钟）
Step 3: Interview Execution (30-45 minutes)
必须：1人主持 + 1人记录 + 必须录屏（含共享屏幕）
核心问题框架：
- 背景了解：职业、获客渠道、使用时长、核心功能、竞品
- 工作流探索：解决什么问题？之前怎么做？现在有什么变化？
- 竞品对比：用了哪些竞品？各自场景？我们的优劣势？
- 痛点挖掘：不爽的地方？Bug？难用的功能？"魔法棒"问题
- 付费意愿：之前付费过什么？愿意付多少？什么促使升级？
关键技巧：屏幕共享观察 > 用户口述。让用户演示真实操作，观察卡点。
Mandatory: 1 host + 1 note-taker + mandatory recording (including shared screen)
Core Question Framework:
- Background Understanding: Occupation, customer acquisition channel, usage duration, core features, competitors
- Workflow Exploration: What problem does it solve? How did you do it before? What changes have occurred now?
- Competitor Comparison: Which competitors have you used? What scenarios are they for? Our advantages and disadvantages?
- Pain Point Mining: What's unsatisfactory? Bugs? Hard-to-use features? "Magic wand" question
- Willingness to Pay: Have you paid for similar products before? How much are you willing to pay? What drives upgrades?
Key Technique: Observing screen sharing is better than listening to user descriptions. Let users demonstrate real operations and observe bottlenecks.
Step 4：收尾与后续
Step 4: Closing and Follow-up
- 大使计划邀请
- 转介绍请求
- 24小时内完成访谈复盘模板
- Invitation to ambassador program
- Request for referrals
- Complete interview review template within 24 hours
Step 5：数据汇总（每5-10场）
Step 5: Data Summary (Every 5-10 Interviews)
汇总共同需求/痛点 → 更新功能优先级 → 修正用户画像 → 调整产品方向
Summarize common needs/pain points → update feature priorities → revise user portraits → adjust product direction
有效访谈 vs 无效访谈判别（2026-07 增补）
Distinguishing Effective vs. Ineffective Interviews (2026-07 Supplement)
"无效用户访谈就是做投资人演讲——自己说 80%，用户已经神游太虚了。" —— 生姜iris
| 维度 | 无效访谈 | 有效访谈 |
|---|---|---|
| 谁在说 | 你说 80%，用户神游太虚 | 听用户讲他是怎么用的 |
| 看什么 | 只听口述、看演示脚本 | 让用户共享屏幕，看真实操作 |
| 场景 | 假设场景 / 自己讲产品 | 真实场景、真实 user case |
| 心态 | 把用户当成纯粹的数字 | EGO 放低，和用户做朋友 |
判别依据：你构建的 user journey 和用户实际的 user journey 完全不一样——只有共享屏幕才能暴露这个 gap。
付费意愿双逻辑："访谈里说愿意付费和最终付费是两套逻辑"——一旦真要买单，每个人都理智得不行。访谈中的付费表态只作方向参考，验证一律以真实支付行为为准（对应下文"付费归因四时间戳"）。
"An ineffective user interview is like giving an investor pitch—you talk 80% of the time, and the user is already distracted." —— Ginger Iris
| Dimension | Ineffective Interview | Effective Interview |
|---|---|---|
| Who Talks | You talk 80% of the time, user is distracted | Listen to users talk about how they use the product |
| What to Observe | Only listen to verbal descriptions, look at demo scripts | Let users share screens and observe real operations |
| Scenario | Hypothetical scenarios / you introduce the product | Real scenarios, real user cases |
| Mindset | Treat users as pure numbers | Put aside ego, make friends with users |
Judgment Basis: The user journey you constructed is completely different from the user's actual journey—only screen sharing can expose this gap.
Dual Logic of Willingness to Pay: "Saying willing to pay in interviews and actually paying are two different logics"—when it comes to real payment, everyone is extremely rational. Payment statements in interviews are only for directional reference; verification must be based on real payment behavior (corresponding to the "Four Timestamps for Payment Attribution" below).
访谈驱动迭代闭环（实战路径，2026-07 增补）
Interview-driven Iteration Loop (Practical Path, 2026-07 Supplement)
- 第一场访谈可以做满 2 小时：深度用户往往比你更了解场景、行业和所有竞品，能帮你总结出真正的价值主张和当下最大的比较性优势。
- 真诚运营换深度反馈：一位早期海外深度用户后来主动写了 2,000 字带截图动图的长评，逐条指出"花了太多时间在用户不需要的功能场景上"+ 具体 bug——"如果不是因为你太真诚，我不会花两小时写这个"。
- 全员拆解 → 限期修完：收到长评后全员开会逐条拆解，用 1-2 个月修完其中全部 bug。
- 闭环回告：修完/排期后回访用户"你提的 X 已修"——反馈闭环本身就是留存杠杆（呼应 Token Top10 第 4 步）。
- 踩坑警示：访谈反馈上传后若仍由 1 号位单人拍板取舍，大量用户输入会被忽略——产研运必须共同定目标、共同消化访谈精华。
信任建立速度基准（自述口径）：无论职级多高，保持每天一线直接和用户聊天，2 个月建立的用户信任可以超过不下场的同事 1 年多——用户会主动掏心掏肺、跨部门为你背书。一线高频直聊是访谈质量的前提。
- The first interview can last up to 2 hours: Deep users often understand scenarios, industries, and all competitors better than you, and can help you summarize the real value proposition and the current biggest comparative advantage.
- Sincere operations for in-depth feedback: An early overseas deep user later voluntarily wrote a 2,000-word long review with screenshots and GIFs, pointing out "spent too much time on functional scenarios users don't need" + specific bugs—"I wouldn't have spent two hours writing this if you weren't so sincere".
- Full-team dismantling → fixed within deadline: After receiving the long review, the whole team held a meeting to dismantle each item, fixing all bugs within 1-2 months.
- Closure notification: Follow up with users after fixing/scheduling "Your request X has been fixed"—feedback closure itself is a retention lever (echoing Step 4 of Token Top10)
- Pitfall Warning: If interview feedback is still decided solely by the top leader after being uploaded, a lot of user input will be ignored—product, R&D, and operations must jointly set goals and digest the essence of interviews.
Trust Building Speed Benchmark (Self-reported): No matter how high the position is, keep chatting directly with users on the frontline every day. The user trust built in 2 months can exceed that of colleagues who don't get involved in over a year—users will take the initiative to open up and endorse you across departments. High-frequency direct frontline communication is the prerequisite for interview quality.
Beta 测试设计框架
Beta Test Design Framework
测试目标三层结构
Three-tier Test Goal Structure
| 层级 | 维度 | 数据收集手段 |
|---|---|---|
| 价值验证层 | 是否解决核心痛点 | 访谈 |
| 体验感知层 | 速度、易用性、效果 | 观察法（屏幕录制/连线） |
| 缺口识别层 | 功能缺失、体验卡顿 | 结构化问卷 + Bug反馈 |
| Tier | Dimension | Data Collection Method |
|---|---|---|
| Value Verification Tier | Whether core pain points are solved | Interviews |
| Experience Perception Tier | Speed, usability, effectiveness | Observation (screen recording/remote connection) |
| Gap Identification Tier | Missing features, experience bottlenecks | Structured questionnaires + Bug feedback |
测试任务设计原则
Test Task Design Principles
- 任务模拟完整工作流，非孤立功能点
- 任务长度触发"等待"场景（暴露性能问题）
- 提供 prompt example 降低认知负担
- 明确说明"Beta不稳定是正常的"
- Tasks simulate complete workflows, not isolated feature points
- Task length triggers "waiting" scenarios (expose performance issues)
- Provide prompt examples to reduce cognitive burden
- Clearly state "Beta instability is normal"
连线实时测试核心
Core of Real-time Remote Testing
- 强调"观察"而非"测试用户"
- Think Aloud Protocol（边做边说）
- 利用加载等待期收集用户背景（被低估的技巧）
- Emphasize "observation" rather than "testing users"
- Think Aloud Protocol (talk while doing)
- Use loading waiting time to collect user background (underrated technique)
五问法（结构化收尾）
Five-question Method (Structured Closing)
- 你觉得这是一个怎样的产品？（让用户贴标签）
- 最满意的功能是什么？
- 哪个环节最卡顿或困惑？
- 如果明天正式上线，你愿意付费吗？为什么？
- 最希望下个版本加入什么？
- What kind of product do you think this is? (Let users label it)
- What is the most satisfying feature?
- Which link is the most laggy or confusing?
- If it launches officially tomorrow, would you be willing to pay? Why?
- What feature do you most want to see in the next version?
冷启动用户运营方法论
Cold-Start User Operations Methodology
冷触达漏斗
Cold Touchpoint Funnel
触达 → 回复邀请(~47%) → 深度追踪(~47%) → 合格在测(~24%) → 持续活跃关键：ICP 匹配的 50 人 > 泛触达 500 人
Touch → Reply to invitation(~47%) → Deep tracking(~47%) → Qualified for testing(~24%) → Sustained activityKey: 50 users matching ICP > 500 users with broad touchpoints
Messaging 迭代方法
Messaging Iteration Method
| 话术类型 | 效果 |
|---|---|
| 功能驱动（做什么） | 低转化，吸引错误画像 |
| 场景驱动（解决什么问题） | 转化率提升 ~83% |
| 痛点对比（之前怎么做） | 最高转化 |
规律：越具体的痛点描述，转化率越高。
| Message Type | Effect |
|---|---|
| Feature-driven (what it does) | Low conversion, attracts wrong user portraits |
| Scenario-driven (what problem it solves) | Conversion rate increases by ~83% |
| Pain point comparison (how you did it before) | Highest conversion |
Rule: The more specific the pain point description, the higher the conversion rate.
两层 Beta 用户体系
Two-tier Beta User System
| 层级 | 画像 | 门槛 | 权益 |
|---|---|---|---|
| Tier 1 Creative Partners | KOL/行业专家 | 持续使用>7天 + 高质量反馈 | Pro权限 + 创始人直达 + Case Study |
| Tier 2 Early Beta Users | 符合ICP的专业用户 | 提交具体改进建议 | 早期访问 + 路线图参与 |
| Tier | Portrait | Threshold | Benefits |
|---|---|---|---|
| Tier 1 Creative Partners | KOL/industry experts | Continuous usage >7 days + high-quality feedback | Pro access + direct founder contact + Case Study |
| Tier 2 Early Beta Users | Professional users matching ICP | Submit specific improvement suggestions | Early access + roadmap participation |
激活与付费基准（2026 实测）
Activation and Payment Benchmarks (2026 Actual Measurement)
访谈招募优先级与首轮实验
Interview Recruitment Priority and First-round Experiment
优先顺序：真实付费/高频用户 → 已激活未付费 → 新注册未激活 → 流失用户 → 泛目标画像。首轮先发 10 条逐人定制消息，记录回复、预约、到场和有效洞察，再决定是否扩量。访谈中优先让用户共享屏幕完成真实任务；观点必须与行为日志、激活和支付时间戳交叉验证。
激活定义必须是行为阈值，不能是"注册过 / 登录过"：
| 产品类型 | 行为阈值实例 |
|---|---|
| Agent 类 | 完成 ≥2 个任务 |
| 对话类 | 连续 3 天每天 ≥20 轮对话 |
| 工具类 | 开始跑任务，或单次使用超 5 分钟 |
| DAU 口径 | 以 unique message send 计，剔除内部用户 |
转化合格线：
- 注册 → 付费 >5% 为合格线：Pro-C 5-8%、SMB 10-15%（大 C 类 1.5-3%）
- 阶段目标要"够得着"：付费率 0.1% 的产品先定 1%/3 个月，不要直接定 5%
流失可运营化：两次对话后 24h 不回访 = 流失，自动触发挽回邮件——流失定义一旦行为化，挽回就能自动化。
付费归因四时间戳：注册时间 × 激活时间 × 支付时间 × 最近登录，四点交叉判定真实付费驱动（是哪个功能、哪场访谈、哪次触达带来的付费）。
Priority order: Real paid/high-frequency users → Activated non-paid users → New registered non-activated users → Churned users → Broad target portraits. First send 10 personalized messages one by one, record replies, appointments, attendance, and effective insights, then decide whether to scale up. Prioritize letting users share screens to complete real tasks during interviews; opinions must be cross-validated with behavior logs, activation, and payment timestamps.
Activation must be defined by behavioral thresholds, not "registered / logged in":
| Product Type | Behavioral Threshold Examples |
|---|---|
| Agent Category | Complete ≥2 tasks |
| Conversation Category | ≥20 rounds of dialogue per day for 3 consecutive days |
| Tool Category | Start running tasks, or single usage exceeds 5 minutes |
| DAU Definition | Counted by unique message send, excluding internal users |
Conversion Qualification Line:
- Registration → Payment >5% is the qualification line: Pro-C 5-8%, SMB 10-15% (large C category 1.5-3%)
- Stage goals should be "achievable": Products with 0.1% payment rate should first set 1%/3 months, not directly 5%
Churn Operationalization: No follow-up within 24h after two conversations = churn, automatically trigger recovery emails—once churn is defined by behavior, recovery can be automated.
Four Timestamps for Payment Attribution: Registration time × Activation time × Payment time × Last login, cross-verify the four points to determine the real payment driver (which feature, interview, or touchpoint led to payment).
用户分级标准
User Grading Standards
| 等级 | 特征 | 运营策略 |
|---|---|---|
| S级 | 高频 + 付费 + 愿意宣传 | 大使优先，CEO直接对接 |
| A级 | 高频 + 有付费潜力 | 内测优先权，定期回访 |
| B级 | 偶尔使用 + 无明确付费意向 | 引导核心功能，推动转化 |
| C级 | 低活跃 + 无付费意向 | 减少投入，关注自然留存 |
| Grade | Characteristics | Operation Strategy |
|---|---|---|
| S-level | High-frequency + paid + willing to promote | Priority for ambassador program, direct CEO contact |
| A-level | High-frequency + potential to pay | Priority for internal testing, regular follow-ups |
| B-level | Occasional usage + no clear payment intention | Guide to core features, drive conversion |
| C-level | Low activity + no payment intention | Reduce investment, focus on natural retention |
流失分析框架
Churn Analysis Framework
| 流失类型 | 典型原因 |
|---|---|
| 性能类 | 设备过热/卡顿、加载超时、崩溃 |
| 工作流断层类 | 缺少下游集成、功能完成度不足 |
| ICP不匹配类 | 无数据主权、项目制无长期需求 |
| Messaging不匹配类 | 触达价值主张 ≠ 产品实际价值 |
流失用户访谈三问：
- 什么时候开始不用的？当时在做什么？
- 遇到了什么问题，还是找到了替代品？
- 如果我们解决了X问题，你会回来吗？
| Churn Type | Typical Reasons |
|---|---|
| Performance Type | Device overheating/lag, loading timeout, crash |
| Workflow Disruption Type | Lack of downstream integration, insufficient feature completeness |
| ICP Mismatch Type | No data sovereignty, project-based with no long-term needs |
| Messaging Mismatch Type | Touchpoint value proposition ≠ actual product value |
Three Questions for Churned User Interviews:
- When did you stop using it? What were you doing at that time?
- Did you encounter any problems, or find an alternative?
- If we solve problem X, would you come back?
PMF 价值评估矩阵
PMF Value Evaluation Matrix
按「素材主权 × 使用频率」评估：
| 用户类型 | 素材主权 | PMF价值 | 流失风险 |
|---|---|---|---|
| 独立创作者 | 完全主权 | ⭐⭐⭐⭐⭐ | 低 |
| 机构决策者 | 完全主权 | ⭐⭐⭐⭐ | 价格敏感 |
| 自由职业者 | 临时主权 | ⭐⭐⭐ | 项目结束即流失 |
| 机构执行人员 | 无主权 | ⭐⭐ | 数据授权顾虑 |
Evaluate based on "Material Sovereignty × Usage Frequency":
| User Type | Material Sovereignty | PMF Value | Churn Risk |
|---|---|---|---|
| Independent Creators | Full sovereignty | ⭐⭐⭐⭐⭐ | Low |
| Institutional Decision-makers | Full sovereignty | ⭐⭐⭐⭐ | Price-sensitive |
| Freelancers | Temporary sovereignty | ⭐⭐⭐ | Churn after project ends |
| Institutional Executors | No sovereignty | ⭐⭐ | Concerns about data authorization |
工具链
Toolchain
| 类别 | 工具 | 用途 |
|---|---|---|
| 问卷 | Typeform | 用户调研问卷 |
| 录音 | Grain, Fathom | 访谈录音转写 |
| 数据库 | Airtable | 用户数据库管理 |
| 日程 | Calendly | 预约访谈 |
| 触达 | LinkedIn, Discord | 用户联系与社区 |
| Category | Tool | Purpose |
|---|---|---|
| Questionnaire | Typeform | User research questionnaires |
| Recording | Grain, Fathom | Interview recording transcription |
| Database | Airtable | User database management |
| Scheduling | Calendly | Interview appointment |
| Touchpoint | LinkedIn, Discord | User contact and community |
完整参考文档
Complete Reference Documents
| 文档 | 内容 |
|---|---|
| references/interview-guide.md | 完整用户访谈指南（HeyGen 937场方法论、问题框架、模板、FAQ） |
| references/cold-start-ops.md | Beta测试设计框架、冷启动用户运营、流失分析、可复用模板 |
| references/templates.md | 访谈复盘模板、用户画像表、Feature Request Tracker |
| Document | Content |
|---|---|
| references/interview-guide.md | Complete user interview guide (HeyGen's 937-interview methodology, question framework, templates, FAQ) |
| references/cold-start-ops.md | Beta test design framework, cold-start user operations, churn analysis, reusable templates |
| references/templates.md | Interview review template, user portrait form, Feature Request Tracker |