benefit-ladder

Original：🇺🇸 English

Translated

When translating product details into messaging, climb a 4-rung ladder from Feature → Product Truth → Functional Benefit → Emotional Benefit. Forces every emotional claim to have a credibility chain back to a verifiable feature, beating messaging that's either too technical (specs without meaning) or too floaty (emotion without proof).

4installs

Sourcemyosin-xyz/hivemind-skills

Added on2026-05-03

NPX Install

npx skill4agent add myosin-xyz/hivemind-skills benefit-ladder

SKILL.md Content

View Translation Comparison →

Benefit 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

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."

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]

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.

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?