Skip to main content

The Big Brands Do It, Why Can't We?

Good marketing often contradicts intuitions and instincts. Those wishing to cling to their intuitions find solace in the fact that big companies are just as likely to make mistakes as little ones.

Kimberly-Clark, a huge company and umbrella brand, chose "Huggies" as the name of a line of diapers. "Huggies" is a descriptive name in that it implies in a not-so-subtle way that it is comfortable and effective. (Similarly, Procter and Gamble sells the "Pampers" line of diapers.) Yet descriptive names generally don't make good brand names.

I can hear it now: "If Kimberly-Clark's marketing department decided on a descriptive name, why shouldn't we?"

I should point out that, aside from its descriptiveness, "Huggies" is actually a pretty good name. It is easy to pronounce, easy to spell, and slightly shocking - all attributes that foster brand recall and recognition. Plenty of products succeed despite a descriptive name.

But let's put to rest the idea that big, successful companies don't make marketing mistakes. Fortunately, Laura Ries debunks this notion on a regular basis. In her latest blog entry, she tears into seven successful companies for recent marketing decisions they've made.

Comments

Observator said…
interesting read. so do you happen to work with GSD&M?
Roger L. Cauvin said…
No, I haven't done any work with GSD&M (now "GSD&M's Idea City").

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

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