Feature, Advantage, Benefit: how to describe something so people want it

By Rita Okonkwo · The Craft

When people describe something they care about, a product, a tool, their own proposal, they describe what it is. What it does, how it works, what is in it. All true, and all about the thing. The listener is left to translate every feature into a reason to care, and most will not bother.

Feature, Advantage, Benefit does the translation for them. What it is, why that is better than the alternative, and what the listener gains. It moves the description, one step at a time, from the thing to the person.

Feature, Advantage, Benefit, one part at a time

Question: Sell us on the document tool you would choose for the team.

  • Feature (What it is): It keeps every version of a document automatically, every time anyone saves.
  • Advantage (Why it beats the rest): Unlike emailing attachments, nobody ever has to ask which file is the latest, and nothing is lost when two people edit at once.
  • Benefit (What the listener gains): Which means you stop spending Friday afternoons merging changes, and you can undo anyone's mistake, including your own, in one click.

The three parts

1. Feature: what it is

The fact about the thing: what it is or what it does. One feature, not a list. Choose the feature that leads to the benefit your listener cares about most, not the one you find most impressive.

2. Advantage: why it beats the rest

Compare it with what the listener would otherwise use, even if that is "doing nothing". An Advantage only means something relative to an alternative: "keeps every version" becomes interesting once you remember the email thread with five attachments called final.

The trap is a comparison nobody was making. Compare with what your listener actually does today.

3. Benefit: what the listener gains

What changes in the listener's life, in their terms: time, money, stress, risk, a better Friday. Speak to them directly ("you stop...") and make it concrete enough to picture. This is the part that sells; the other two are there to make it believable.

The "which means" test

The quickest way to find a Benefit is to say the Feature and then add "which means...", and keep adding it until you reach something the listener would actually want. "It keeps every version, which means nobody loses work, which means you stop spending Friday afternoons merging changes." Stop when you reach the person. If you run out of "which means" before you get there, you have picked the wrong feature for this listener.

An answer, taken apart

Feature. It keeps every version of a document automatically, every time anyone saves.

Advantage. Unlike emailing attachments, nobody ever has to ask which file is the latest, and nothing is lost when two people edit at once.

Benefit. Which means you stop spending Friday afternoons merging changes, and you can undo anyone's mistake, including your own, in one click.

Three sentences, and the last one is entirely about the listener. That is the direction the whole answer travels.

One feature, two listeners

The same feature can lead to different benefits, and choosing between them is most of the skill. Say you are recommending a new booking system for a small physiotherapy clinic. The feature is the same either way: patients can book and move their own appointments online.

To the clinic owner:

Advantage. Unlike phone bookings, a cancelled slot shows up for other patients straight away instead of sitting empty.

Benefit. Which means fewer gaps in the diary, and fewer weeks where the numbers depend on who happened to call.

To the receptionist:

Advantage. Unlike now, a patient who wants to move an appointment does not need to ring during opening hours.

Benefit. Which means the phone stops interrupting you every ten minutes, and you can actually finish the morning's paperwork.

Neither version is wrong. Each one is right for one person in the room, which is why it pays to know who you are talking to before you choose the Feature.

Saying it out loud

Written down, the three parts can look mechanical. Spoken, they should not sound like labels. A few habits help.

Let "unlike" and "which means" do the joining. They carry the listener from one part to the next without announcing a structure.

Slow down on the Benefit. It is the sentence you want remembered, so give it a little more room than the other two, and stop after it.

Use their numbers if you have them. If the listener told you they lose two hours a week to something, the Benefit is those two hours, in their words.

Where it works, and where it doesn't

Use it for sales conversations, product demos, recommending a tool or supplier, pitching a feature to your team, and the "why should I use this?" question in any form. It also works on ideas: a policy's feature, its advantage over the current rule, its benefit to the people affected.

It assumes the listener already has the problem. If they do not, start with Problem, Solution, Benefit, which names the pain first.

How the Coach listens for it

The Coach checks a take for a feature, an advantage and a benefit. The usual miss is a take that stays at the feature: a clear description of what something does, with no comparison and nothing about the listener.

A five-minute drill

Pick an object on your desk. Name one feature. Then say "which means" out loud three times in a row, each time going one step closer to a person. Now pick a different listener, a student, a parent, your manager, and do it again from the same feature. If the two chains end in the same place, push the second one further until it does not.

Practise it

Practise Feature, Advantage, Benefit in the Coach. Lock it and try the Sale and Pitch scenarios; then try it on something that is not a product at all.