Skip to Content

10 Steps to a Success Mobile Software Implementation

Once you determine there is justification for mobilizing your workforce, you will want to understand how to successfully implement an enterprise mobile solution.  Companies around the globe are looking for ways to do more with less. Many recognize that their mobile workforce is being managed inefficiently and extending business process automation to mobile field workers is becoming a priority. The following 10 steps identify how you can get started automating and mobilizing these business processes.


  1. Understand the ROI/Scope of the Project and Plan Ahead: “What are the most challenging parts of a mobile project?” The answers are that many companies don’t put enough upfront thought into defining the business and technical requirements, scheduling testing resources and planning a deployment and support strategy. The results of these deficiencies are project scope creep, cost overruns, missed deadlines and poor user acceptance rates. 
  2. Build a Team of Stakeholders: Ensure that the members of your team have the right roles and responsibilities to help the project succeed. Mobile solutions usually tie into other corporate IT assets and business processes, therefore impacted members of your IT department and business units need to be on the project team. In addition, a representative mobile field worker(s) should be included on the project team to provide valuable “real-world” insight.  
  3. Select a Partner That Specializes in Mobility Solutions: Performing successful data synchronization from mobile computing devices can be a challenging and complex task. There are many variables that can affect the results of synchronization. To ensure you get a mobile solution done correctly the first time, you need experienced experts in mobile technology. You need technologists who specialize in the design, development, deployment and support of enterprise mobile solutions. 
  4. Know Your Target Users and Their Environment: During the planning and scoping phase of your mobile project, take time to experience the working environment of your mobile workers and observe the business processes in action. Pay specific attention to how information is collected and exchanged between the office and the mobile workers. These observations can significantly impact the design, development and deployment of a successful project! Evaluate the physical environment of the work. How do moist, cold and dirty environments impact the mobile devices? How does low light or bright sunlight affect visibility of the screen? Can workers read the small text on the PDA screen, or does the text need to be larger?  Are they able to re-charge their batteries regularly, or do they need multiple batteries? 
  5. Don’t Underestimate the Complexity of Synchronizing Field Data: One of the biggest mistakes a project planner or IT department can make is to underestimate how complex data synchronization can be. Part of designing a solid and reliable mobile solution is to select robust synchronization middleware and to spend time designing and testing the data synchronization. Without the right middleware and design your end users could encounter issues such as extra long sync times (hours, not minutes), duplicate records, incomplete data, lost data and even database corruption. Every one of these issues will trickle down to your support department, so designing it right the first time is very important. 
  6. Build in Phases: Most successful projects involve a series of phased implementations. Each phase can be developed, tested and implemented in an orderly manner. Once a phase is deployed and proven, additional phases can be layered on top that include more features and added complexity. Remember, the more data requirements that you add the more data you must synchronize and the longer each synchronization session will take. Only synchronize data that your remote users require in the field. In addition, most mobile devices don’t have the same CPU power or memory as a PC/laptop, so be aware of how the performance of your solution will be affected by a smaller, lower powered device. 
  7. Evaluate Your Hardware and Connectivity Needs before the Purchase: The term “mobile devices” can have many different interpretations. Today, laptops, Tablet PC’s, UMPCs, PDAs and Smart phones are all identified with this term. When determining the best mobile device for your project you will want to consider screen size, data storage capacity, security, physical working environment, required hardware accessories such as barcode scanners, GPS, digital cameras, RFID, and the ability to upgrade the device with updated hardware and software components.
    How do you connect your mobile device to your enterprise database applications? You have many options including cradle, WiFi, satellite, Bluetooth, wireless, dial-up modems and satellite uplinks to name a few. The method(s) you choose will be affected by how often your mobile workers need to send/receive data. How much data will be transmitted and will they always have connectivity. Study each option, your working environment and consult your mobility partner to make the best selections. 
  8. Deploy to a Limited Focus Group, Evaluate, De-bug and Improve: Once you have completed version 1 of your mobile solution and you are ready to deploy in the real world, roll out your solution to a small group of trusted and motivated users. Define a specific period of time to evaluate the solution, document the results and identify any required changes and improvements. The result of this evaluation should be an improved mobile solution that is ready for wide deployment. 
  9. Set and Enforce Hardware and Security Policies – Mobile devices are small computers with the ability to store sensitive corporate data, communicate this data over the Internet and even catch viruses. You must clearly communicate how mobile devices are to be used and for what purpose. Establish and publish guidelines for using mobile devices.  
  10. Provide Full Support for Mobile Users
You must be Logged on to comment or reply to a post.
  • Hi Kevin,

    The article was definitely an intersting read.

    I am quite interested in understanding  the ‘variables that can affect the results of synchronization’

    Thanks a lot for the mature insight shared in the blog.

    Best Regards,

    • -How do you resolve data conflicts during synchronization (i.e. when 2 field service workers synchronize edited information on the same client at the same time.  What data is accepted and what data is not?)?

      -How do you support 300 synchronizations of a new product catalog at 8 AM in the morning?  Do you have the capacity and IT environment in place to support large synchronizations the first thing in the morning?

      -Some mobile work locations have the ability to hire temporary workers in the field.  They enter the employee information on the handheld in the morning, utilize the worker for 8 hours, and end the employment.  This all gets uploaded perhaps in batch at the end of the day.  Can you hire, pay, and fire an employee all in the same synchronization with the corporate ERP?

      -What happens if you sell product on your mobile handheld product catalog, but it is no longer available in inventory or on the corporate price list?  How is the mobile worker informed of these issues?

      ***These issues are very often a result of timing.  The mobile worker is often disconnected.  How do you handle issues that arise from working in a connected/disconnected work environment?