Back to Details

positioning-and-story

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Positioning & story

定位与叙事

Your story is boring without a villain. And you are not the hero of it. The developer is. You're the wise advisor who hands them a better weapon.
Use this when: your homepage explains what your product does before it names the problem, your positioning is interchangeable with three competitors, or nobody feels any urgency to act now.
没有反派的叙事毫无吸引力。而你并非故事的主角，开发者才是。你是那位为他们提供更趁手武器的智者顾问。
**适用场景：**你的官网在点明问题前就先介绍产品功能、你的定位与三家竞品毫无区别，或是没人有立即行动的紧迫感。

The core idea

核心思想

Developers don't buy features; they hire a tool to defeat something that's making their life worse. Get the roles right:
  • Hero = the developer (never the vendor, never the product)
  • Villain = the undeniable trend making the pain worse every day
  • Wise Advisor = you, arriving with a gift (the product)
  • Inciting event = the change in the world that forces the hero to act now
No villain → no urgency → no story → no conversion.
开发者不会为功能买单；他们是为了解决困扰自己的问题而选择工具。要明确角色定位：
  • 主角 = 开发者（绝非厂商或产品）
  • 反派 = 真实存在的、让痛点日益加剧的行业趋势
  • 智者顾问 = 你，带着解决方案（产品）而来
  • 触发事件 = 行业变化迫使主角必须立即行动
没有反派 → 没有紧迫感 → 没有叙事 → 没有转化。

Framework: the 3-part story (Frankl)

框架：三段式叙事（Frankl 提出）

  1. Inciting event: introduce the hero and the villain; the world changed and the hero can't stay put.
  2. Obstacles: a series of specific challenges, each solved with your help, best told as mini before/afters: "Before X, we had [problem]. Now [measured result]."
  3. Resolution: villain defeated (for now), specific results, hero shares the wisdom → that's your testimonial.
The benchmark (EngFlow):
"Slow builds waste your time. Standard build tools can't handle today's codebases. Speed up builds now to keep engineers in flow."
  • Pain: slow builds waste your time
  • Villain: standard tools can't handle modern complexity
  • Hero: engineers, kept in flow
  • Wise Advisor: the build experts
Good villains: cloud-cost sprawl · tool fragmentation · compounding tech debt · flaky pipelines · observability gaps · manual deploys · YAML sprawl · agents you can't trust in prod.
  1. 触发事件：介绍主角与反派；行业发生变化，主角无法再安于现状。
  2. 阻碍挑战：一系列具体难题，每个难题都在你的帮助下得以解决，最好用“前后对比”的小故事呈现：“在使用X之前，我们面临[问题]。现在[可衡量的成果]。”
  3. 解决方案：反派被击败（暂时），取得具体成果，主角分享经验 → 这就是你的客户证言。
参考案例（EngFlow）：
“缓慢的构建过程浪费你的时间。标准构建工具无法应对如今的代码库。立即加速构建，让工程师保持高效流畅的工作状态。”
  • 痛点：构建缓慢浪费时间
  • 反派：标准工具无法应对现代代码复杂度
  • 主角：保持高效工作的工程师
  • 智者顾问：构建领域专家
**优质反派示例：**云成本失控 · 工具碎片化 · 不断累积的技术债务 · 不稳定的流水线 · 可观测性缺口 · 手动部署 · YAML文件泛滥 · 生产环境中不可信的Agent。

Framework: the 4 levels of differentiation (Frankl)

框架：四级差异化定位（Frankl 提出）

Compete as high up this ladder as you can. Feature wars are a race to the bottom.
LevelTypeSounds likeGrade
1Feature"we have X, they don't"D
2Benefit"we save you time"C
3Customer segment"for CTOs under release pressure with compliance"B
4Problem"the only fix for [problem no one else has named]"A
Reaching Level 4 / category creation: talk to enough TAB members (see 
talk-to-users
) to surface a problem competitors haven't named, then name it so precisely your product is the obvious answer. When rivals adopt your vocabulary, they've already lost the position. (JFrog: "artifact repository" → "Universal Artifact Repository" and leapfrogged Sonatype.)
尽可能在更高层级展开竞争。功能战只会让你陷入恶性循环。
层级类型话术示例评级
1功能层面"我们有X功能，竞品没有"D
2利益层面"我们帮你节省时间"C
3客户细分"面向面临发布压力且需合规的CTO"B
4问题层面"唯一能解决[竞品尚未提及的问题]的方案"A
**达到第4级/创建新赛道：**与足够多的TAB成员交流（参考
talk-to-users
方法），挖掘出竞品尚未提及的问题，然后精准定义该问题，让你的产品成为显而易见的解决方案。当竞争对手开始使用你的话术时，他们已经失去了领先地位。（JFrog：从“制品仓库”→“通用制品仓库”，一举超越Sonatype。）

Decision tree

决策树

Can you state a problem only you solve, in the user's words?
├─ YES → Level 4. Lead with the problem; name the category.
└─ NO  → Can you name a specific segment with a compelling reason?
         ├─ YES → Level 3. Lead with the ICP + their trigger.
         └─ NO  → you're stuck at feature/benefit → go run `talk-to-users`.
你能否用用户的语言表述一个只有你能解决的问题？
├─ 是 → 第4级。以问题为切入点；定义新赛道。
└─ 否  → 你能否明确一个具有强吸引力的特定细分群体？
         ├─ 是 → 第3级。以理想客户画像（ICP）及其触发因素为切入点。
         └─ 否  → 你停留在功能/利益层面 → 去执行`talk-to-users`。

Mistakes that look reasonable

看似合理的误区

  • Product as hero: "ShipFast helps you…" Make the developer the subject of the sentence.
  • No villain: all solution, no antagonist → zero urgency.
  • "Platform": developers hear months of integration and risk. Name the specific thing it does.
  • "Pleased to announce": nobody cares about your emotional state; a feature is not a story, a customer win is.
  • Feature-matrix positioning: a checklist vs competitors keeps you at Level 1 forever.
  • 以产品为主角："ShipFast 帮你……" 要让开发者成为句子的主语。
  • 没有反派：只讲解决方案，没有对立因素 → 完全没有紧迫感。
  • 滥用“平台”一词：开发者听到这个词会联想到“数月的集成工作与风险”。要明确说明产品的具体功能。
  • “荣幸宣布”：没人在乎你的情绪；功能不是叙事，客户成功案例才是。
  • 功能矩阵定位：与竞品列功能清单对比会让你永远停留在第1级。

Your next 30 minutes

接下来30分钟可完成的任务

  • Write one sentence: hero + villain + inciting event (steal the EngFlow shape).
  • Grade your current differentiation 1-4. If it's D/C, list what would move it to B/A.
  • Find the villain in your 
    talk-to-users
    "environmental changes" bucket, it's already there.
  • Rewrite your headline so the developer is the subject and the problem comes before the product.
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.
  • 写一句话：主角 + 反派 + 触发事件（参考EngFlow的句式）。
  • 为你当前的差异化定位评级（1-4级）。如果是D/C级，列出升级到B/A级所需的行动。
  • 在你的
    talk-to-users
    “行业变化”分类中找到反派，它早已存在。
  • 重写你的标题，让开发者成为主语，问题先于产品出现。
基于开发者工具GTM（上市推广）的真实经验构建，框架源自Adam Frankl（《面向开发者的创业公司》）与Jakub Czakon（markepear.dev）。 当框架无法做出决策时，就需要专业人士的支持：开发者工具GTM公司。