The Trap of “Features & Benefits”

COMPANIES ALL OVER THE GLOBE use a list of “Features & Benefits” to pitch their products. It is a device used by sales people, product managers, and marketers alike. And, too often, it fails to effectively present the product it pitches.

Listing benefits can and should speak to the value that a prospect can receive from a product. But there are two basic problems that can destroy the effectiveness of a Features & Benefits list:

· In the majority of cases, “Benefits” merely serve to justify the “Features.”

· What are listed as benefits are often just further descriptions of the features.

Semantic duels are waged over the words “Features” and “Benefits.” Some people even add the word “Advantages” to the mix. But the problem begins with the title itself.

Hampered from the Start

By leading with the word “Features”, you are announcing that this is about yourself — i.e. the features of your product — not about your prospect’s needs or interests. That registers with your audience every time.

It doesn’t necessarily help to flip the labels around, however. Calling it “Benefits & Features” still puts the emphasis on features, if for no other reason than virtually every listing of benefits and features is done in a two-column table. It always comes down to the features.

“But don’t people want to know about the features?” you might ask. Sure, but within a context — with a reason for being. Meanwhile . . .

› If your prospects already know what the features are, they already know the benefits. For example, if someone is planning to buy a projector, they’ll look to see what the lumens or contrast or resolution is. In most cases, they’ll ignore any listing of benefits, since they know that information already. They just want to see the particulars of the features.

› If your prospects don’t know what specific features are used for, there are better ways to educate them than with the typical list of features and benefits. Give them a context first, so they’ll understand how individual features fit into the overall product performance or application.

Now, business does get done in spite of lists of features and benefits. Business even gets done in the face of really poor communications. If a person’s need is strong enough, they’ll wade through all kinds of materials and bad pitches to try to find the answers or applications they need.

But in a competitive world (which all of us face, or will), do you really want to leave things to chance or to a prospect’s desperation in your efforts to win more business?

Abolishing the Labels


Your prospects don’t think in terms of labels, they think in terms of actions, capabilities, and outcomes. Most don’t walk around saying “I need a Solution.” or “I need these Benefits.” They say “I need to do this.” or “I need to solve that.”

If you talk to your prospects in their terms, you will have more meaningful conversations, make stronger connections, and achieve better results.

This makes for an interesting challenge, of course, when you need to structure and present formal communications about your products: How do you express the value your product provides if you don’t attach it to the features your product possesses?

It’s simple: separate the two.

Product features are merely a means to an end. They’re not unimportant, but they should not be highlighted until a prospect is ready for that level of detail. First, a prospect needs to grasp and identify with the overall value or benefit that the product can provide them.


So in place of one “Features & Benefits” document, you potentially end up with three documents or slides:

1) An overall positioning of the value your product provides, in clear, compelling language.

2) A simple list of product features, to be provided upon request, included as an appendix, or available as a separate link on a web site. This should not have “Benefits” listed, unless it is for internal use as part of a training document.

3) Descriptions of specific applications of the product, when you need to educate prospects about your product. This provides context for individual features and does a better job of educating newbies.

Adapting Your Current “Features & Benefits”

If you need a document that catalogs the capabilities of various features, try labeling it as “Features & Functions” (or “Capabilities” or “Applications”).

Another approach would be to set up a list of “What” and “How” — as in “What you want to do:” and “How to do it:”

In any of these scenarios, don’t mix benefits in with features. Reserve “Benefits” for a higher-level discussion. If prospects understand the overall value of your product, they’ll be much more interested in the specific features and attributes.