Skip to main content

Costs of Launching a New Brand

Reading Al Ries and Laura Ries' War in the Boardroom, I took particular note of the following excerpt (page 36):
[A] left brainer at a smaller company thinks, "We can't afford the costs of launching a new brand. So let's use our existing name. Furthermore, we already have some good consumer recognition. With a new brand, we'd have to start all over again. We don't have the resources to launch a new product and a new brand at the same time, nor is it necessary to launch a new brand."
The authors ridicule this line of reasoning, which is unfortunately common even among marketing professionals. The authors counter that successful product strategists:
  1. Strive to create a new product category.
  2. Create a new brand to stand for that category in the mind of the customer.
  3. Keep the brand focused on that one category.
In the short run, creating a new brand may be more expensive. But in the long run, trying to "stretch" a brand name to stand for more than one category is even more expensive.

Comments

Create a new brand to stand for that category in the mind of the customer.

This rule is huge for me. Make your brand synonymous with the market "category" you are trying to corner. Google, Facebook, most of these companies were not the first but they succeeded(in a lot of things actually) but one was becoming synonymous with their category. Search = Google, Social networking = Facebook, online music = iTunes. This is marketing gold.
Sarah Wallace said…
What about the decision on how to move into a new industry? Should a company use their brand which is almost unknown to the new industry or use the brand of a recent acquisition that has a previous reputation (good or bad) in the industry already?
Roger L. Cauvin said…
Thanks for the comment, Sarah.

A brand is a set of associations imprinted in the minds of existing and potential customers. A brand can be an extraordinarily powerful force for selling your products.

The lesson from Al Ries and Laura Ries is that a brand's potential is limited mostly by prior perceptions and biases, not by a company's marketing budget. As a general rule, when introducing new products, companies should choose brand names and images free of historical baggage.

Most companies choose the opposite path. Instead of trying to avoid a brand name with prior associations and biases, they try to leverage whatever positive ones may exist, thinking it will save customers mental effort and the company money. Al Ries, Laura Ries, and other top marketing experts who think outside the box believe this philosophy is a dangerous oversimplification.

Popular posts from this blog

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

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

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