The official hub of The Enterprise Mobility Foundation
Want more than just blog posts? Login or Sign up for a free acount and get research, videos, slide decks and more! Join the online social network for Enterprise Mobility.

Understanding The Difference Between Mobile Device Management and Mobility Management

A couple of weeks ago, I shared with you my experience of participating in a TweetChat on the Consumerization of IT as a prelude to the CITE event in San Francisco in the beginning of March (4-6 to be precise).  Well, today we had another one of these sessions.  I was just telling someone that I thought it was a great style of “event.”  It’s real-time, brings people from all across the world together, and unbelievably interactive…and the kicker?  It’s 100% free.  You gotta love it.

The one thing that did come out of the 1st TweetChat was that I felt compelled to write a missive regarding the need to better understand The Difference Between The Consumerization of IT and BYOD.  It seems as if I feel compelled yet again to clear up some confusion that arose from today’s chat.  Today’s chat was all about tablets in the enterprise.  I expected the conversation to be focused primarily on the use of the devices in the workplace, as well as talk about the kinds of applications that people are using for their work on those shiny tablets (or should I say iPads). Instead, the conversation very quickly shifted to talking about securing the applications on those devices, with the added nuance around managing BYOD vs. COPE based tablets.

There were some very interesting comments during the session.  In fact, one of the members of the chat session made (in my opinion) a particularly astute comment:

The difference in security on a tablet vs another device is misleading it’s all about the data

I think he’s dead on.

The problem is that another member of the chat session made a comment eluding to the fact that the solution was to deploy a MDM solution and then another person added:

I would think MAM and MIM would be wrapped into MDM

Now you (hopefully) understand why I am writing today’s missive. So first of all, what the heck is MIM?  MIM stands for Mobile Information Management.  This is something I brought up about 18 months ago, but didn’t seem to catch on at the time.  Maybe the time is now.

In any case, today’s missive is to (yet again) help you all understand that Mobile Device Management is not the right term when you want to think about the totality of managing mobile implementations in the work place.  I don’t care if you’re talking about Consumerization of IT, BYOD or COPE, Individual Liable, Corporate Liable or whatever.

MDM is simply not the right term to use.  What you want to do is think instead about enterprise mobility management.  The Enterprise Mobility Foundation also has documents here and here that help you understand the distinction between MDM and EMM.

Now don’t get me wrong, MDM (as I have said countless times) is vital to the success of effectively managing mobility in the workplace (some will disagree with me), but MDM is about the DEVICE.  It’s NOT about the applications and it is certainly not about the data on the devices.

You want to manage the deployment of applications to your workforce?  Great.  That’s why you need a tool with Mobile Application Management capabilities. That’s why “MDM” vendors have been moving so quickly to add Mobile Application Management capabilities onto their solutions…but to call that MDM does us collectively a disservice as it only obfuscates the conversation (as evidenced today).

So back to MIM.  This is the future people.  We are all talking today about the “data.”  “The data is what’s important.”

Totally agreed.

That’s why I think that once we have properly tackled mobile application management (which I think will happen this year BTW from a technology perspective), I think the one last thing we’ll need to do is find a way to most effectively manage the data that is passing through these mobile devices.  This, I think, will be trickiest part of all, but could potentially put to rest all the issues around questioning how to manage corporate security and policy depending upon who owns the mobile device.

4 Comments

  1. Posted February 24, 2012 at 02:23 | Permalink

    Somebody needed to point out the distinction, thanks Philippe.

    I’m sure some people are indifferent, but a MDM provider that has incorporated app management features is definitely not a MAM solution. Meanwhile, I won’t deny that MDM features should be included in future developments in MIM and Enterprise Mobile Management (you didn’t really want me to add another acronym to this comment, did you?)

    I love the metaphor of MAM as a surgical knife. The scalpel is designed to cut as little as necessary, but it’s still a blade capable of bigger jobs if desired.

    MDM? The sledgehammer.

    - Walt

    Thumb up 1 Thumb down 0

  2. Posted February 24, 2012 at 08:31 | Permalink

    Thanks Walter. I’d love to hear more about how you make the distinction between “app management features” and a “MAM solution.” Could you elaborate please (for the community)?

    Thumb up 0 Thumb down 0

  3. Posted March 12, 2012 at 11:36 | Permalink

    What about mobile server and application management for the IT Dept.? How come no one is talking about that? It seems to me we are spending all our time helping out the employees, but who is thinking of the IT person being able to manage their apps and servers via their smart phones or tablets?

    Thumb up 0 Thumb down 0

    • Posted March 12, 2012 at 12:04 | Permalink

      Actually, there are a number of companies that provide tools for the IT admin to manage their own infrastructure (as well as trouble tickets) via mobile devices. Also – when you talk about application management, what types of applications are you referring to?

      Thumb up 0 Thumb down 0

Post a Comment

You must be logged in to post a comment.