Skip to main content

Contradicting Instincts

Talking to a colleague on the phone about a month ago, I remarked that a significant amount of what a product manager does is recommend strategy that contradicts basic instincts. The basic instincts of marketing seem to include:

  1. Strive to make your product appeal to as broad and diverse market as possible.
  2. Ensure your product has all of the same features as the competition, plus more.
  3. Choose a name, logo, and web domain name that are as descriptive of your company or product as possible.
  4. Try to hide or play down your product's weaknesses.
Yet these instincts are generally the opposite of how you should be managing your product.

Instead of striving to appeal to as broad a market as possible, you often should carefully select a single segment that is sufficiently large and focus on it. Rather than worrying about me-too feature comparisons with competitors' products, you should concentrate on solving your target market's problems. Scientific studies show that names and logos bearing little or no resemblance to your product are more effective than descriptive names. Finally, you should be embracing your product's weaknesses in order to highlight its corresponding strengths.

Comments

clapoint said…
Re: "scientific studies show that names and logs bearing little or no resemblence to your product are more effective...". Wow, you took a HUGE leap of faith in applying this singular article on product naming whose final paragraph states "Kahn says the use of odd names seems to work best in products that rely on the senses, such as food or fashion, and would probably not work in a high-stakes product category such as healthcare or financial services."

Unless you are a product manager in the consumer sector, this really doesn't apply. In the technology sector, choosing a descriptive name (especially one that might position you in the same category as your top 2 competitors) is not a bad approach.
Roger L. Cauvin said…
Hi, thanks for the critique.

It's true that some experts and scientific studies have restricted their conclusions on this matter to consumer products. And perhaps it is a "huge" leap to generalize to the B2B market.

However, it's nowhere near as big a leap as assuming - as you appear to have done - that descriptive names are okay in the technology sector. I have yet to see a single study supporting that conclusion.

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

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

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