Does EMM have to be so difficult? This is a question that bothers me very much, every single day. I mean from the perspective of the customer. Expectations soar high every time there’s a mention of an EMM implementation. And every time I feel I know the answer, there’s ‘one more thing’ that gets added to the EMM definition that makes it all the more elusive. And there it is – that’s exactly why. EMM means many things to many people.
CIOs and the IT Operations teams view EMM as a tool to improve operational efficiency in managing mobile assets (asset inventory) and monitoring their compliance status. Business Unit Leaders want EMM to help their sales teams access corporate resources anywhere, anytime on any device they prefer so they can enable their salesforce with real-time information. And employees want to be able to be good citizens of the workplace and be more productive without waiting for the right time and place.
CISO’s and the Security teams rely on EMM as a reliable tool to set security policies on the device, prevent data leakage from applications, ensure regulatory compliance by enforcing encryption and so on.
Not only are we dealing with two orthogonal requirements, we are also looking at a single tool that literally becomes a ‘swiss-army knife’. A tool that has to meet the diverse requirements of diverse industries. And a tool that has to keep pace and be built on top of an ever changing OS platform.
I like to use the metaphor of the ‘Operating system for the Digital Workplace’ to explain the complexity of EMM.
The Magic Quadrant for EMM was published last week. This year we have a few new vendors that made it to the MQ and a few that were left out or simply disappeared. Interestingly, there are no challengers this year. In many ways, this market is unique in that every vendor approaches it with a vision that they beleive will define the next ‘Digital Workplace’. Most solutions will appear to have very similar foundational components, but are yet very different when it comes to actually using them. I like to use the metaphor of the ‘Operating system for the Digital Workplace’ to explain the complexity of EMM.
Amidst all this chaos is the misconception that EMM equates to mobile security. And Gartner frequently encounters questions such as – ‘Do I need anti-malware when I already have an EMM tool in place?’ or ‘Can I extend existing investments in antivirus utilities on the PC to mobile devices?’
To answer this and elucidate the difference between EMM and Mobile Security/Mobile Threat Defense tools, Dionisio Zumerle and I published a research note When and How to Go Beyond EMM to Ensure Secure Enterprise Mobility.
The journey has just begun for most organizations. Organizations that have no management in place are starting out with MDM, others are beginning to manage and secure apps via MAM, few others that have apps deployed are looking for ease of authenticating users using SSO capabilities and Biometrics.
Watch this space as we jointly explore more interesting aspects of enterprise mobility. EMM is but one piece of the puzzle. Enterprise mobility is a moving target, or should we just say – a ‘mobile’ target?
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
How to Live Without Mobile Device Management
This webinar addresses the growing trend of users refusing to have enterprise management of their mobile devices due to privacy concerns....
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.