# Translate a feature into user impact

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Translate a feature into user impact

ID: MHC-D-BRALI-0093 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/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.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- You need to explain why a product, design choice or proposal matters to a particular audience.

### Avoid when

- Do not turn a possible advantage into a promised outcome. Different users can value the same feature differently.

### Explanation

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.

### Template

Capability: ___.
What it changes in use: ___.
Who benefits and in what situation: ___.
Evidence or assumption behind that benefit: ___.

### Question

Is the “benefit” observed, supported, or only plausible?

### Check

The audience can see the connection between the capability and a bounded practical consequence.

### Limits

- Do not turn a possible advantage into a promised outcome. Different users can value the same feature differently.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-8c6c6676229d9341d39e. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/fab-statement-generator.json)
- FP-BRALI-SRC-8c6c6676229d9341d39e: Use the FAB Technique (features, Advantages, Benefits) to Explain the Value of a Product, — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/fab-statement-generator.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (use_before): https://vedokrok.com/knowledge/structure-a-proposal-from-problem-to-next-step
