Skip to main content

Categories: Naming

If you manage to create a new category and be the first in it, you have a chance to name the category. You can introduce the category name in your marketing literature and PR campaigns.

The guidelines for choosing a category name differ from the guidelines for choosing a brand name. While descriptive brand names are a bad idea, a category name is by nature descriptive.

"Xerox" was a powerful brand name that dominated the "copier" category. The brand name was a blank slate, not descriptive of anything [at least to the average person; see the comments], especially of the product. The category name, on the other hand, was a straightforward description of the product's function.

The main guideline in choosing a category name is to ensure it clearly conveys that the product(s) in it differ significantly from products in existing categories. Such a category name aids in the marketing of your product, as it makes it easier to position it versus the competition.

Comments

Anonymous said…
Xerox is a descriptive name, The Haloid Company was renamed to Haloid Xerox cause their first copier did use xerography.

And sorry, I dont agree with the nill brand names. This might be needed nowadasys to get trademarks, but it was never needed in earlier days.

Have a coke, have a pepsi?
Bernd
Roger L. Cauvin said…
Thanks for the info about Xerox, Bernd. From the point of view of the average consumer, however, "Xerox" didn't mean anything. It was a blank slate to most consumers.

The reknowned marketing guru Al Ries, his daughter Laura Ries, and the well-respected Seth Godin all agree: overly-descriptive or generic brand names are a bad idea. Scientific studies support their position.

If you have any studies or evidence to the contrary, please do share.

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

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