SC Johnson and Brand Extension

In February, I wrote about how to maintain focus and avoid brand extension by creating a new brand name. Now Laura Ries examines SC Johnson and its line of shaving care products.

SC Johnson's highly successful male-oriented brand of shave gels is Edge. Ries praises SC Johnson for opting for a separate brand, Skintimate, when it introduced a line of shave gels for women.

I am not sure whether introducing a separate brand was all that important in this case. What did "Edge" mean in the mind of the consumer? Would introducing "Edge for Women" have undermined the existing Edge brand? Sometimes line extension dilutes the brand, and we need to be cognizant of this fact. Even more undesirable, however, is undermining the original brand. I'm not sure if "Edge for Women" would have undermined the original meaning of "Edge" in the consumer's mind.

Ries writes that "Edge" originally meant "gel" in the consumer's mind. While the idea of a shave gel for women doesn't undermine this meaning, trying to extend the Edge brand into shaving cream does. So she recommends that SC Johnson, if it really wants to diverge from the gel category, should attempt to create a new brand name and a new category instead of extending the Edge brand. Seems like sound advice to me.

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

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

Cauvin

Search This Blog