iPhone Marketing Issues

The introduction of Apple's iPhone brings up a number of marketing issues.

Focus. Apple is marketing the iPhone by stating that it "combines three products". Is it a phone? Is it a digital media player? Or is it a device for accessing the Internet? A lack of focus often leads to product failure.
Naming. Cisco is suing Apple over the name "iPhone". More importantly, the name is generic. Generic names usually make the worst brand names.
Differentiation. Apple tried to "think different" in designing the phone. Did they succeed? The phone includes a "visual voice mail" feature in which you can view a list of your pending voice mails and select which one to hear. I don't know of any other phone with this feature. Most of the other hyped features (including touchscreen dialing) seem to be available in other phones.
Brand extension. Apple changed its name from Apple Computer to Apple, Inc. The iPod is not a personal computer, yet it has been a huge success for the company. The iPhone is another deviation from the notion of Apple as a traditional computer company. For what does "Apple" stand in the mind of the consumer?
Pricing. Apple chose not to compete with other phones on price. Competing on price is typically an indication of incompetence in marketing or a lack of differentiation. A high price, on the other hand, sometimes is perceived as an indication of greater value.

It will be interesting to see how these factors play out.

UPDATE: While no mobile phones have the feature, the concept of visual voice mail is not new.

Comments

Anonymous said…

You wrote:
> Pricing. Apple chose not to compete with other phones on price. Competing on price is typically an indication of incompetence in marketing or a lack of differentiation.

Well said! Not many marketers (and zero sales people) seem to have the nerve to charge more when, as you point out, more expensive products are generally perceived to be better.

Fri Jan 12, 04:41:00 PM 2007

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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the four problems that companies face, or are trying to overcome, as they make product decisions . Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions. They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

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...

Cauvin

Search This Blog