This morning I visited with a significantly larger enterprise client that has divisions that provide services in mining, oil and gas exploration, environmental impact studies, building engineering, water conservation and more. In our conversation he commented, "My biggest challenge is that we have come to realize we all have all these disparate mobile solutions that service individual business silos, but can not interact with each other. Each division is running their own mobile strategy. Some have mobile apps, some are still on spread sheets, others have no mobile solution but considering and I just learned we currently have two MEAP solutions running. And we haven't even discussed the mobile device issues. While we are all benefiting individually, it's a mobility mess."
In my experience companies who have rolled out mobile solutions have deployed them in an opportunistic fashion. Typically a field manager has caught the mobile vision early. Through his ingenuity, tenacity and budget maneuvering has implemented a mobile solution specific to his group. The positive impact of his mobile solution inevitably catches the eye and envy of other departments who eagerly clamor to adopt mobile solutions.
While this approach provides a strong, quantifiable internal use case for mobile solutions it often leads to a reevaluation of the first mobile solution. Especially, if the first mobile implementation only addressed a specific business need, was limited in scope, didn't plan for the broader needs of the company and was not scalable.
Developing a strategic plan is critical for the on-going adoption of enterprise mobile solution. The key is understanding "
why you are going mobile". Evaluate what you trying to accomplish from an enterprise level all the way down to the individual level. Then develop a strategy that addresses this across the enterprise. Companies need to focus on the following key areas
- Identify key business processes that will benefit from mobilization.
- Determine how individual mobile projects integrate with a central mobile management, backend databases and security infrastructure?
- Establish security policies for data accessibility, network accessibility, application distribution, device management, BYOD policies, etc.
- Identify supported mobile devices; SmartPhone, TabletsPCs, Rugged devices
- What supporting hardware is needed? Mobile Printing, GPS, RFID, etc.
- Determine if mobile apps will be available on different mobile form factors; SmartPhone, TabletPCs, Rugged devices, etc.
- Identify mobile user roles. User will roles determine data accessibility, security rules, appropriate device options.
- Determine if mobile roles are transactional, informational or collaborative
- Identify if mobile business processes and user roles are B2B, Internally driven or B2c
- How many mobile users are targeted?
- How will deployment and support of mobile users scale over-time?
- What mobile architecture do you need to have in place?
- How will mobile apps be developed, deployed and managed? Who will oversee this?
- What types of apps will be supported? Custom-built, off-the shelf, modified mobile app templates, HTML5 mobile apps
- Determine how success will be measured
Yes enterprise mobility brings new challenges and opportunities. Investing the time to conduct a full enterprise mobility assessment and developing the appropriate strategic mobility plan is critical for long-term sustainability and scalability of mobile solutions in the enterprise.
Like my client said, "We've been dabbling in mobility long enough. It's time to get serious and unify our mobile strategy and get out of this mobility mess."
