Skip to main content

When the Market Changes, Should Your Brand Also Change?

Trends in the marketplace affect the appeal of your message and the profitability of your product. When the trends run counter to your marketing message, should you re-position your product?

Laura Ries says, "No." She discusses the Hellman's brand. Hellman's mayonnaise is full fat, so
What do you do when the world seems obsessed with dieting, fat and calories? When every product is promoting it is low-fat, fat-free, low-carb, high fiber or zero calorie? When everybody is on a diet, gobbling up calorie reduced manufacture foods yet still hungry, miserable and (at least in the U.S.) fat?
Most company executives and product managers would either modify the marketing message or come out with a "light" version of the product under the same brand.

What does Laura suggest?
Whatever your brand is, you have to deal with it. Pretending it isn't high fat isn't going to change what’s in the package. And promoting your “light” version just reinforces in the mind of consumers how “fattening” the regular version must be.

Like food, a brand is best when it is real, simple and focused. If opportunity strikes in another direction, companies should launch a new brand.
In other words, maintain brand focus.

Comments

Unknown said…
I have to agree with Laura. You are what you are--embrace it. Brands are destroyed when the marketing people continually chase new messages. Those who follow trends never catch up because the trends always change.

McDonald’s doesn’t claim to be food that’s good for you; they offer a clean restaurant with food that tastes the same everywhere. I wish McDonald's would bring back the old oil for fries with a message, "If it tastes good, it's gotta be bad. Our fries will stop your heart so don't you want to be eating something that tastes great when it happens?"

Apple has said, "we're expensive and we're worth it." How many vendor products have ads that talk about quality but a sales force that undercuts that quality message with discounts.

Look at Rod Stewart. Rod was once a real rocker but then he followed every trend that came along and now he's a crooner. What is his "brand"? He has none. He won't be remembered after he's gone.

You are what you are--embrace it. Never hide from your strength.

Steve Johnson
Pragmatic Marketing
more at productmarketing.com

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the