What killed Blackberry? Employees started buying their own devices
washingtonpost.com
washingtonpost.com
I was in IT support at the time they came out. One of the things I hated about IT support, and I found it common with most colleagues, was the idea that if you are in IT, every thing with a plug or batteries is some how part of an IT person's skill set. Because we are the clever mysterious people who can fix the server, we must also be able to explain the MD's new HiFi to him, fix the microwave or mobile phone, or some such.
So, out comes Blackberry and it suddenly becomes the executive's toy of choice, and we were expected to support them. No one asked, there was no meeting or consideration, they just bought Blackberrys themselves, bought them in and expected us to be configuring and supporting them. Its was like a suddenly change in infrastructure that just arrived because individuals insisted on it. And because usually these were senior people, management expected us to play ball. It was kinda like the whole system being windows and one day some one installs Linux and expects it to be instantly supported and integrated, regardless of whether or not the company software actually ran on it. And early on, that wasn't trivial.
So, what happened in my IT circles was that Blackberry got a bad name because its was a toy executives lumped on us with out any consideration, let alone some sort of discussion, and heaven forbid, planning. So, the sort of back ground vibe was negative, and for many I know, remains so.
So, even though all these years on it is likely to be very unfair, I still see Blackberry as representing arrogant unthinking executives and the resulting headaches, and there for negative.
Edit: And I missed the obvious. Im so brain dead at times....
It is suggested that employees buying their own phones killed the Blackberry. Yet, ironically, in my experience at least, it was employees buying Blackberrys that got them their traction in the first place.
"No, I won't" is the wrong answer. The above comes to the same thing, but in my experience is not going to result in dismissal.
He could advise her and tell her why it is a bad idea, and if she still wants to use it, he must support it.
Instead he said no, which is fine from his side. But If you don't want to do something the company expect from you, don't be surprised if you get fired.
Basically, he didn't like being told by the not particularly technically knowledgeable CFO/CIO what technologies to deploy. We had Netscape Calendar/Email. He knew Netscape Calendar/Email. He wasn't interested in deploying a new Calendar and Email technology that he didn't know. The new boss really wanted support for her Blackberry.
To some degree it worked out well for everyone. He was fired, and went to a new job where he got to work with Unix Technologies, and the new IT Manager was hired to deploy Microsoft Exchange.
Ive tried to play ball and call to meetings for distasteful and wasteful requests/requirements from business/manager people, but its such a drain on my energy as a developer, I just began saying flat out No. I take the risks of getting fired, but I will not be bitter 10 years from now for sitting in meetings discussing what is a change request and what is a requirement with people who have not read one paragraph on software engineering, trying to get me to once again change the functionality of the app because of their change in opinion, or trying to just get me to do things just because they say so. Fuck that, and fuck no. Im out. If I am expected to be a code monkey at a workplace, thats not the workplace I want to be at.
Also I would start looking for a new gig myself...
But it's a different context and situation to the one above. If I came to you as a software engineer and said; "Antocv, our new customer is insisting that we add an extra step in our QA to get our contract signed off" I would expect you to either say "Sure, no problem" or "My friend, it sounds easy, but the thing is that doing it will sink us. Because..." if you said "No" and left it at that I'd conclude this is a guy who I can't work with.
The thing is the reasonableness of the behaviour - if I come to you with a request that you can fulfil reasonably and you are paid to do it, you should do it, or find a way to let me know that I do not really want you to do it in the first place. The "because" is the critical thing; random acts of rebellion are not helpful.
But be clear; nor are dickheads from HR/Accts/Sales appearing and announcing that they know how to do the jobs of skilled professionals by remote control. That's every bit as unacceptable as uncooperative techies, and if you are in an environment where that washes it's definitely for the short term only. It just means that money is being wasted and no one knows what to do.
Either leave now, or put up with it until they go bust; there is no third way.
BlackBerrys have never been particularly attractive, cutting-edge, or user-friendly.
As you say, they were definitely seen as attractive, cutting-edge, and user-friendly at one point because the execs forced them into companies. Pretty much right up until the day the iPhone came out. They went from great to old fashioned almost overnight.
Anyway, I've always advocated dumping legacy browser support because once the right people have problems viewing the web, fires get lit and the job gets escalated.
The only people who can't upgrade their own browsers are the ones with an IT team standing in their way.
If you want bleeding edge software across the organization, admins need to have enough extra free time to coordinate the rollout and get the training to support it. Recall the administrators "prime directive" - fix what's broken. If the admin team is swamped with tickets all the time, you'll be stuck with legacy stuff, because they don't have enough time to adapt.
We have a joke at work that new stuff gets done during our "infinite amount of free time".
Typically, the issue is like this:
1) Management demands that a specific solution is installed, and ignores IT's complaints
2) The solution requires an environment IE 7 (or Windows XP, or... take your pick)
The admins now have two problems: they need to convince management to move away from the old solution to a new one (another capital expense), in addition to maintaining a hateful, old environment so that the business doesn't break. Senior management doesn't realize they dug their own grave, and refuses to pay for the capex "just" to have the latest version of the solution, when the business is seemingly working just fine on the current environment.
Eventually, after much praying and finger crossing, only one of the two things saves the admins:
1) The solution is upgraded to support modern software
2) The environment becomes unsupported, and management is forced to reconsider the upgrade.
Have some sympathy, mate! :(
IT keep servers machine running, they don't care that those machine aren't doing anything useful. The server software stopped being useful years ago yet they keep it running at all costs because their job performance is tied to uptime. When I work our yearly mandatory training requires Firefox 3.6.23, IE6 or Netscape! People have to borrow loaner laptops that nobody dare upgrade just to do the training classes. This is thanks to our IT department not wanting to support "newer" technology. Eventually we get a new VP who fires all these people that don't understand that people want to use iPhones and VPNs and WebEx on their iPad and it's not ITs job to put roadblocks in their way, but instead to figure out how to support it.
"I still see Blackberry as representing arrogant unthinking executives and the resulting headaches" - you mean the people that pay you and figure out how to stay in business despite your best efforts to thwart it?
Blackberry made a tremendously successful high featured phone. Then Steve Jobs and Apple released a full-fledged minicomputer that fit in the palm, with a usable interface, that happened to also function as a phone.
The iPhone killed off more than the Blackberry. It killed all off all phones in favor of small computers that happen to function as phones.
iOS is responsible for more than the raw numbers suggest. iOS begat Android, WP7, and countless lesser imitations. Whether this was through inspiration, as I believe, or outright theft, as Apple maintains, is immaterial.
The fact is that the modern smartphone market was born with the introduction of the iPhone. All else before was prelude.
1. http://www.practicallyefficient.com/home/2010/09/28/the-adja...
http://www.osnews.com/story/25264/Did_Android_Really_Look_Li...
http://www.engadget.com/2007/11/12/googles-android-os-early-...
http://www.idownloadblog.com/2011/10/27/android-handsets-bef...
Apple's "Godphone" keynote was a rude awakening for an industry who had dragged their heels for years, providing a rubbish experience for users and locking all but the largest developers from any access to their devices.
But you fail to see that:
1) red went there from nowhere. In a totally unrelated industry from zero to hero.
2) all other colors, from that point on, started offering stuff just like what red introduced. Before the iPhone's introduction, the top 10 phones looked totally unlike it. So much unlike that people thought it would be a flop, and considered the total lack of physical keyboard "insane" (!). After that introduction, all they started look totally the same.
(Including Android, whose prototypes shown just before the iPhone announcement were crappy, 2006 like regular phones, with physical keyboards and a small screen -- and whose firsr version, introduced a whole year after the iPhone was just like it).
Android didn't have an ability to do that for awhile unless you used apps like Touchdown. IMO, android started hyper growth in 2010-2011.
I ran a 100,000 seat exchange environment from 2008-2012. We had 50 active sync devices in 2008. 3,000 in late '08, 8k in 2010 and around 10-11k today. During that same period, BlackBerry went from 5,000 to less than 500.
It takes that long (and more) for a platform entrenched with enterprise users to lose its dominance. Those are slower to adapt than the end user market (consider enterprises still using IE6).
Plus, the original iPhone didn't have Exchange support and some other stuff RIM users would want to ditch RIM, it got that later.
Here's one smart take on this (from 1.5 and 2.5 years ago, clearly seeing where things were headed):
http://www.asymco.com/2012/04/24/unforgiven-the-consequences...
http://www.asymco.com/2011/06/02/does-the-phone-market-forgi...
From April 2012:
"The rumors swirling around RIM and LG are centered around exits and some suggest Nokia will follow. [...] Earlier last decade the exits were prompted by loss of brand value and subsequent loss of distribution. This decade disruption brought upon by mobile computing brings with it new business models centered on ecosystems and value captured through software and services."
They didn't see the world beyond that. There wasn't an even reasonably decent browser in 2009, when I stopped caring. Apple and android changed everything by creating an Internet consumption device.
Blackberry killed blackberry.
The Opera browser was quite nice for BB in 2009. But if you mean native browser, you're absolutely right.
In 2007 the iPhone was seen as an oddity by those who used their blackberries for business - without a keyboard, and really rudimentary communication tools, it wasn't ready for real-time business communication. But wow - that browser, and maps app was something else; and then Apple let third parties develop applications for the iPhone...
By 2009, after a couple iterations of the iPhone, I was running a network engineering team, and provided everyone on the team a blackberry so they could communicate real time with each other (We had a corporate BES server). Every single one of them was left in a desk drawer, as people ignored them and just connected their iPhone to their iMap account and used SMS for the real time stuff.
I just got back from a 4 week engagement in Singapore, and I was working daily with fifteen people in five organizations across four companies, distributed across three sites and field visits. We had to perform real-time communication during some particularly tricky diagnostic event on hardware, at the same time we were tracking some configuration remediation in a meter-lab. Every single person present (except for one poor Field Engineering manager from California who showed up with a non-GSM android) kept in touch with WhatsApp. We didn't even have to supply the four college students we hired to do some field-evaluations with phones - they showed up with their own devices (all Androids), and we simply added their accounts to our group chat system. Latency was on the order of a second even with Singapore's surprisingly iffy data environment (at least from the perspective of my California AT&T iPhone)
I think a major contributor to the death of blackberry was a combination of iMap ports open to the internet + Exchange Support in iPhone + awesome replacements for BBMS (inexpensive SMS, Viber, Whatsapp, etc...) - every key advantage of the Black Berry, with the exception of that keyboard, has an equivalent or better replacement today on the Android/IOS platform, with the addition of a world class app suite that's available on the Android/iPhone, but will never, ever, come to the Blackberry (except in the form of Android sideloading - but that further kills the need to develop blackberry specific apps)
That's what killed the Blackberry.
http://en.wikipedia.org/wiki/Internet_Message_Access_Protoco...
I would probably had seen IMAP thousands of times. iMap is the first time and has a very similar shape to iMac that is very known for me as I had several of those.
I don't really know why he starts with lowerCase, them Upper case in the middle, then lower again.
Is that the new maps in iOs?
Only after reading your message I connected the dots.
http://blog.whatsapp.com/index.php/2012/01/1-million-is-so-2...
This probably isn't the main thing that killed RIM, there were probably hundreds of reasons, but over time this put in a culture of complacency, and there probably isn't much upper management could have done, because it was all done for the sake of improving "company culture"
That is different to people who don't understand something but ask the right questions so that they understand and can apply in future.
"Sure Boss, I'll sort that out for you, I'll get a business case for the migration together over the weekend, can we meet on Monday to go through it and sign off?"
Moving off IE6/7 costs £x k, because there are 1->1000 applications (I know my company has about 30 major ones) that are known to need changes to function on later versions properly (even with compatibility mode) and 100+ that will need some testing.
Now, when I say these applications need work, often the problems are incredibly trivial, but in a corporate these things (a button has moved, a menu item doesn't work but the button does, you need to hit the ok button not hit <enter> etc. GENERATE HELPDESK CALLS!
And the calls don't go away after 2 days as the users get used to it - they are ongoing, there will be escalations, your manager's manager will be teased at the SMT event, worse your manager's managers peers in other corporates will get war stories featuring your manager in A BAD LIGHT (think about the implications of that) all of which is unfair and silly.
But this is what will happen.
Ok - you get the case done, you see your boss. The number is £30k; is it in the budget? No.
The consequence of not doing it? Your manager shows the case to her manager.
The consequence of doing it without the migration: see above.
End off.
RIM won by showing up and not being totally incompetent. They lost by being complacent.
The Thesis goes: employees bought iPhones and brought them to work, enough (or senior enough) employees were able to force IT departments to support them. Afterwards no-one wanted to use their crappy old phones.
If only this could happen for Browsers, too!
I think it's time to start a campaign for 'Bring Your Own Browser To Work Day".
> I think it's time to start a campaign for 'Bring Your Own Browser To Work Day".
It is entirely possible that that is what tablets are. I suspect that some of the crufty old "we see every packet" IT groups the notion that you can have your own tablet at work getting 4G network access outside the company control structures is exceptionally challenging.It already happens to an extent. I work in an environment where we have very limited control over our desktops. Can't install software, can't use the command prompt, etc. IE7 is the mandated browser. I'd estimate that at maybe a third of staff run either Firefox and Chrome alongside IE7. Neither requires Administrative privileges to install and so users just get on with it.
The problem is that market is about 1% of the market for the touch-screen, independent-app rich, no-keyboard market.
It's not an uncommon situation - do you sell your soul to chase the $$$ or stick with your core mission, money be damned.
Tangentially- when I went to check out the Z10 it was locked in a demo mode. I couldn't figure out how to look at anything on the phone that they didn't want me to see with "helper" sales pitch notes. I finally found a real phone one of the employees was carrying and was able to try it out (and buy something different).
I couldn't believe they (or AT&T) would think so little about their customers and providing a real experience on the device. It insulted me. Maybe it changed later...
In 2008 I believed android would dominate the smartphone market. This was even before the first android phone was brought to market. Most consumers had not even heard of android back then and the iPhone was quickly gaining market share. Why did I think this back then?
What killed BB is, at core, the result of Geography. It is not only the fate of societies, a la Jared Diamond, but the fates of tech companies that geography can influence. In 2008, I was living in northern California and you could sense the amount of developer interest in android. What android did and BB couldn't do (or really try) was to win over developers. Many were upset at Apple's process for publishing apps. Google did everything to address those concerns. Instead of winning over consumers first, android won over the developers who then made the apps to bring those consumers. BB was just too far away and too out of touch to see any of this.
The world is not flat. Place matters. If it were as simple as focusing on consumers, why did Nokia lose despite doing this all along? -Geography! And why did android win despite not initially focusing on consumers? (the G1 was a crappy phone). The winners (android and IOS) won because they're located in Silicon valley where most of the best developers are. The losers (Nok, RIMM) lost because they weren't.
No, "the best developers" are not all in California.
The "BYOD" culture is some crucial damage for BlackBerry. But what will wipe them off the map isn't really that, but rather, not being even an option for a second device, enterprise-only. Because they've got nothing to add.
If the iPhone didn't appeal to the top tier, the Blackberry would have reigned supreme in corporations.