Next Steps For RIM?

With less than ideal numbers for Q2, and lots of dire predictions and teeth gnashing, asking “what’s next” for RIM naturally arises. There are plenty of ideas: sell to someone else, break it up and sell off the pieces, nothing is wrong so do nothing. First, the idea that nothing is wrong is a bit optimistic. RIM has been losing marketshare for a while now, with little end to the decline in sight. The Playbook has been a dud. Some were expecting Blackberry 7 to make some difference, but so far, it hasn’t even put a scratch in the other guys. Why should it? It’s not like it is so completely new and different. It’s another evolution, and another operating system that you can only get by upgrading hardware. There are others that think that the future QNX-based devices are going to be RIM’s saviour. I’m not so sure. Those are still a long ways out, and there is a new iPhone and probably another iPad iteration coming before the middle of next year. QNX could be RIM’s swan song in the handset space.

But what are the options and alternatives? Can RIM be saved in any way at all, or is some kind of break-up and/or sale the only option?

Before discussing a possible path to the future for RIM, I think it is important to understand RIM’s problems, and where they stem from. The issues are RIM aren’t financial, at least not yet. They have a modest amount of cash in the bank, and while market share continues to slip, they do see increases in unit sales (it’s the “rising tide lifts all boats” effect of a growing overall market). RIM’s problem, fundamentally, is product. They have products that fewer and fewer people (and companies) want. This product problem stems from a “handset-first” approach to the underlying operating system, devices, ecosystem and upgrade paths, that all starts at the top, with Balsillie and Lazaridis. There is no question that these are smart guys. They got RIM to the top in smartphones in North America, and became a credible number 2 globally after Symbian. But they seem to be stuck in a mindset that people are buying handsets, and not small mobile computers. They focus too much on what the carriers want and seem to largely ignore the customers and the app developers. To improve its product, RIM needs to change its mindset and culture. That won’t happen with the current senior management in place.

So, how do you fix the product? What does RIM have that could save it? First, I don’t think that trying to sell yet-another-mobile-OS is the way to go. The market has made its choice, and that is iOS and Android. It doesn’t matter if other operating systems are technically superior. Customers don’t buy tech specs, they buy devices that they can do stuff with. Both Android and iOS have rich ecosystems, with very, very large selections of apps. It doesn’t matter that there might be enough apps on Blackberry AppWorld to meet most customer’s basic needs. People look at the numbers: AppWorld has a few thousand, Android Market and iTunes App Store have hundreds of thousands. Two have “lots”, one has “almost nothing”. A new operating system isn’t going to change those numbers for RIM. Instead, I think it is time to face reality, and face up to the fact that neither Blackberry OS nor QNX have a viable future.

What does that mean? One word: Android. It gives RIM instant access to a large suite of apps and a large body of developers who want to build them. It means RIM will need to give up on the idea of getting any revenue directly from apps, unless they want to run their own app store. I would counsel against that. It just adds to the fragmentation in Android app stores that is starting to build, and they would likely be lost in the noise.

Okay, but how does becoming yet another Android manufacturer help RIM? By giving them a popular platform on which to continue to build and grow their considerable expertise in the enterprise market. RIM has 3 powerful products that risk dying along with Blackberry and Playbook: Blackberry Enterprise Server, Blackberry Internet Service and Blackberry Messenger. RIM was able to more-or-less own the enterprise market, from small one-person shops to large multinational corporations, on the strength of the infrastructure that supported the Blackberry device and made it useful. It was what allowed Blackberry to supplant Windows Mobile and PalmOS in North America. Even with additional features in products like Microsoft Exchange, BES offers better security and tighter integration with the devices, but only with Blackberries. RIM needs to broaden the appeal of their server-side products, and using Android allows them to keep that, but widens their appeal on the consumer side by having access to apps (and lots of them) without some awkward or “it works most of the time, except…” emulation layer.

What I see is a 4-prong approach. It start with RIM-built and RIM-designed Android handsets that include built-in support for BES, BIS and BBM right out of the box, tightly integrated with the operating system for communications and security. This combination would give enterprise customers the security and control they are familiar with today. For consumers, it would give them easy access to infrastructure (through BIS and BBM) that is both secure and simple to configure.

