The key mistake most organizations make with employees that bring smartphones and tablets to work is not weighing the risks and not exploring the business opportunities.
This is the third post in a three-part series on a Bring Your Own Device (BYOD) program, the challenges and solutions. Last week’s post talked about the strategies that can help IT meet the varied employee demands while reducing the risks to security. Today’s post addresses the solution, best practices and exploring outsourcing of mobility IT.
Now we understand the challenge.
With employees and customers increasingly tied to their own smartphones and tablets, companies are left with little choice other than to embrace the bring-your-own-device, or BYOD, trend in modern business.
The question is how to do so while not risking unnecessary security lapses?
The answer from Part Two is establishing a mobility committee comprising as broad a base of stakeholders and players as possible to get a buy-in across the organization.
You need legal representation, HR and regulatory compliance. IT are collaborators, they are there to assist. But just because they know the technology, they can’t go out and implement the program, says Brian Patterson, a consultant with TELUS Managed Mobility Services (MMS), powered by Vox Mobile.
He also told a March 6 session on enterprise mobile programs at the BlackBerry Innovation Forum that others involved in application development also need to be in the room.
If people in application development don’t participate, you will get roadblocks down the road, Patterson warned.
Alternatively, if a company has huge marketing and sales teams, top-level representatives for those divisions need to be on the mobility committee, not least for corporate consensus.
It’s no different than anything you want to implement in an organization. If you get a large committee together, not everyone will agree. So our policy is to disagree, make a decision and move on, Patterson recommended.
Best Practices
Once the mobility committee is formed, the next step with TELUS MMS as a mobility consultant, is taking its members through a menu of over 150 possible best-practice policies to consider, from end-user behavior to data security and business costs.
The committee will also be encouraged to weigh the opportunities and risks of a mobility program.
Patterson points to a Power Company he recently met with that insisted that, no matter what, it needed to stay in contact with its employees for disaster response should its electricity grid go down. When their power goes out, and there’s a flood, people can die. Lives are at stake, he explained.
An organization also needs to set its costs for a mobility program, establishing whether the company will pay for a second or third device for this or that employee or executive, and who is liable to pay for extra charges like connection fees. The committee will also be asked to drill down on mobility costs to set a baseline on which to measure possible cost savings.
There are mobility hardware costs to consider, as are the costs of buying and deploying devices. There’s also technical support and monthly carrier service costs.
Considering Outsourced Mobility IT
Add to those the cost of a mobility device management (MDM) license should the organization decide after an initial audit to out-source its mobility program.
We capture all mobility costs, based on an organization’s strategic objectives, by measuring current costs and giving options, Patterson said of establishing who buys what hardware, who pays for bandwidth and when, who fixes what and who solves device and service problems.
TELUS and partner Vox Mobile, an end-to-end managed mobility services provider, will also advise a company on how to off-load or deflect costs within an organization, not least by charging certain employees to connect their devices. It’s amazing how many people will pay to connect their devices. They just want to be connected, Patterson insisted.
Then there’s the ever-present voice and data security challenges to master as a company embraces a BYOD mobility policy.
Patterson points to an unnamed manufacturer he advised that had a new product line coming out with enhancements. A month before the product release, a competitor had the same offering on the market, with the same enhancements.
An investigation showed an engineer left the company a month earlier. So they locked everything down and no one could get anything done in the organization, he recalled.
TELUS MMS Advise
Introducing a successful enterprise mobility program also calls for determining whether to do so in-house with an existing IT department, or out-source to TELUS and Vox Mobile or rival managed mobility services offerings.
Helping a company put together their mobility program is what Telus MMS Advise is about. We come in, help you build a program, help you develop your policies, help you develop your segmentation of users, then help you develop the business case, Patterson explained.
Once we accomplish that, we can take on and manage your mobility program. So if you want to out-source your support or server management, you pay us a bill, and we manage your fleet for you, he added.
Deciding whether to out-source will be a big decision for your mobility committee.
As a business, you have to look at what makes sense. Should you continue to pay six or eight people to manage your mobility fleet and that costs me $500,000 in G&A costs, or can I out-source it for $100,000. That’s real money, Patterson argued.
At the end of the day, out-sourcing is really about a company sticking to what it does best, while bolstering cost savings and business competitiveness by modernizing its mobility program.
Do you want to be a mobility shop, or do you want to focus on your core competency to advance your business? Sometimes that’s a difficult discussion to have, Patterson said.
Etan Vlessing is a Toronto-based business writer.
Related posts:
Part 1: Your mobile IT policy: Its not just a document. How to kick start your BYOD program.
Part 2: Many Employees, Many Wants of mobility. Why your IT department shouldn’t despair
What challenges has your organization faced in implementing a BYOD program? Share your comments below.