benefit-ladder
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBenefit Ladder
价值阶梯
When to use
适用场景
- Translating engineering / product language into customer-facing comms
- Writing positioning statements for a feature or product
- Building messaging architecture for a campaign
- Reviewing existing copy that feels either too technical or too generic-emotional
- 将技术/产品语言转化为面向客户的沟通内容
- 为功能或产品撰写定位声明
- 为营销活动搭建话术架构
- 审核过于技术化或过于泛情感化的现有文案
When NOT to use
不适用场景
- Pure technical docs where features ARE the value (B2B internal documentation)
- Brand-level work without a specific product or feature in scope
- Simple commodities where there's no meaningful product truth to climb from
- 纯技术文档（功能本身即为价值，如B2B内部文档）
- 未涉及特定产品或功能的品牌层面工作
- 无实质性产品本质可挖掘的简单商品
Core procedure
核心流程
For a given product, feature, or claim, fill in four rungs from bottom to top:
针对特定产品、功能或主张，自下而上填写四个层级：
Rung 1: Feature / Attribute
第一层：功能特性/属性
The raw specification. What the thing literally has or does at the implementation level.
Example: "10ms latency on async writes."
原始技术规格，即产品在实现层面具备的特性或执行的操作。
示例：“异步写入延迟低至10毫秒。”
Rung 2: Product Truth
第二层：产品本质
The proof point that makes the feature different — the ingredient, technology, or design choice that justifies the claim. Without this rung, emotional claims have no credibility chain.
Example: "Custom write-ahead log built on memory-mapped files."
让该功能与众不同的支撑点——即证明该主张合理的成分、技术或设计选择。缺少这一层，情感诉求将失去可信度链条。
示例：“基于内存映射文件构建的自定义预写日志。”
Rung 3: Functional Benefit
第三层：实用价值
The practical payoff. What the user actually gets done because of the feature.
Example: "Your dashboards stay live even during peak traffic."
用户能获得的实际收益，即借助该功能用户可以完成的具体事项。
示例：“即使在流量峰值期间，你的仪表盘也能保持正常运行。”
Rung 4: Emotional Benefit
第四层：情感价值
The felt payoff. The identity, status, confidence, or belonging that comes from the functional benefit. This is where brand meaning lives.
Example: "You stop being the person who has to apologize when the dashboard breaks."
用户获得的心理收益，即源于实用价值的身份认同、地位、自信或归属感。这是品牌意义的所在。
示例：“你再也不用因为仪表盘故障而道歉了。”
Output format
输出格式
FEATURE: [raw spec]
PRODUCT TRUTH: [proof point — the why-you-can-claim-this]
FUNCTIONAL: [practical payoff — what the user gets done]
EMOTIONAL: [felt payoff — identity, status, confidence]FEATURE: [raw spec]
PRODUCT TRUTH: [proof point — the why-you-can-claim-this]
FUNCTIONAL: [practical payoff — what the user gets done]
EMOTIONAL: [felt payoff — identity, status, confidence]Use guidance
使用指南
Climb only as high as the audience will follow. B2B technical buyers may live on rungs 1-3. Consumers usually live on rung 4. Don't skip rungs — that's where credibility breaks.
Multi-segment work: write three separate ladders for three target segments, then pick which emotional rung the campaign should sit on. Different segments often need different rungs in the same campaign.
Direction: always start from the bottom (Feature) and climb up. Top-down (starting from emotional intent) tends to produce claims with no proof point.
仅攀登到目标受众能接受的层级。 B2B技术买家通常关注第1-3层，消费者则更关注第4层。不要跳过任何层级——否则会破坏可信度。
多受众场景： 为三个目标受众分别撰写价值阶梯，再确定营销活动应聚焦的情感层级。同一活动中，不同受众往往需要不同的层级。
方向： 始终从底层（功能特性）开始向上攀登。自上而下（从情感意图出发）往往会产生无支撑依据的主张。
Failure modes
常见误区
- Skipping product truth. Going Feature → Functional → Emotional without the proof point makes the emotional claim feel unearned.
- Generic emotional rung. "Happier" or "more successful" don't pass — they could apply to anything. Force the emotional benefit to be specific to this audience and this functional benefit.
- Over-climbing. B2B audiences resist emotional language they perceive as marketing-speak. Stay on rung 3 if rung 4 reads as overreach.
- Confusing functional and emotional. "Saves time" is functional. "Frees you from feeling like you're always behind" is emotional. The test: does it describe the result or describe how the result feels?
- 跳过产品本质层： 直接从功能特性→实用价值→情感价值，缺少支撑点会让情感诉求显得毫无根据。
- 泛化的情感层级： “更快乐”或“更成功”这类表述并不合格——它们适用于任何产品。必须让情感价值针对该受众和该实用价值具体化。
- 过度攀登： B2B受众反感被视为营销套话的情感语言。如果第4层显得过于夸张，就停留在第3层。
- 混淆实用价值与情感价值： “节省时间”是实用价值，“让你摆脱总是落后的焦虑感”是情感价值。判断标准：它描述的是结果本身，还是结果带来的感受？