Originally published: Mar 14, 2012
Mobile is huge in the consumer space, and it's starting to have a big impact within organizations. Very rapidly, senior management are demanding iPhones and iPads, and trends such as BYOD ('bring your own device') are raising questions about the line between corporate and home tools.
While there has been quite a lot said about mobile enterprises, and how to deliver them, this has often fallen into the trap of 'hand waving' discussions that cover the topic at a very high level.
The reality is that there are many different aspects to enterprise mobility, which need to be delivered and supported in distinct ways. To aid with planning and delivery, it's helpful to distinguish four types of enterprise mobility:
Each of these requires different technology solutions, design approaches, and management models.
This is the most basic aspect of enterprise mobility, allowing staff to access key services such as:
These capabilities have been available for some time on Blackberry devices (which is their main selling point), and should be extended to other devices.
This is fundamentally an IT infrastructure task, taking steps to open up access to mobile devices in a secure way. All device manufacturers are rushing to make this easier from their end, hoping to capture a slice of the lucrative enterprise market.
This is the primary focus of discussions about enterprise mobility, exploring how knowledge workers can be given better work tools on mobile devices.
This can mean many things:
The best starting point is often to identify a few key tasks that can be delivered in a simple way on mobiles, and then expand from there.
It has often been overlooked that mobile functionality has been alive and well in field environments for over a decade. Often delivered to tough tablets or 'ruggedized' mobiles, this provides frontline and field workers with key tools to support their day-to-day work.
These solutions are very different from the mobile productivity tools currently being explored for knowledge workers. They are often single purpose applications that provide forms and applications with off-line synchronization that eliminates the need for always-on mobile connectivity.
The final category includes tablets such as the iPad, where staff (often executives) use these lightweight devices as replacements for desktops or laptops.
In contrast to the other categories, these devices provide simplified versions of desktop tools, alongside larger-screen versions of mobile functionality. These are also used in sales environments, and as point-of-sales tools.
Differentiating between types of enterprise mobility forms the foundation for a concrete plan of attack. It helps with answering fundamental questions such as:
These are just a few of the questions that must be answered, to ensure success. Here's quite a few more to kick-start internal thinking and discussions:
Who and what:
This may be a daunting list of questions for organizations to address. Many issues may be hard to resolve in the early days of enterprise mobile adoption.
The good news is that early steps can be taken to deliver simple functionality that still provides clear business benefits. Further capabilities can then be added over time, as experience and expertise grows.
In other words: start simple, but have a plan for strategic growth!
We're lucky to have James participate in two different UIE events. On April 4, James presents, Bringing Order to Your Intranet, a 90-minute online seminar. He'll also be conducting a full-day workshop, Mobile Design for Enterprise Intranets, at the UX Immersion conference on April 25.
Do you have experience tackling mobile intranet design? Let us know at the UIE Brain Sparks blog.
Read related articles: