Back to Details

time-to-first-value

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Time to first value (get them to the first win)

首次价值达成时间（助力用户获得首次成功）

For a dev tool, the product is the pitch. A developer tries it alone and decides in minutes. Acquisition without activation is just a faster way to lose people.
Use this when: people sign up or star the repo and then nothing, they get it working once and never come back, your docs assume the reader already understands it, or you are about to spend on a launch or a channel while the first ten minutes still leak.
对于开发者工具而言，产品本身就是最好的宣传。开发者会自行试用，并在几分钟内做出判断。只获取用户却不激活他们，只会更快地流失用户。
适用场景： 用户注册或给仓库标星后毫无动静，成功使用一次就不再返回，你的文档默认读者已了解产品，或者你准备投入资源进行发布或渠道推广，但首次使用流程仍存在用户流失问题。

The core idea

核心理念

You can nail your positioning, your homepage, and your launch, and still lose everyone in the first ten minutes. For a dev tool the first run is the sale: the developer tries it, alone, without talking to you, and decides. Two gates, straight from Frankl's DREAM funnel:
  • Evaluation: can they get it working over a weekend, with zero human help? (the weekend test)
  • Activation: how fast do they reach their first real win, the "I'm awesome" moment (time to first value)?
Fix this before you scale acquisition. Pouring users into a leaky first run just loses them faster, and 
know-if-its-working
will show you that retention, not signups, is the number that matters.
你可能精准定位了产品、优化了首页、完成了发布，但仍会在用户首次使用的前十分钟内流失所有人。对于开发者工具来说，首次使用就是“成交”：开发者自行试用，无需与你沟通，就能做出判断。这两道关卡直接源自Frankl的DREAM漏斗：
  • 评估： 他们能否在无需任何人工帮助的情况下，在周末让产品正常运行？（周末测试）
  • 激活： 他们需要多久才能获得第一次真正的成功，也就是那种“我太棒了”的时刻（首次价值达成时间）？
在扩大用户获取规模之前先解决这个问题。将用户引入存在漏洞的首次使用流程只会加速流失，而
know-if-its-working
会告诉你，留存率而非注册量才是关键指标。

The two thresholds

两个关键阈值

The weekend test (Frankl). A motivated developer should get your product doing something real over a weekend, without a call, a demo, or an email to you. If they cannot, that is your single highest-leverage work, above any channel, launch, or homepage tweak.
Time to first value (Czakon: "time to Hello World"). Measured in minutes, not hours, and the first meaningful win in the same sitting, not after an onboarding call next Tuesday. The first "Hello World" should be minutes in; the first real "oh, this is useful" should be that same session.
The win belongs to the developer, not your product (Frankl: the developer is the hero). The aha is "look what I just did," not "look what our platform can do." Design the first run so the developer feels capable, fast.
周末测试（Frankl提出）：一位有动力的开发者应该能在周末让你的产品实现实际功能，无需电话沟通、演示或向你发送邮件。如果做不到，这就是你最具影响力的工作，优先级高于任何渠道、发布或首页优化。
首次价值达成时间（Czakon称之为“Hello World达成时间”）：以分钟而非小时为单位计算，首次有意义的成功应在同一场会话内实现，而非等到下周二的入职培训之后。第一个“Hello World”应该在几分钟内完成；第一个真正的“哦，这很有用”的时刻也应发生在同一场会话中。
成功属于开发者，而非你的产品（Frankl提出：开发者是主角）：顿悟时刻应该是“看我刚刚做到了什么”，而非“看我们的平台能做什么”。设计首次使用流程，让开发者快速感受到自己的能力。

Framework: the friction log (Czakon)

框架：摩擦日志（Czakon提出）

The core tool. Do not try to document every path. Nail the ONE most common path to first value.
  1. Pick the single core journey a new developer takes to their first win.
  2. Walk it yourself as a stranger: new machine or incognito, no insider shortcuts, no filling in gaps from memory.
  3. At every step, log three things: the question they have, the frustration they hit, the friction or barrier that makes them stop.
  4. Fix the obvious barriers first. Cut the top three places a motivated dev would quit.
  5. Put a metric on each core moment so you can see where they drop.
核心工具。无需记录所有路径，只需聚焦通往首次成功的唯一最常见路径。
  1. 选定新开发者获得首次成功的单一核心流程。
  2. 以陌生人的身份亲自走一遍流程：使用新机器或隐身模式，不走内部捷径，不凭借记忆填补信息空白。
  3. 在每一步记录三件事：他们产生的疑问、遇到的挫败感、导致他们停滞的摩擦或障碍。
  4. 先解决明显的障碍。消除有动力的开发者最可能放弃的前三处节点。
  5. 为每个核心环节设定指标，以便查看用户在何处流失。

What removes friction (and what adds it)

消除摩擦的方法（以及增加摩擦的行为）

Removes it:
  • Free tier or trial, no credit card, no "contact sales" (Czakon: hard barriers send devs straight to a competitor).
  • An idiot-proof install and a copy-pasteable example that works on the first try.
  • A "get started in 5 minutes" path, and a docs quickstart written for the stranger, not the expert.
  • A sandbox or demo populated with data close to their real use case, not 
    foo
    and 
    bar
    (Czakon: realistic sandbox data gets you most of the way).
