Skip to main content

How to Extend Your Brand

In a MarketingProfs.com article, "How Far Will Brand Extensions Stretch?", Ted Mininni argues that you should attempt to extend your brand only after conducting some careful market research.

Money quotes:

"While there can be significant benefits in brand extension strategies, there can also be significant risks, resulting in a diluted or severely damaged brand."

"The most common brand stretches include line extensions within the same category."

"Yet, a large number of brand extensions into new categories have proven to be dismal failures."

"Many marketing managers think that it makes sense to 'transfer' the promise and equity of their established brand. But that isn't always true. Companies sometimes go too far trying to extend into categories that are not a good fit, and they risk losing credibility in their flagship brands."

"If consumer perception, based on research, does not corroborate that the proposed extension is a fit with the brand's values, it will not be a success, no matter how needed or exciting the new product is."

"Once a brand extension is executed, it is still important to identify any changes, positive or negative, in perceived core brand values, using the consumer as the barometer for these measurements."
Extending a brand is not something you should take lightly, and doing it effectively requires market research and strategy expertise. Read the article to get more specifc tips on how to extend your brand - if you dare.

Comments

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

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware