Enterprise Mobile Project Gone Wrong Who You Gonna Call ?
We get to speak to a wide variety of organizations some of whom have already tried unsuccessfully to deploy an Enterprise Mobility project.
Reasons can be complex and certainly in some situations management buy in and adequate funding can be issues.
However on too many projects the Return on Investment ROI calculations go straight out of the window just as the initiative gets difficult. Enterprise mobile project gone wrong ? Here are 5 common problems that we have encountered that may help to explain why this happens.
5 Common Problems
- Endless Development - It is very easy especially if you engage an “expert” coding house to end up with an endless cycle of software development. For instance lots of companies who think they are expert in HTML 5 know nothing about using mobile devices in mission critical projects security or host integration. Key question; have they done this before? if not it can get very costly, complex and time consuming. The resulting app can become technically outdated be difficult to change maintain and upgrade. As this process rolls on hardware is often still sitting in a corner collecting dust.
- Difficult to use Development Environments – There are some well marketed “mobile application development environments” out there all claim to be easy to use. The problem is enterprise mobility can get messy. At the very least it needs to map your field based process as well as be reliable and sustainable once deployed. Making some of these environments actually come up with the app you need on the device you want can lead to lots of tinkering which means more budget burnt on professional services.
- Lack of Product Documentation – This is something that most people don’t think about until its too late. All of the organizations with failed implementations that we have spoken to this year said that the lack of product documentation how to’s, frequently asked questions, installer guides, etc rendered the already difficult to use development environment or custom cut code useless. All leading to increased time spent and cost incurred when the app should be deployed addressing the business problem that prompted the project in the first place. Key question; look at the user guides a vendor has put together for other customers – can you understand the material?
- Hidden Costs – one customer told me he thought that the provider he chose to custom develop his application was going to be the perfect fit affordable, solid, great product vision and support. However, when he needed to make a very simple change to his application he was charged with 40 hours of development time. Key question; ask up front and get the vendor to show you, how easy is it to amend an app and re-deploy it in the field and what is the cost.
- “We bought an off the shelf app” – Key question; Great! but does it match your business process or does it offer a transformational way of doing what you might already be doing with pen and paper at the moment? If not be ready to experience the traditional square peg round hole approach where the app can be expensive and inflexible or where the customisation needed to map your processes is eye wateringly expensive.
If any of the above describes your enterprise mobile project gone wrong I have good news….. MobileWorxs can help! Think of our mobile enterprise application platform environment as a means to an end. It has a bunch of great features that allow us or our customers to build great enterprise grade apps that will run on .NET Android or iOS and are solid and sustainable. We have experience in a wide variety of application areas such as field service management and facilities management so can help automate and enhance the process workflow of your mobile workers.
Challenge us, we will build your application and demo it to you live on our very first phone call.
Andrew has worked on some of the largest Enterprise Mobility projects in the UK Eastern Europe the Middle East and Africa. He has user and project experience in helping companies think through and develop mobile strategies to get the most out of a deployment.