Skip to main content

Laura Ries on Brand Mortality

Laura Ries' latest blog entry squarely addresses the issue of what to do about brands and product categories that are dying. The thrust of her advice is to avoid the natural inclination to try to preserve a dying brand by modifying it.

A strong brand stands for something in the mind of the consumer. Years of consistent, focused marketing and a remarkable product or company are the typical recipe for a strong brand. But sometimes the entire product category becomes obsolete, and the once-strong brand dies with it.

The natural inclination is to try to preserve the brand symbols (name, logo, etc.) since so much time, effort, and money went into making them powerful and well known. So why not transition into new or evolved products and attach the same brand to them?

Changing your brand is like trying to change the meaning of a word. If a word is relatively new and not well known, then it's not much of an uphill battle to assign a new meaning to it. But good luck trying to change what an old word with an established definition means to people. You're much better off inventing a new word.

Ries gives numerous examples of ill-conceived attempts to preserve or modify brands.

When your brand is dying, resist the temptation to modify it. Spin off a completely new brand (and not an extension of your current brand). It will take time and money to build it, but at least your new brand won't be doomed to failure.

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

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing

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 hardw