Nowadays, more and more companies are implementing BYOD among its employees, which let them use their personal phones and laptops for work. It’s an alternative strategy allowing employees, business partners, and other users to utilize a personally selected and purchased client device to execute enterprise applications and access data. Typically, it spans smartphones and tablets, but the strategy may also be used for PCs.

Here are some mistakes you must avoid as you consider how to implement your own BYOD program.

Resisting BYOD

It may seem obvious in a list of BYOD mistakes, but resisting BYOD is becoming increasingly indefensible policy. As computing devices have grown to be more personal, trying to dictate device usage to employees is similar to telling them what brand color and color pens they’re allowed to use.

Not supporting common devices

It’s tempting to support only a limited selection of BYOD devices, or only one brand or operating system; however, providing more choices rather than fewer is key to successful BYOD. In general, the tradeoff for BYOD is that users are providing their own hardware and software support, so limiting device selection generally does little to change your support requirements. Similarly, it makes sense to support common form factors. BYOD should be about more than employee-owned phones, and once you have the structures and policies in place for one device type, it’s generally easy to extend that support to BYOD smartphones, tablets, and laptops.

Going “NSA”

Devices contain everything from work-related emails to intimate photos. Just because a management toolset allows you to access and monitor everything on an employee’s personal device does not mean you should do so. Furthermore, it’s important to ensure that access to monitoring tools is tightly controlled. It’s respectful of your employees’ privacy and also a good measure to prevent legal troubles should IT be found missing these tools.

Not facilitating self-support help groups

Since BYOD programs often attract tech-savvy early adopters, help facilitate these pioneers by providing self-support tools. Many companies create intranet pages or publishing mechanisms, so users of a particular platform can publish tips on how to set up these devices to access corporate services. For little more than a few pages on your intranet, you can make your employees your first line of BYOD support.

Instituting a “we don’t support that” help desk

A major frustration of BYOD users is calling support for an application problem and being told “we can’t support you” since they’re on a BYOD device. BYOD should not be a license for your help desk to end a call immediately upon discovering an employee is on a personal device. Rather, initial troubleshooting should seek to identify if the problem is related to the device or a corporate application or service.

Not matching security to risk

Although there are certainly security risks to allowing employee devices to access company services, you must take care to match the security requirements to those risks. If you demand that employees install a half-dozen security applications that slow their laptop to a crawl, or mandate a 15-character alphanumeric password and 30-second timeout on their phones, you’ll tilt the balance too far. Remember that the ultimate goal of BYOD is to make employees more productive and effective by allowing them to use their preferred devices. Putting unreasonable security requirements in place where there is little sensitive data at risk is generally going too far.

Tags: ,

This entry was posted by Staff Writer on Saturday, August 6, 2016 at 6:24:33 AM and is filed under Small-Medium Business.

Leave a Response