Benefit not feature
The chain from what a product does to why someone cares
Feature: what the product has. Benefit: what changes for the user. Outcome: the user's life after the change.
For every feature, ask:
- What can the user do now? The benefit.
- What changes in their day? The outcome.
The translation table
| Feature | Benefit | Outcome |
|---|---|---|
| Real-time database sync | Users always see current data | No more "why is this wrong?" support tickets |
| Role-based access controls | Each team member gets exactly the access they need | Audits pass on the first try |
| Offline-first architecture | Works when the internet doesn't | Field teams stop losing work mid-session |
| Automated changelog generation | Ship without writing release notes | 30 minutes back every release cycle |
Catch the feature-leading phrases
"Featuring," "With built-in," and "Now with" are structural tells. Turn "Now with X" into "Now you can Y."
The disguised feature
"Easy onboarding" is still a product property. The reader asks: "what does my first hour look like?"
Test: does the sentence describe a product property or a change in the user's day?
Outcomes that are too generic
"You'll be more productive" could mean anything. "Ship Friday without anxiety" puts the reader in a scene. "Cut report time from 2 hours to 20 minutes" is proof.
Specific outcomes contain a number, a time, or a scenario.
When features can lead
In reference docs and comparison tables, features belong. "Supports SAML SSO. Exports to CSV." The reader is already shopping.
For technical audiences, "WebSocket connections" needs no rewrite. The rule hits hardest on hero copy and landing pages.