Humanitarian agencies should allow enumerators to use the data collection devices we give them for their own personal uses, not just for work purposes. (Yes, including their own pictures, personal chats, emails, and downloading apps). Agree? Or do you think restrictive mobile device management is the way to go?
Today, I read the article “Can Mobile Device Management Improve the Data Collection Processes?” over at ICTWorks (go check it out after you read this article!) It made the case for developing a mobile device management tool that would allow:
- Data utilization management
- Application blacklisting
- Location tracking
- Group notifications
- Remote lock/unlock/wiping of devices
At first glance, this looks like a great solution. It helps smartphones not run out of storage space or power too quickly.
There is a time and a place for every different management style. And for some, using mobile device management might be the right solution.
However, I also want to give a different perspective that aid workers should consider before rushing in to control and restrict smartphone usage. I just don’t want everyone to think that device management is “the only right way”. There are very good reasons for NOT using device management as well…
First, allowing data collectors to use their smartphone for personal reasons means they’ll take care of it a little better.
When you give someone enough ownership over a piece of equipment that they treat it as their own, my experience is that they keep those devices charged, they keep them on hand at all times, and they stay in constant communication with you.
Second, if you allow your volunteers and staff to use the smart device for “personal stuff”, you can use it as an incentive.
When we mobilize hundreds of people at a time to collect data, we’re not only mobilizing employees. We’re also mobilizing volunteers – community health volunteers, community hygiene promoters, etc. It’s possible that they will provide even more value back to you through the data collection project if they see that you’re allowing them personal value out of the phone. In some cases, what if you just give away smartphones to these volunteers after you finish your data collection project? It doesn’t always make sense, depending on the life of the project and the life of the phones. But it’s an idea to consider in lieu of salary costs, or as a way to maintain a massive network of future enumerators in case of emergency.
Third, it may be safer if a data collection app, such as ODK Collect or Kobo Collect, is only ONE of the apps on the phone in case that phone is confiscated in a sensitive operating area.
If you allow the enumerator to use the phone as a personal device, it could end up relieving suspicions and avoiding interrogations.
Fourth, while it makes sense for managers to want to track the location of all their devices, does it infringe on personal space?
I can understand using location tracking if the devices are only taken out of the office during work hours. But do your enumerators take the devices home at night? If so, there should probably be boundaries on when location tracking can be used. The employee should have a right during non-business hours to not have their location tracked.
Fifth, does mobile device management restrict personalisation and innovation by individuals?
If application downloads are blacklisted, does that mean that no one in your field team will be able to differentiate themselves by finding new creative tools with which to carry out their work? It’s like restricting Facebook at work – yes, Facebook CAN be a way to waste time at work. However you can just as easily use it to connect with other professionals, network, and innovate together. I would prefer to create a culture of innovation and trust rather than restricting access to anything I have not pre-approved.
In conclusion:
Regardless, I see all the pros of mobile device management tools as well. So I believe that in some contexts, using mobile device management is the way to go. However, it’s not always the right solution.
Before you make a decision, you need to weigh the benefits against the cons. Do you want to restrict and control device usage because of the mismanagement of the device by a couple of people? Don’t punish the masses because of a couple of outliers.
Probably the most important criterion to consider when deciding whether or not to implement MDM is whether the device contains identifiable client data. If this is the case, then protecting this data via encryption and strong password policies is essential, and MDM is one of the most effective ways of ensuring this happens. (I can’t count the number users I’ve come across who use their phone number as a password, or who use a ‘Z’ swipe pattern…)
Even then, however, there is no need to completely lock down the device, and I agree that many of the suggestions made above – allowing personal use of the device, letting users explore new tools and apps which could help their work – should be considered when configuring your MDM policies.
Samuel, thank you so much for adding this point. You’re absolutely right. I’d say we have two priorities when making a decision on how to manage our devices. One is staff safety. The second is protecting whatever personal and sensitive data is on that device.
We should be sticklers for data protection, even if we give freedom with device usage. Even when not using an MDM tool, devices should be encrypted, protected with a password (and set by the organization to ensure strength), and I also believe the data itself should be encrypted and inaccessible on the phone. Because it doesn’t take much for someone to force you to enter your password so they can have access to the device themselves.
Thanks again!
Janna