Adds it:
  • A signup wall, a sales call, or a credit card in front of the first win.
  • Docs written by someone who already understands the product.
  • A first run that shows off your architecture instead of getting the developer to their result.
消除摩擦：
  • 免费层级或试用，无需信用卡，无需“联系销售”（Czakon提出：硬性障碍会让开发者直接转向竞争对手）。
  • 极其简单的安装步骤和可直接复制粘贴的示例，确保首次尝试就能成功。
  • “5分钟快速上手”流程，为陌生人而非专家撰写的文档快速入门指南。
  • 填充贴近用户实际使用场景数据的沙箱或演示，而非使用
    foo
    和
    bar
    这类占位符（Czakon提出：真实的沙箱数据能起到大部分作用）。
增加摩擦：
  • 在首次成功前设置注册墙、销售电话或信用卡验证环节。
  • 由已熟悉产品的人员撰写的文档。
  • 首次使用流程侧重于展示你的架构，而非帮助开发者获得结果。

Decision tree

决策树

Can a motivated new dev reach a real win alone, in one sitting, without talking to you?
├─ NO  → this is your highest-leverage work, above any channel or launch.
│         Run a friction log on the one core path and cut the top 3 barriers.
└─ YES → do they come back the next week?
         ├─ NO  → the first win isn't valuable or sticky enough. Wrong "aha,"
         │         or no reason to return. Re-pick the activation moment.
         └─ YES → now acquisition is worth scaling. Go to `first-50-users`.
有动力的新开发者能否在无需与你沟通的情况下，在一场会话内独立获得真正的成功？
├─ 不能 → 这是你最具影响力的工作，优先级高于任何渠道或发布。
│         针对单一核心流程运行摩擦日志，消除前三处障碍。
└─ 能 → 他们下周会回来吗？
         ├─ 不能 → 首次成功的价值不足或缺乏粘性。选错了“顿悟”时刻，
         │         或者没有返回的理由。重新选定激活时刻。
         └─ 能 → 现在可以扩大用户获取规模。前往`first-50-users`。

Mistakes that look reasonable

看似合理的错误做法

  • Optimizing the homepage or the launch while the first run leaks. Fix activation before acquisition. A great channel into a broken first run just burns the channel.
  • Celebrating signups. Signups are vanity if they never activate. Watch time to first value and week-one activation, not the top of the funnel (see 
    know-if-its-working
    ).
  • Gating the first win behind a wall, a demo, or a credit card. Developers bounce and do not come back.
  • Making your product the hero of the first run. The developer is the hero. The moment is "look what I did," not "look what it does."
  • Writing docs for the expert. The quickstart is for the stranger who has never seen it. Test it on one.
  • Documenting every path. Nail the one common path first. Perfect coverage of a journey nobody takes is wasted work.
  • 在首次使用流程存在流失问题时，仍优化首页或进行发布：先解决激活问题再扩大用户获取。将优质渠道引入有缺陷的首次使用流程只会浪费渠道资源。
  • 为注册量庆祝：如果用户从未激活，注册量只是虚荣指标。关注首次价值达成时间和首周激活率，而非漏斗顶部的数据（详见
    know-if-its-working
    ）。
  • 将首次成功设置在墙、演示或信用卡验证之后：开发者会直接离开且不再返回。
  • 让你的产品成为首次使用流程的主角：开发者才是主角。时刻应该是“看我做到了什么”，而非“看它能做什么”。
  • 为专家撰写文档：快速入门指南是写给从未接触过产品的陌生人的。找一位陌生人测试一下。
  • 记录所有路径：先搞定那条常见路径。完美覆盖无人使用的流程只是白费功夫。

Your next 30 minutes

接下来的30分钟你可以做这些

  • Name the ONE core path a new developer takes to their first real win. Just one.
  • Walk it as a stranger (incognito or a clean machine), and time it. Log every question, frustration, and barrier at each step.
  • Circle the first three points where a motivated dev would give up. That is your backlog, ahead of any marketing task.
  • Define the single "I'm awesome" moment, and make it reachable in minutes, in one sitting, with no human help.
  • Put one number on it: time to first value, or the percent of signups that reach the win in week one. Watch it like you watch uptime.
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.
  • 确定新开发者获得首次真正成功的唯一核心流程。就选一个。
  • 以陌生人的身份走一遍流程（隐身模式或干净的机器），计时。记录每一步的所有疑问、挫败感和障碍。
  • 圈出有动力的开发者最可能放弃的前三处节点。这就是你的待办事项，优先级高于任何营销任务。
  • 定义那个单一的“我太棒了”时刻，并确保它能在几分钟内、一场会话内、无需人工帮助的情况下达成。
  • 为它设定一个指标：首次价值达成时间，或首周内获得成功的注册用户百分比。像监控系统正常运行时间一样监控它。
基于真实的开发者工具GTM经验构建，融合了Adam Frankl（《面向开发者的创业公司》）和Jakub Czakon（markepear.dev）的框架。 当框架无法做决策时，就需要人工介入：The DevTool GTM Company。