Asymco

Asymmetric Intelligence

Theory

  1. Changing places: Microsoft trades HP for Nokia

    Research · 56 comments

    The juxtaposition of HP's strategy of increased independence and Nokia's new strategy of increased dependence can't be more striking.

    HP is probably Microsoft's biggest customer. As the largest licensee of Windows it probably generated more revenue for Microsoft than any other company. The fact that HP invested in a new operating system for its mobile efforts shows a level of discomfort with the lack of strategic leverage.

    Nokia, on the other hand, has been resolutely independent in its software strategy. For over a decade it held out against licensing any OS, especially one from Microsoft. The pantomime theatrics that took place over that decade will make a great case study some day.

    But now we have a complete reversal of roles: The abandonment of platform independence by a mobile giant at precisely the same time as the acquisition of platform resolve by an IT giant.

    It seems almost poetic. And that should be a clue. Whenever you see poetry, you need not look far for some truth.

    These chess moves are taking place in the context of a greater game: the collision and disruption of IT and Telecom. It's not surprising that massive market forces are causing incumbents to react. HP, Microsoft and Nokia are in the throes of fundamental disruption. Even if these moves may not be all in the same direction, they each react in ways that make sense to them.

    It's also very likely that all the moves are for naught. Incumbents rarely win with reactions. Let's not forget that the entrants came with different business models. Apple and Google are not making money in the ways of Nokia and HP (who are channel dependent) or Microsoft (who is license dependent). The reaction must itself be asymmetric. So far it's not clear where the asymmetry lies.

    Read more:

    HP/Palm’s Rubinstein believes in integration

    WebOS: HP, and HP Only. QNX: RIM and RIM Only

    HP’s PC group spends 0.7% of sales on R&D

    The reason Robbie Bach was fired

  2. The (iPod)Touch(i)Pad

    Research · 99 comments

    The world's largest PC company just launched a "media tablet[1]". Conflating the iPod Touch and iPad brands into "TouchPad" HP joins RIM in announcing an integrated OS/device product to compete as a platform vs. iOS and Android (and to some degree even against Windows).

    There are others waiting in the wings. Presumably, Microsoft is hard at work to release a tablet-compatible Windows sometime near the middle of this decade. MeeGo is also going through its gestation period targeting Atom-based tablets. John Gruber notes the excitement around tablet platforms in his article about this post-PC renaissance in computing alternatives. I also noted that the end of the PC era was marked by the end of WinTel at CES.

    In that context, yesterday's WebOS event was perhaps anticlimactic. But it's still remarkable. Consider how far we've come. Step back now and remember the dark days only one year ago when, right after the iPad announcement, a  nearly unanimously chorus was pouring derision on the concept.

    AAPLinvestors is still maintaining the iPad death watch which I took a snapshot of back in March 2010. To reminisce: It was exactly one year ago, on Feb. 10th 2010, that Bill Gates was quoted as saying "It’s a nice reader, but there’s nothing on the iPad I look at and say, ‘Oh, I wish Microsoft had done it.’" On the same day, Shannon Zimmerman of The Motley Fool wrote: "[Apple's] hamster-wheel of innovation ... may have hit a snag with the iPad." Those are just two of dozens other memorable quotes.

    I noted last May that the secrecy surrounding the iPad prior to launch was unnecessary. Nobody understood the product for months after it launched (and many still don't a year later).

    Apple keeps a tight lid on new products so that competitors don’t get a head-start on copying, but in the case of the iPad, advance knowledge would not have had any impact. Competitors look at the iPad and see nothing.  They’ll only react once the market explodes and they start to feel belated pain.

    Indeed, responses only came after sales figures started to cause consternation among competitors.

    How did these presumably keen observers of the market fail to notice the sea change under way? This is not just a rhetorical question. It really is hard. Students of disruption know that spotting such change is a difficult skill to obtain. But it is a skill, not a gift.

    So here we are, 12 months later and the derision has turned to flattery by imitation. The only scorn I hear about the TouchPad is that it can't come to market fast enough.

    ----

    1. I find this term repugnant and highlight it here only to ridicule those who coined it.
  3. Why focusing on a few products is hard

    Research · 59 comments

    "Focus is about saying no." This quote is perhaps apocryphal but it's credited to Steve Jobs. It's not a novel idea. Many companies chant this mantra but do they really understand what focus implies?

    Focus is the antithesis of portfolio theory. Portfolio theory is a great concept. Every pedestrian in New York City has experienced it. While the weather is fine, street vendors sell their regular wares, but when a rainstorm appears it seems everyone is selling umbrellas.

    The idea that you keep umbrellas in stock seems very prudent. It's a hedge that people will need a different product under different circumstances. Maintaining a product portfolio is a way of selecting a collection of products that has collectively lower risk than any individual product. The formulation of this even earned its creators the Nobel prize.

    But "focus" is the willful rejection of this theory. By saying no to alternatives you increase risk disproportionally to the reward. If you have the means to maintain a portfolio it certainly seems imprudent not to do so.

    So why would someone want to focus?

    The answer is that too much diversification is dangerous. It's dilutive to everything the company uses to create value: its resources, its processes and its priorities. It dulls the mind and tarnishes the brand.

    So focus is not just saying no. It's being supremely confident in what you say yes to. It's having the ability to call the winners and the losers. A company that lives and breathes product gains this confidence. A company that puts markets or profit formulas first never obtains the confidence to focus, inflates its portfolio and thus risks everything.

  4. The Apple doctrine

    Research · 95 comments

    The best way to get to the essence of any company is by evaluating its priorities. These priorities are like an unwritten constitution. The analog in theology is dogma which when codified becomes doctrine. In law it's common or case law.[1] In business, priorities are hard to discern and are usually only anecdotally observed.

    At Apple the top priority is the product.

    Sounds trivial, but very few companies place product first. Those who do tend to be producing creative works (e.g. movie or advertising studios, companies built around a creative process). Most companies place either production or distribution first.

    Placing product first forces the bizarre behavior that Apple is well known for: being innovative and quixotic. It makes them foolish and hungry. Sometimes it even makes them catastrophically destructive to competitors.

    ---

    Notes:

    1. These definitions are from Wikipedia:

    Constitution: A set of fundamental principles or established precedents according to which a state or other organization is governed. These rules together make up, i.e. constitute, what the entity is.

    Dogma: The established belief or doctrine held by a religion, or by extension by some other group or organization. It is authoritative and not to be disputed, doubted, or diverged from, by the practitioner or believers.

    Military Doctrine: an established procedure to a complex operation in warfare. The typical example is tactical doctrine in which a standard set of maneuvers, kinds of troops and weapons are employed as a default approach to a kind of attack.

    Common law: also known precedent, is law developed by judges through decisions of courts and similar tribunals rather than through legislative statutes or executive branch action.

  5. Calling the end of innovation in mobile computers

    Research · 72 comments

    People are lining up to call the market for mobile phones. Analysts and amateurs alike are connecting points on charts and predicting with confidence the future of mobile platforms. Consensus is forming that there is no future but a quiescent state. By the acclamation of pundits, the survivors are declared to be iOS and Android. They are also predictably arranged in a way similar to OS X and Windows. End of story.

    Except for one thing.

    3.5 years ago neither of these platforms existed.  In fact, it was only two and a half years ago, in mid 2008, that one of the finalists even became a platform with the launch of an app store. The other "winner" only launched in a handset later that year and had no significant volumes until a year ago. In other words, these suddenly predictable platforms have been in existence for less than the life span of one device that runs them.

    To point out how extraordinary this claim is, if we look back to the history of computing, could we have declared the PC industry future cut and dried in 1978, two years after the founding of Apple? What about 1983, two years after the emergence of the IBM PC? What about 1986, two years after the Mac? Or maybe 1990, after Windows was born? Maybe the writing was on the wall in 1997, two years after Windows 95 caught up with the Mac's UX. That would be 21 years after Apple's founding. Some would argue that even today the story of desktop or portable computing is far from over.

    Sure, times have changed. Things move much faster now. But markets are also much bigger and take a long time to penetrate. Mobile channels are bounded by provincialism and parochialism.

    What's more, it's not like there haven't been platforms before these two upstarts came along. I've seen 9 mobile platforms in 9 years (PalmOS, Windows Mobile, Symbian, Java, WebOS, Windows Phone, iOS, Android, RIM Blackberry). New platforms are still emerging and evolving (e.g. MeeGo, Bada, LiMo, QNX and Tapas).

    So the existential question is this: If you were to draw a time line, would a mark in early 2011 signify the end of mobile platform history? The point in time when unforeseeable change will cease to happen?

    Let me offer a hint as to why not: every major platform battle has been sparked by an innovation built around a new input method. The keyboard integrated into a personal computer in the 1970s, the mouse in the 1980s, the stylus in the 1990s and the fingertip in the 2000s. Each of these input methods created new platforms (DOS/Apple ][, MacOS/Windows, PalmOS/Windows CE, iOS/Android), new ecosystems, new industries, new competitors and new platform battles designed to enrich forecasting pundits. I won't even try to go back to the changed in the half century of computing prior to the PC.

    So here's my challenge to the prognosticators: If you are willing to draw a line in the calendar now and say that no input methods will ever emerge in mobile computing after this point in time I'll buy the thesis that it's over and we can count our chips.

    If you think that out of the hundreds of user experience patents being filed, and hundreds of prototypes being slaved over in labs throughout the world, not a single new product will emerge with a new way of interacting with a computing device, then it's time to move on to something other than what can be declared a commodity market.

    But if you believe that, as happened four years ago, a new input method, previously only in the realm of mockups and movie magic, suddenly was shown, in a working product, on stage, then this business still has a chance of staying interesting.

  6. The Asymco way

    Research · 49 comments

    When I started Asymco.com I did not have a plan. I did not have a policy or vision statement. I wrote what I found interesting. I knew nothing of blogging or of web publishing as a business. Over the following nine months I learned a few things. I also learned a bit about how web publishing (and publishing in general) works.

    My observations were brought into clear focus by this brief overview of the core values of web publishing summed up by this leaked document form AOL: "The AOL Way".

    AOL tells its editors to decide what topics to cover based on four considerations: traffic potential, revenue potential, edit quality and turn-around time.

    AOL asks its editors to decide whether to produce content based on "the profitability consideration."

    The documents reveal that AOL is, when the story calls for it, willing to boost traffic by 5 to 10% with search ads and other "paid media."

    AOL site leaders are expected to have eight ideas for packages that could generate at least $1 million in revenue on hand at all times.

    In-house AOL staffers are expected to write five to 10 stories per day.

    AOL knows its sites are too dependent on traffic from AOL.com, and it wants its editors to fix the problem by posting more frequently, with more emphasis on getting pageviews.

    This codification of values has inspired me to put in writing my own priorities for Asymco:

    • Learn by writing. Teach by listening.
    • Improve. Move the intellectual ball forward.
    • Illuminate topics which are bereft of analysis.
    • Be notable. "The proliferation consideration." How likely is the idea to being widely re-published?
    • Review. Encourage participation by reading all comments and reply to as many as possible. Police comments with zero tolerance.
    • Repair. Declare and correct errors.
    • Select. Publish only when the contribution is unique. Avoid redundancy, clutter and noise. Don't waste reader time.

    Many have asked: What about the business model? I'm afraid there isn't one. I'm still naive enough to think that if I build a great product then everything else will take care of itself.

  7. Google as Android "Vendor"

    Research · 113 comments

    In a recent tally of mobile OS market share estimates from Canalys, the market was organized by OS vendors. The number of devices sold by operating system vendor includes as many OS's as each vendor may supply.

    For example, Microsoft licensed two different OS's during the period: Windows Mobile 6.5 and Windows Phone 7. Nokia also offered multiple versions of Symbian, which have varying degrees of inter-operability.

    Google's offerings include (as per footnote) OMS and Tapas platforms in addition to Android.

    Fragmentation is not a new subject as OS licensing models have been ripe with it for as long as they existed.

    What I want to draw attention to is the concept of Google as "vendor."

    A vendor in the traditional supply chain model is a supplier that sells to an up-stream value-adding stage of the value chain. The word itself has as its root the word "vend" which means to sell.

    But we know Google does not sell Android. And it's not just that Google builds a product and ships it for free.

    There are no contracts associated with the transaction of downloading the Android source. No contract means no obligations, no warranties, no terms and no conditions. The product is not indemnified against litigation. There are no licenses, no support, no copyrights and no patent license granted.

    The contract-less nature of Android makes it easy to distribute. It's one of the key reasons why distribution can grow at 600% a year--there is no distribution in the classic sense. The real disruptive advantage for Android lies in the removal of distribution costs (not just development costs). Google themselves admit that they have no idea who implements the software and how it's used.

    Which makes the classification of Google as a "vendor" a misnomer. The notion of 'vending' something implies a contract. What Google does is write code and place it on an FTP server.

    It's a wonderful way to save on SG&A (there is no sales, general or administrative expense.) But as everyone knows, there is no such thing as a free lunch.

    By avoiding any contractual engagement with the authors of the source code, implementors are subject to independent litigation for IP violations. This is why HTC and Motorola are targets for Apple and not Google.  Google is no more liable for writing Android than the author of a book on bomb making is liable for the bombs put into use [1].

    Patent violation rests with implementation, not the writing of the idea itself.

    Furthermore, Google cannot ensure Android users have any specific experience. They can't encourage upgrades, service models or any form of common UI. The experience, like the protection of property is the responsibility of the implementor.

    Can Google change this approach with Android? Not as long as Android is open source. Can Google change Android from being open source? No, they don't own the source to Android. Nobody does.

    ---

    Notes:

    1. If the bomb making book was a copy of another, then the author is liable, which is the case being made by Oracle.
  8. Of Platforms, Operating Systems and Ecosystems

    Research · 21 comments

    In the earnings Q&A Stephen Elop used the word 'Platform' once, 'Operating System' three times and 'Ecosystem' 15 times.

    Though they seem interchangeable, the three phrases have significant differences in meaning. Briefly put, a Platform is a business model concept,  an OS is a technology concept and an Ecosystem is a marketing concept.

    Platform

    A platform, as the New York Times recently pointed out, can take many forms. The Barbie doll is a platform as is the US Interstate Highway system. These are products or infrastructure that allow other products to be 'built on top' and can thus charge rents from them. When building platforms, a company needs to think of how to make their work foundational so it can support other structures. Other examples of platforms are browsers, the Apple 30 pin dock connector, Game Consoles and Facebook.

    In terms of innovation theory, a platform is a signal to industry that the company is willing to allow its innovations to be extended and thus share in the creativity of adopters. There is however a down side: platform adopters may also create so much value that users will shift loyalties to the layers above the platform thus restricting the freedom of the platform owner to modify or modernize the underlying platform.

    This loss of control over the roadmap often forces platform owners to institute draconian limits to the extensibility of the platform (e.g. the iPhone developer restrictions.) In other cases, platform owners have acquired and integrated various core apps or services so that the platform and core apps can be upgraded in sync. This was the impetus to the development of Microsoft Office. Office was motivated by a need to prevent Lotus from slowing the upgrade path for Windows not, as it's assumed, to create a new revenue source. However, again, the effect is the destruction of the ability to innovate on that particular area (no new Word Processor or Spreadsheet programs for 20 years).

    It takes a great deal of work to platformize a product. I would guess 10x more than a similar product which does not allow collaborative innovation. Platforms are difficult to build, require delicate balancing acts to maintain but can be enormously valuable due to network effects.

    Operating System

    In contrast an Operating System has a very clear technical definition. It has been extended to include many applications and services, but it's basically the control system of a computer. An OS may or may not be a platform. For example embedded operating systems typically do not have APIs to support applications. Some basic mobile operating systems support applications through a sandbox like JaveME (in this case the platform is Java) and are therefore also not platforms.

    A company licensing an OS may not accept the platform with the license or may not consider it valuable. It's even possible to license an OS and consider the platform value to be a liability to your own strategy (arguably HP fits in this scenario as regards to Windows. HP had its own operating systems and tried to build alternative platforms in spite of Windows).

    An example of an OS with minimal platform value may be WebOS which has a very limited API for native applications.

    Ecosystem

    The word ecosystem as it applies to technology was coined by Palm to describe the app vendors that built apps and the accessories for its Palm Pilot. This is not a common word as it's largely equivalent to Platform. The subtle difference is that it's used in a marketing context to signal platform value. Having a large ecosystem implies the acceptance of a platform by a large base of developers.

    For example a platform may not have a viable ecosystem if there are few developers and/or little economic value 'on top' of the platform. Symbian is often cited as being a decent OS, but a poor platform with a mediocre ecosystem.

    So these three phrases are overlapping but have a different tone. Although perhaps unintentional, Elop's emphasis on Ecosystem vs. Platform or OS, might signal that what's missing from Nokia's strategy is the motivation or encouragement of developers to participate. My prediction of WP7 licensing may not fit well with this deficiency but perhaps Microsoft's ecosystem building potential is still greater than Nokia's.

    I should also point out that Nokia's platform strategy has also included an intermediate layer called Qt that enables cross-platform ecosystems, thus making the OS irrelevant. Technically this may have merit, but it's a long haul to getting an ecosystem for it.

  9. A new era in financial analysis is dawning

    Research · 43 comments

    The story of amateur out-performance has been getting more attention lately and that's a good thing. Success emboldens more amateurs to try their hand at financial analysis. Transparency of methods and data demystifies a practice that is not as complex, and a skill that is not as hard to obtain, as it's often assumed.

    While, quarter after quarter, the gap between the two cohorts is calibrated, what we haven't heard much of is a defense from the professionals.

    That's a bit strange given the negative impact some of the attention must be having on their reputations. This is why I was glad to see that Adam Satariano's well-written piece finally got some reactions from the professionals.

    Professional analysts tend to be more conservative. That’s partly because they’re closely monitored and regulated, said Shaw Wu, an Apple analyst at Kaufman Brothers LP in San Francisco. He and his colleagues must pass a series of tests administered by the Financial Industry Regulatory Authority before becoming certified.

    “I have to be careful of everything that I do because it’s scrutinized,” said Wu, who has recommended buying Apple shares since joining Kaufman in 2008.

    Alexander Peterc, an analyst for Exane-BNP, said professionals are “very wary” of putting out aggressive estimates because of institutional memory of past technology booms and potential backlash from clients if they’re wrong.

    “They got it right on the way up, but we’ll see what happens after that,” Peterc said. “Often bloggers and amateur investors are very good in bull markets, but get lost in bear markets. If some of these guys call the moment at which Apple’s fortunes begin to turn I will be impressed.”

    via Apple's `Underdog' Analysts Outperform Wall Street From Helsinki, Caracas - Bloomberg.

    However, neither answer satisfies.

    Wu cites regulation and scrutiny but that does not prevent one from being intellectually honest. What matters is not avoidance of conservatism or exuberance. What matters is rigor; being impartial to everything but the data. One must keep one's convictions in proportion to one's valid evidence not to regulatory oversight (which is there to prevent abuse, not balance).

    Peterc cites pressure from clients (hence the obligations of employment). That implies that professionals are under pressure to say something other than what they believe, which is a sinister form of self-censorship. Not only is that less valuable as an opinion, but it's likely to be less accurate as well.

    But more fundamentally, the issue for the pros is that the institution of analysis risks becoming de-professionalized. In the same way many jobs that took specialized skills became commoditized by the use of new tools or access to information, the era of DIY financial analysis is dawning.

    The difference between professionalism and amateurism isn't whether one is well paid or not or whether one is anointed with credentials. It's whether one is consistently out-performing randomness (note emphasis on the consistency).

    Amateurs can get lucky and pros can get unlucky. But in the end it's about hitting that home run over and over again.

    So the question remains why, in bull markets or bear markets, the professionals are consistently wrong on Apple. The evidence has always been anecdotal and data was fragmented, but now the data is being diligently compiled and it will serve as testament to a shift that I think will be permanent.

    Stay tuned.

  10. What Google can learn from John Sculley: How technology companies fail by placing their strategy burden on technology decisions

    Research · 107 comments

    And so we come to the question of Chrome and H.264. First off, it should be clear that video codecs are infrastructural technology[1]. They are commodity algorithms which are generally invisible to users. They are ubiquitous and are "shared" in the sense that they are available for licensing often without much in terms of cost.

    So they don't really offer strategic advantage to the adopter. Some may end up adding slightly more to a cost structure than others, but not in a way that determines strategy.

    Flash on the other hand is not infrastructural. It is not shared, it is not invisible to users, it is a brand, it has a significant business model and market value. It is sustaining to Adobe.

    So the argument I've heard against Google's decision is that they are using an infrastructural technology decision (a new video codec) to placate or sustain Adobe Flash, at the expense of Apple, a potential or perceived rival.

    If this was the plan, it would be a strategic mistake.

    The reason is that Flash will live or die on the basis of whether the business model is sustainable. That is decided by whether an integrated, proprietary technology is over-shooting and unable to adapt to a mobile computing future that demands modularity from components. If Flash is doomed, then its fate is inevitable.

    In other words, you cannot use an infrastructural technology to defend a sustaining, possibly over-serving technology.

    Which is why I don't think this was the motivation.

    I rather think that Google's decision is a misguided emphasis on technical details in lieu of engaging in a deep strategic re-evaluation.

    A RISCY BET

    To illustrate the way technology companies fail by placing their strategy burden on technology decisions, here is how John Sculley made a decision to go with PowerPC and how he lived to regret it.

    [Our best technologists] came back and they said it doesn’t make any difference which  RISC architecture you pick, just pick the one that you think you can get the best business deal with. But don’t use CISC. CISC is complex instructions set. RISC is reduced instruction set.

    So Intel lobbied heavily to get us to stay with them… (but) we went with IBM and Motorola with the PowerPC. And that was a terrible decision in hindsight.

    ...

    we totally missed the boat. Intel would spend 11 billion dollars and evolve the Intel processor to do graphics… and it was a terrible technical decision. I wasn’t technically qualified, unfortunately, so I went along with the recommendation.

    I would argue it wasn't a failure of technical knowledge--the technicians were right about the architectural advantages. It was a failure of strategy and understanding of innovation dynamics[2]. Sculley asked the wrong question. The question to be asked is not "CISC vs. RISC". Rather, it should have been: Is the architecture the relevant decision point or is it the choice of partner? The technologists put the architecture choice above the more strategically important question of whether Intel had the fuel to continue getting better even if saddled with sub-optimal architecture.

    That decision sounds very similar to what is being done today at Google. Increasingly, technology decisions are leading strategy. The question should not be "H.264 vs. WebM" or "HTML5 vs. Flash". Google should be asking itself if mobile computing will allow browsing to remain the predominant interface for internet consumption. If, as I suspect, it won't then no amount of browser tweaking will help. The browser is already infrastructural. It can't be the object of strategic focus.

    To get an idea of how this would work consider Flipboard. Flipboard turns the entire browsing paradigm inside-out. Instead of consuming social media inside a browser, the app presents it in a more natural magazine-like format.

    What will happen when that media becomes predominantly video? Flipboard will be far more influential to content producers and their decision on which codecs to support will lead adoption.

    By focusing on threats and byzantine standards machinations, rather than on broad, experiential learning, Google missed (yet another) next big thing.

    ---

    Notes:

    1. In  IT does not matter. Nicholas Carr introduced the concept of infrastructural technologies. Becoming Infrastructural is what happens after a technology overshoots the market and stabilizes into a commoditized ubiquity. It ends up being "shared" in the sense of being openly and sometimes freely licensed.
    2. To be fair to Sculley, the research on innovation theory that would have helped him had not yet been published.
  11. Who killed the Intel microprocessor?

    Research · 76 comments

    The recently announced move by Microsoft to support the ARM architecture with their Windows product, indicates something profound is happening in the market for microprocessors.

    Dr. Hermann Hauser puts in bluntly:

    “The reason why ARM is going to kill the microprocessor is not because Intel will not eventually produce an Atom [Intel's low-power microprocessor] that might be as good as an ARM, but because Intel has the wrong business model,” said Dr. Hauser. “People in the mobile phone architecture do not buy microprocessors. So if you sell microprocessors you have the wrong model. They license them. So it’s not Intel vs. ARM, it is Intel vs. every single semiconductor company in the world.”

    via Intel Microprocessor Business ‘Doomed,’ Claims ARM Co-Founder - Tech Europe - WSJ.

    To make sense of that you have to step back and look at what's been happening in microprocessors and how mobile computing is affecting the whole processor value chain.

    The first observation to be made is that, as Dr. Hauser points out, ARM licensees use a different model than Intel. The development of an ARM-based microprocessor is done in a modular way; in contrast to the integrated way that Intel builds their products. ARM supplies a license, and designers build the chip adding various other circuits like Bluetooth or music decoding on the same silicon as the processor creating so-called SOC (system on a chip). Nokia has been doing this for years and Apple began doing it recently with their A4 SOC.

    The design is then sent to a fabricator who actually manufactures the chip (TI and Samsung are some of the bigger ones), often in smaller batches than what an integrated vendor produces.  SOC fabs need to be much more flexible in their production and are much more sensitive to the needs of their customers, the designers.

    In contrast, Intel has a proprietary microprocessor architecture that is not available for licensing and they have their own designers and their own fabs to build chips that they sell from a catalog to device builders. PC or device vendors only get to use what Intel offers and there is little in the way of customization (In a rare exception Apple famously forced Intel to modify the packaging of the first CPU fitted to a MacBook Air.)

    Because of the differences in business models, the markets for SOC and microprocessors are diverging rapidly with subsequent business model priorities becoming completely asymmetric.

    To illustrate, I draw upon an observation[1] that due to Moore’s Law, every year, through the equipment they deploy (e.g. from Applied Materials) fabs make 60% more transistors available on an area of silicon than were available the prior year. Intel almost always takes advantage of this by making more cores or adding more cache.

    But if you look at the ability of SOC designers to utilize transistors, they are only able to utilize 20% more transistors than they were the year before. The reason is that they have constrained design budgets; they don’t have enough money or time to design circuits that are complex enough to utilize all the transistors that Moore’s Law makes available. Plus, when it comes to devices, they don't need the power.

    What that means is, for most of the volume applications in the world, circuit designers are actually awash in transistors.  They are being over-served by the advances in fabrication equipment. However, Intel designers aren't. Being at the very high end they still need even finer line widths and demand that Moore’s Law take the next step to that next leap of technology.

    What value chain evolution theory would then predict is that circuits which had to be proprietary and interdependent in their architecture are following an over-service path. In contrast, to serve the needs of SOC designers, fabs, as suppliers, will have to change their pitch for winning new business to being fast and flexible and responsive and to being able to deliver systems on chips that offer every device exactly the functionality that they need and none of the functionality that they don’t need.

    Now in the world of mobile computing (and almost any situation where logic gets embedded in a system) it’s the device itself that is not yet good enough and, therefore, you cannot back off from pushing all the components to conform to your device's purpose.  For a device to be competitive it has to be optimized with a proprietary, interdependent architecture.  That means that the processor inside of a BlackBerry or an N8 has to be modular and conformable to allow the system to be optimized.

    This is a quirky idea so I'll repeat it: since the device is not good enough it has to be integrated, including the processor, which being good enough, has to be conformable. The processor has to bend to the will of the device market not vice versa.

    This then puts Dr. Hauser's point in perspective: a modular business architecture for microprocessors is a necessary condition to being successful supplying devices. The corollary is that Intel's integrated business model is obsolete in a device world. No amount of polishing of the Atom will help.

    The root cause for this obsolescence is the over-shooting of Moore's law when processing power (and hence circuit density) is superfluous while power consumption, size and flexibility of design are straining to eke out any improvement.

    So this renaissance of ARM is happening now because Moore’s Law has overshot what most circuit designers can utilize. And that overshooting is happening because mobile computing products don’t need a multi-core multi-gigahertz processor, allowing designers to back away from the frontier of what's possible.

    What it culminates in is that the places in the value chain where attractive profits can be earned are migrating in a very predictable way: away from Intel and toward ARM.

    So in a perverse way, it was Intel founder Moore's law that killed the Intel microprocessor.

    ---

    [1] This discussion is inspired by Clayton Christensen's "Capturing the Upside" presentation at the Open Source Business Conference 2004-03-17. Although taking place nearly seven years ago, Clay's vision regarding the future of the microprocessor was astonishingly, though perhaps unsurprisingly, prescient.