At glance, corporate-owned mobile devices appear to be easier to manage than employee-owned devices, as the boundaries...
are clearer, but IT still has a lot to keep track .
Organizations must decide on a mobile device budget and corporate policies, among other responsibilities. After that's all said and done, organizations must make sure that employees use corporate-owned devices properly and efficiently.
Here are some ways for IT to take control a corporate mobile device strategy and ensure that the benefits using mobile devices outweigh the risks.
Consider mobile device cost
One the steps when introducing a corporate mobile device strategy is determining the cost. This is a more complicated process than simply adding up the cost each device and employee data .
Organizations with BYOD have some flexibility when choosing what they will pay for, but corporate-owned and personally-enabled (COPE) plans are more strict. COPE programs should cover the cost both the data and the device. Data plans typically run between $50 to $75 per user, per month, but these costs decrease once the organization pays off the cost of the device.
There are other cost factors to consider, as well. Organizations should account for enterprise mobility management (EMM) platforms, the cost of which can vary depending on the vendor and whether they are on-premises or cloud-based. Cloud-based EMM is typically less expensive, but it has less room for customization.
Organizations must also consider additional tools such as identity and authentication products, which can bring the cost of mobile devices to more than $2,000 per employee annually.
Create a mobile app policy
Once an organization deploys corporate-owned mobile devices, it's important to establish a policy on acceptable mobile apps. Whether that policy is strict -- employees can only use these five work-approved apps -- or lenient -- employees can use whichever apps they want – it's important for IT to at least get on the same page. Many mobile apps, such as WhatsApp, can security risks and leak corporate data.
Organizations with stricter policies should consider creating a whitelist, which is a list authorized apps that employees can use. These organizations should also constantly review and update a blacklist to maintain a higher level security, as extensive blacklists can quickly get out control.
The ideal scenario is for organizations to use a mix blacklists and whitelists in their corporate mobile device strategy. In departments with productivity concerns, organizations should use a blacklist. For departments that deal with sensitive data -- such as legal or financial information -- organizations should use whitelists to enhance security.
Get the data
IT can collect data from corporate-owned devices to gain deeper insight into the organization itself. For example, IT can benefit on the security side from alerts for predictive maintenance about sensors or network logs.
With mobile device analytics, organizations can help employees use devices more effectively. Analytics can point to wasted data usage or decreased battery performance, for example, and IT can delve into why these issues occurred and how to prevent them in the future.
Analytics can also help IT determine where mobile apps succeed and fail. IT can obtain user acquisition data and retention rates a mobile app to work with the product and development teams and improve the user experience. With analytics, IT can see how end users interact with their mobile devices and use that information to improve their overall productivity.
Don't wait for device death
Mobile devices are far from immortal, so it's important to determine the lifespans devices and replace them appropriately. IT should do this proactively rather than implementing a don't replace it until it's broken strategy.
Organizations that don't heed this advice can experience a significant drop in productivity and profitability. Smartphones at the end of their lifespans experience a 15-20% drop in efficiency when accessing apps, for example. Mobile devices can reach the end of their lifespans relatively quickly; a two-year-old smartphone will have 30-50% battery performance degradation. In addition, some older smartphones are not equipped with the necessary security features to protect end users' privacy.
To be safe, organizations should generally replace corporate-owned mobile devices every 12-18 months. It's preferable for most organizations to purchase a model rather than sink significant costs into repairing a smartphone.