Case Study in Brand Extension

Laura Ries writes about an interesting case of brand extension:

My last post praised Geox, the first breathable shoe. Mario Moretti Polegato, CEO and founder of Geox, has built a powerful global shoe brand by focusing on one word “breathable.”

But then Ries follows up:

Mario’s itch has led him to start a Geox fashion line featuring clothes that breathe.

But he is staying focused you might be thinking. The product is still breathable. Yes, but there is a great difference between shoes and clothes. It is a great divide that Geox will have great difficulty crossing.

Now, I do think that extending the Geox brand to clothes instead of just shoes has its risks and liabilities. But just how serious these risks and liabilities are depends on whether "Geox" means "breathable shoe" or just "breathable".

If it means "breathable shoe", then extending the brand to clothes is actually a form of rebranding. It's not just a matter of applying the meaning of "Geox" to another line of products. It actually changes the meaning from "breathable shoe" to something broader. Changing what a brand stands for is a dangerous move.

If "Geox" already means "breathable" instead of the narrower "breathable shoe", on the other hand, then applying the brand to clothes is a natural extension that does not change the meaning of "Geox". Ries seems to believe it is an unwise decision, but I'm not sure.

Comments

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Cauvin

Search This Blog