<img src="//pixel.quantserve.com/pixel/p-_JKXxuL8SR7wu.gif?labels=_fp.event.Default" style="display: none;" border="0" height="1" width="1" alt="Quantcast">
blog-banner.jpg

Next-Gen CASB Blog

How Enterprise Mobility Management (EMM) Can Annoy Users

By Bitglass | June 13, 2016 at 10:00 AM



Video Transcript

Hi, I'm Mike from Product Management at Bitglass. I want to talk a little bit about enterprise mobility management and how users interact with devices that are managed. From a solution perspective there's two camps of things that people do. One is, they manage devices with something called an MDM, a Mobile Device Management solution. That allows IT to be able to control the apps that can go into that device. They can track various content from a perspective of user's location, the configuration on the device, and they can control it, but it is more focused on managing the device.

From a perspective of adoption, what you get is a user base where I have, let's say, 5000 employees in my company, and I want to make them all adopt this solution. From the perspective of manage devices, that's pretty straightforward. I can force someone to come in and adopt the solution, install them on their manage devices and, let's say that a third of the total devices that exist in the enterprise. Now, when I start to try to roll this out to BYOD, all those more onerous types of management, the location tracking, and what apps are on my phone and whatnot, puts just generally users off. What usually happens with this is they start to stall out.

You get a little bit of adoption and then there's a bunch of devices that you're actually not protecting, which is obviously a negative. Another approach, instead of the full-on device management, is more granular where you do, instead, a MAM, and I have a container inside of my phone that has apps, and data, and content. That's a little better. What that allows you to do, from a solution perspective, is to be able to manage that these devices get installed in the container. They can only be open inside of the container. It's almost like a different persona almost, where I hold my phone and I select, "Am I doing work contact or am I working with content that is more personal?" That's good as well, but that has downfalls too.

If I'm on my phone and, let's say, I have a conversation with my wife at lunch, and I get a personal, another personal call, everything's fine, everything works out great. If I get a call though, that is based on contacts that are inside of this MAM container, something like a work phone call, since the contact is inside of the container, I will get a unknown number, so I can't tell who's actually calling me. That's highly problematic and annoying. What happens, from a user perspective, is that when they have these devices, and this is a little bit better than that, right? Then they start copying the contacts over into their personal contact list, which is obviously something you didn't want in the first place. Right?

The other issue that comes up a lot is things like calendaring. When I'm trying to schedule something that's personal and then, all of a sudden, I want to check on if they coincides with another event that may be work related, I have to switch personas. I have to switch into this other calendar and it's completely separate. That can be annoying as well. In general, there's different types of solutions that are less EMM focused and more focused on data that are coming out. Bitglass has a solution that allows you to do something like that, which is actually of primary interest for companies that don't want all this heavy-lifting to do from a device management perspective and whatnot, so check it out. This has been another Bitglass Glass Class.