Skip to main content

iPhone Predictions: A Post-Mortem

Now that we have had more than a year to assess the success of Apple's iPhone, let's see how the predictions of the marketing gurus panned out.

Laura Ries predicted that Apple would initially sell a lot of iPhones, but that ultimately the product would flop. I think it's safe to say that the iPhone has not flopped. Apple sold four million of them in a recent six month period. Ries has recently revisited her prediction.

Seth Godin predicted that the iPhone would be successful, and that Apple would sell more than two million of them in 2007. I suspect he was right about the 2007 sales.

From a marketing perspective, the most important observation about the iPhone is that it has not turned out to be so much of a convergence device. While much of Apple's initial marketing touted the iPhone's merging of music, Internet, and phone capabilities, that perception in the mind of the consumer has not taken hold. In fact, 51% of iPhone purchasers say they will use an iPod in addition to an iPhone.

If you look at the comments by Brandon and Thomas on a previous entry on iPhone predictions, you'll see that they pretty much hit the nail on the head.


Paul Young said…
Ries seems very focused on the hardware features and convergence/divergence of the iPhone; and misses the mark completely. What makes the iPhone work is the _software_, which enables an incredible platform for apps with all sorts of potential. FWIW I love browsing the web on my iPhone, even non dot mobi sites.

Paul (from my iPhone)
Roger L. Cauvin said…
Paul, to be fair to Laura Ries, she is concentrating on the marketing and branding aspects of the iPhone. In that respect, she is right to address the convergence issue.

Nevertheless, the issue from the beginning was whether the iPhone is a convergence device or creates a new product category. It's a mistake to equate convergence of technology with convergence of product categories. While Ries will be the first to tell you that what matters is the perception in the mind of the prospective and existing customer, it appears she conflated the two types of convergence in this case.

It seems the iPhone has been a success and has created a new category in the mind. What does "iPhone" mean in the mind of the customer? I'm not sure, but perhaps it means "stylish smartphone".
Mike Lunt said…
It seems like there is a much more fundamental misconception at play here. In my mind, the technology has not yet been converged between the iPhone and the iPod.

Sure, they can both play music, but once Apple came out with 80 and 160 GB iPods, many people, such as myself, could never downgrade to 4, 8, or 16 GB.

There is technology overlap but not a full convergence in this case, which makes it difficult to say whether the marketing attempts at convergence can/will succeed.
Roger L. Cauvin said…
Mike, your observation that the iPhone would be a downgraded for existing iPod owners is important. Far from being a "misconception", however, it actually strengthens the case for those who criticize convergence.

When you merge two different functions into one product, you typically end up with a product that is inferior at both functions.

Al and Laura Ries once wrote:

"Why are divergence products generally winners and convergence products generally losers? One reason is that convergence products are always a compromise."

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