Not too long ago, BlackBerrys were the go-to business tool. Revolutionary for their time, they provided two major benefits. Not only did they offer fresh communication potential that significantly altered the way that professionals work, but for the IT team, the BlackBerry made their lives a lot easier.
In more recent years, its major let down wasn’t that the company previously known as RIM’s rate of innovation was futile (though it didn’t do the company any favors). It was that BlackBerry was an expensive platform and essentially an IT tax on every connected employee.
It was a brilliant product strategy that generated revenue for RIM in a way no other BYOD solution has managed to duplicate. Initially a couple of geeks in IT - or more often ops - got RIM devices, which were then noticed by a techie senior exec.
That then drove executive adoption, and for that you wanted a BlackBerry Enterprise Server. Once the BES was in place, then you were a single solution organization -- RIM. Every new user bought hardware and a BES seat. Budget managers were forced to accept it.
Fast forward to 2008 when a few techies, often marketing people, started showing up with iPhone 3s. They were connected enough with a friendly IT admin to get Wi-Fi access. Techie execs saw them and said they wanted them too and “best of all,” said the first adopter, “you don’t need a BES server and I’ll pay for my own device”.
Once the budget king got wind of that, BlackBerry was done. Unfortunately, so were the days of easy device administration. Apple and Microsoft saw an opportunity and quickly worked together to make the iOS/Exchange Active Sync at least marginally useful to IT, allowing the budget office to counter the IT manageability argument. IT relented and opened some Guest SSIDs (service set identifiers).
As with any shiny new technology that changes the world in a rush, this has produced a growing problem for IT managers. Few organizations believe they have an adequate BYOD management plan and it’s further compounded by the ever-increasing MDM (mobile device management) problem that had already been an issue for some time.