Pragmatic Marketing Rule #17

This is the seventeenth in a series of posts on the Practical Product Management rules from Pragmatic Marketing.

Pragmatic Marketing Rule #17: You need a positioning document for each type of buyer.

In the beginning of technology marketing, when it came to communicating about our products, we mostly spoke techinese. We emphasized the features, and sometimes forgot all about the benefits.

Then someone uttered those famous last words, “People don’t buy features, they buy benefits.”

And it was off to the races with benefits statements.

Unfortunately, all benefits statements started to sound alike: Use our product to save time and money, increase productivity, and grow your revenues.

You could read these benefits statements and come away with no idea whatsoever whether someone was trying to sell you a mainframe or a spreadsheet.

This all came about, I’m afraid, because as marketers we often failed to think through exactly who our buyers were in terms of all of the constituencies who might be involved in a purchase decision.

We jumped right from thinking only about the techies, and their need to know the gritty product details, to thinking only about the vaunted “C-level” decision makers who wanted to know what the payback was. (Don’t bother me with the details…)

A positioning document for each type of buyer is an excellent remedy for the problem.

With separate positioning work, you’ll have the essential messages you need to communicate your products, and its values to all of your audiences.

Having these positioning documents on hand can save you a boatload of effort when you’re creating sales tools, collateral, and program material. You’ll know what to say, and you’ll make sure you’re saying the right thing to the right people.

But, as I implore marketing folks everywhere, please, please, please make sure that no one goes away without knowing what the your product actually is and does. (As my friend, and marketer par excellence, Valerie always says when she’s just read something that’s less than clear, “But what do it do?”)


Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader. If you don't have a feed reader, you can always have these articles delivered to your email inbox every day. Click here to sign up.

No comments yet.

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

(required)

(required)