Template
Translate a feature into user impact
A feature list describes the thing. A decision usually depends on what the feature changes for this reader. Trace the line from capability to consequence without inventing benefits the evidence does not support.
Before you use it
- Use when
- You need to explain why a product, design choice or proposal matters to a particular audience.
Keep this limit in mind
- Do not turn a possible advantage into a promised outcome. Different users can value the same feature differently.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Capability: ___. What it changes in use: ___. Who benefits and in what situation: ___. Evidence or assumption behind that benefit: ___.
A question to ask
Is the “benefit” observed, supported, or only plausible?
Why it matters
A feature list describes the thing. A decision usually depends on what the feature changes for this reader. Trace the line from capability to consequence without inventing benefits the evidence does not support.
Check your result
The audience can see the connection between the capability and a bounded practical consequence.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTranslate a feature into user impact
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaEdit for attention and action
Evidence and sources
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
Use the FAB Technique (features, Advantages, Benefits) to Explain the Value of a Product, · data/life-os-content/fab-statement-generator.json
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12