Back to Details

talk-to-users

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Talk to users (the TAB system)

与用户沟通（TAB系统）

The best marketing to developers comes from talking to developers. That's it. Everything else in this repo is downstream of this skill.
Use this when: you've never done a real user interview, your messaging is clever but unverified, or you keep debating the roadmap internally instead of asking the people who feel the pain.
针对开发者的最佳营销方式就是与开发者沟通。仅此而已。本仓库中的所有其他内容都是这项技能的衍生。
适用场景：你从未做过真正的用户访谈，你的推广话术看似巧妙但未经验证，或者你一直在内部争论产品路线图，却不去询问那些真正感受到痛点的人。

The core idea

核心理念

Stand up a Technical Advisory Board: 30-50 people who represent your users and buyers, not grey-haired advisors telling you how to build. You interview them, on repeat, and let their words become your positioning, roadmap, and homepage copy.
A TAB call is not a demo and not a sales call. It's an interview. You never mention the product.
建立一个技术咨询委员会（TAB）：由30-50名能代表你的用户和付费客户的人员组成，而非那些告诉你如何构建产品的资深顾问。你需要反复与他们进行访谈，让他们的话语成为你的产品定位、路线图和首页文案的依据。
TAB访谈不是产品演示，也不是销售电话。这是一场访谈，你绝不能提及自己的产品。

Framework: the TAB system (Frankl)

框架：TAB系统（Frankl）

Composition
  • One+ representative of every persona that touches the product (see 
    who-is-this-for
    )
  • Both users (interact) and customers (pay), often different people
  • Target 30-50 members
Cadence
  • 30 minutes · one-on-one · monthly · for ~6 months
  • Zoom, recorded with permission, never in person
  • Same questions every time · never pitch
Recruitment (it's a numbers game)
  • Personalize every message, never batch-and-blast
  • Lead with their problem, not your startup
  • Max 4 sentences
  • ~10% reply → plan ~500 outreaches for ~50 members
  • No payment: early access, influence, swag
Template:
Dear [Name],

Your post about [specific problem] was genuinely sharp.

I'm building something to attack [that problem] and I'd value your view. Would
you consider joining my technical advisory board?

If so, reply and I'll set up a short call to explain what's involved.
人员构成
  • 至少一名代表每个接触产品的用户角色的成员（参见
    who-is-this-for
    ）
  • 包含用户（使用产品）和客户（付费购买）两类人群，他们通常是不同的人
  • 目标人数：30-50名成员
访谈节奏
  • 每次30分钟 · 一对一 · 每月一次 · 持续约6个月
  • 通过Zoom进行，经允许后录制，绝不进行线下访谈
  • 每次使用相同的问题 · 绝不进行产品推销
招募方式（这是一场数字游戏）
  • 每条消息都要个性化，绝不批量群发
  • 以他们的问题为切入点，而非你的创业项目
  • 最多4句话
  • 回复率约10% → 若要招募约50名成员，需计划约500次 outreach
  • 无需付费：提供提前使用权限、影响力机会、周边礼品
模板：
Dear [Name],

Your post about [specific problem] was genuinely sharp.

I'm building something to attack [that problem] and I'd value your view. Would
you consider joining my technical advisory board?

If so, reply and I'll set up a short call to explain what's involved.

The 7 questions (never more than 7 in 30 min)

7个问题（30分钟内绝不超过7个）

  1. Magic wand: "If you could wave a magic wand and change anything about how you do [task], what would it be?"
  2. The stakes: "If we delivered that, how would it change your day / your work?"
  3. Why now: "What's different about the world now that makes this more valuable than five years ago?"
  4. What caused this problem in your org?
  5. What have you tried, and why did it fall short?
  6. What happens if nothing changes for another year?
  7. Where do you go to stay current on this? (who/what they trust)
  1. 魔法棒问题：“如果你可以挥动魔法棒改变你做[某项任务]的任何方式，你会怎么做？”
  2. 影响问题：“如果我们实现了你的想法，这会如何改变你的日常工作？”
  3. 时效性问题：“与五年前相比，如今的世界有什么不同让这个需求更具价值？”
  4. 你的组织中是什么导致了这个问题？
  5. 你尝试过哪些解决方案，为什么它们未能达到预期？
  6. 如果未来一年情况没有任何改变，会发生什么？
  7. 你会通过哪些渠道了解该领域的最新动态？（你信任的人/信息源）

Analyze: turn transcripts into assets

分析：将访谈记录转化为资产

Highlight complete sentences (not fragments) into four buckets, then synthesize the top 3-5 of each, in the interviewee's exact words:
BucketYou're mining for
Painsbad outcomes, risks, obstacles
Gainsoutcomes they want
Jobswhat they're trying to accomplish
Environmental changestrends making the pain worse over time → your villain
Those four buckets feed directly into 
positioning-and-story
and 
value-prop-that-converts
.
将完整句子（而非片段）高亮并归入四个类别，然后总结出每个类别中排名前3-5的内容，完全保留受访者的原话：
类别挖掘目标
痛点不良结果、风险、障碍
收益他们期望达成的结果
任务他们试图完成的事项
环境变化随时间推移使痛点加剧的趋势 → 你的“反派角色”
这四个类别的内容将直接用于
positioning-and-story
和
value-prop-that-converts
。

Mistakes that look reasonable

看似合理的错误做法

  • Interviewing friends: they're nice and useless. You need people who'll say no.
  • Pitching mid-interview: the moment you demo, they start being polite instead of honest.
  • Leading questions: "wouldn't it be great if…" gets you the answer you fished for.
  • Batch outreach: a templated blast to 200 people gets 200 ignores. Personalize or don't send.
  • Asking for solutions: users are experts in their pain, not in your product. Mine the pain.
  • 采访朋友：他们很友善但毫无用处。你需要会说“不”的人。
  • 访谈中途推销产品：一旦你开始演示，他们就会变得客气而不再坦诚。
  • 诱导性问题：“如果……不是很棒吗？”只会得到你想要的答案。
  • 批量群发消息：向200人发送模板化消息会被200人忽略。要么个性化，要么不发送。
  • 询问解决方案：用户是自身痛点的专家，但不是你产品的专家。挖掘痛点即可。

Your next 30 minutes

你接下来30分钟要做的事

  • List every persona from 
    who-is-this-for
    ; you need TAB members for each.
  • Find 10 people who've publicly posted about the problem (HN, Reddit, GitHub issues, X).
  • Send 10 personalized, 4-sentence, problem-first invites. Today.
  • Lock your 7 questions (3 above + 4 tailored). Do not exceed 7.
  • After 3 calls, fill the Pains/Gains/Jobs/Changes table with real quotes.
Built from real dev-tool GTM experience, with frameworks from Adam Frankl (The Developer-Facing Startup) and Jakub Czakon (markepear.dev). When a framework can't make the call, that's what a human is for: The DevTool GTM Company.
  • 列出
    who-is-this-for
    中的所有用户角色；每个角色都需要对应的TAB成员。
  • 找到10名公开发布过相关问题的人（HN、Reddit、GitHub issues、X）。
  • 今天发送10条个性化、4句话、以问题为切入点的邀请。
  • 确定你的7个问题（上述3个+4个定制问题）。绝不超过7个。
  • 在3次访谈后，用真实的受访者原话填写“痛点/收益/任务/变化”表格。
基于真实的开发者工具GTM经验构建，融合了Adam Frankl（《面向开发者的创业公司》）和Jakub Czakon（markepear.dev）的框架。 当框架无法做出决策时，就需要人类的参与：The DevTool GTM Company。