The second prong is to include Android apps from RIM for non-RIM Android devices, so that they can get some of the benefits of BIS, BES and BBM. This expands the potential customer base for BES installations, such that RIM could be making BES and in-house BBM server sales to companies, even if they don’t want RIM devices. BIS could offer a basic, free level of service, as well as a subscription-based service for more features.

The third element is to build apps for iOS, along the same lines as the general-purpose Android apps. Stop excluding Apple devices and, again, include them and make the case for BIS, BES and BBM, even if the customer wants to use iPhones or iPads. It won’t be as tightly integrated as a RIM/Android device, but some integration is better than no integration.

The money for RIM won’t necessarily be in the handsets, and it won’t be in the apps. RIM could potentially charge a premium for some of their devices (mainly those aimed at the enterprise market), and some companies might be willing to pay to gain the added security and control. Even if they don’t want the RIM devices, RIM can still provide them with secure, reliable, scalable infrastructure. Their revenue will be largely in infrastructure and services. I would still see some handset revenue, but it may not be as big as it has been in the past.

The fourth prong in this is a bit more radical, and builds on ideas others have put forward: the idea of virtual devices on a single handset. The reality is that people want to be able to keep their handsets, and use apps they’ve paid for, but still be able to use it for work. They don’t want to have to carry 2 phones, and they don’t want to have to lock-down, compromise or otherwise give up control of their handset to use it at work. There is work underway to build virtual handsets, where a single device would have multiple personas. RIM should jump on this, offering a “virtual handset” for work-related activities, that is locked down and controlled by the employer’s IT group, plus a second virtual handset that is the user’s. This would mean adding features to Android that can run on more than just RIM devices. It won’t be easy, and it will have considerable challenges. But it offers companies a way to let people keep and use their own devices for work-related activities, while maintaining the control and security that some organizations need. If RIM wants to try to keep the enterprise market, or at least maintain a reasonable presence, I think this is part of the solution to doing that.

These are radical ideas, no question. But RIM’s current plans really don’t give the company a future, as far as I can see. There are other technically competent operating systems (WebOS, Windows Phone) that are either dead or dying. The Playbook has been a complete dud (1 million units in the first year? Who cares? Apple sells more than that in iPads every 2 weeks). Developers don’t care about Blackberry, and QNX isn’t going to change that: it isn’t the platform, it’s the size of the customer base that counts, as well as the toolset and relationship with developers. Stop trying to fight the market, and instead go with it, but build on your own strengths.

I doubt these will ever come to pass, for one simple reason: it will take too long to bear fruit. Even starting today, RIM would be hard-pressed to have their first Android units available in a year. However, they could have their Android and iOS apps ready sooner, with updates to BES, BIS and BBM to work with them. That would keep RIM relevant while they worked on handsets and tablets with their own enhancements. However, shareholders and the market are growing impatient, and I expect they’ll take the easy way out: break up the company and sell off the pieces. It will probably start with Balsillie, Lazaridis and other senior management being replaced. Their replacement(s) will then start to package up the company as the talent jumps ship, and without that talent, some of the parts of the company just aren’t worth as much.

It is too bad, because there is a lot of talent at RIM. It is being held back and misused because of a commitment to failing products and no real bold or innovative initiatives. I’ll admit that “build another family of Android handsets” doesn’t sound very innovative on the surface. But, unlike the Samsungs and HTCs of the world, RIM still has a sizeable presence in the enterprise space, as well as experience running large and reasonably reliable infrastructure services. Building Android handsets, while a bit “me too” in appearance, means RIM can focus on the areas where they actually add value, and take advantage of Android’s presence in the consumer space. It solves the “we don’t have enough apps or content” problem. It widens the appeal of BES, BIS and BBM from the limited base of RIM-only devices, and would open up a lot of devices to be able to run on those servers, making them more appealing to enterprises. It’s a platform with a future and consumer interest. It’s a product people want, and that is ultimately what RIM needs.