Skip to main content

Laura Ries' iPhone Prediction

Laura Ries is now on the record. She predicts that the iPhone will eventually flop after an initial surge:

I don't disagree with the prediction that initially Apple will sell quite a few iPhones. Steve Job's brilliant job with the PR and the media's love of convergence will make an iPhone a must have for some early adopters and elites.

But shortly after the launch the initial hype will wear off and Steve will move on to the next project at Apple. Then the iPhone will end up in the convergence scrap heap along with the ROKR, N-Gage, WebTv and many others.

Initially convergence products, like line extensions get attention and generate early sales. But long term they usually fail and always undermine the brand.
I've set an appointment on my calendar for July 2008 to assess Ries' prediction. Anyone want to go on record with a contrary prediction?

Comments

Brandon said…
I think the iPhone will succeed. It will succeed because it's a really good communication device. I don't think of it as a convergence device. The iPod has a bunch of stuff for contacts and games but it's not the focus of the product. Sure the iPhone will play music but at I predict it's a great phone. Frankly, the UI's on phone just plain suck. Bringing a better UI alone is going to be revolutionary.
rcauvin said…
Good to see you sticking your neck out and making a prediction. I see merit in both Ries' arguments and yours, so I'm not comfortable making a prediction at this point.
Unknown said…
Al & Laura are two of my favorite guiding lights in terms of messaging. Their books line my bookcase. While I completely agree with their general theme of 'convergence only works in clock radios', i think the iPhone is not a convergent device... it is a divergent device that is in a new category completely.

Rather than looking at it as a phone with features and a better interface look at it as a computer that has diverged. Previous devices like Palm were divergent of calculators & organisers (more features like adding a phone). Windows mobile devices were divergent of mobile phones (more features like adding an organiser). The iPhone is divergent from a computer (less features catered for on the go).

Looking at it from that point of view I think it will be a raging success. For now, I believe it is a smart move to keep iPods and iPhones as two separate products that may have overlapping features.

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

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the