Creating an Enterprise Mobile Strategy: Culture & Roadmap

In an earlier post, we talked about what enterprise mobile strategies with real ROI looked like. We also gave you questions to help you figure out if an app project aligns with your overall business objectives. In addition, we touched on the subject of security and the implementation of enterprise mobile strategies. In this blog post, we will discuss the roadmap that an organization can take when starting the process of considering an enterprise wide mobile strategy.


To start the process of considering an enterprise wide mobile strategy, you need to consider two important things:

1) The Company Culture: Depending on your company's culture, implementing an enterprise wide mobile strategy will vary. Remember: You don't want to change a company’s culture too soon. If your company has an internal IT department, it is important to involve these people in the enterprise mobile strategy. Their input will help with the overall success of a mobile strategy. In other companies, IT projects are outsourced completely. You'll need to work with the outsourced company to ensure that both parties understand what the vision is for the mobile solution. There are also companies that have a mixed model where they have a small IT department and work with outside companies as well. It is very important to figure out the company culture before considering an enterprise wide mobile strategy.

2) Your Goals: What are your immediate and long term goals? Some companies want quick wins. At ChaiOne, we find that it is best to align with a company’s immediate needs so we can align with their processes.


Milestones are an important part of implementing a mobile strategy. It's crucial to understand that you'll need to go through various phases to get to a great mobile ecosystem. These milestones will help keep the project on track and your company focused on your goals.

1) First Year: During the first year of a mobile strategy, you have to think of the Minimum Viable Product or MVP. A minimum viable product helps you get a mobile app out quickly and then continue to improve it through iterations. When you get software builds of the app, you need to use it and give feedback so that the developers can fix any problems and add additional features that will enhance the user experience. Your organization will feel more engaged in the transformation process when everyone feels that their feedback is being heard. To add to that, it is important to have a mechanism to allow for the collection of feedback from users. The most important thing to remember is: There is no point in putting out an app when no one wants to use it.

2) After the first year: After the first year or two, your company should focus on apps that are more transactional. Transactional apps will change more of your processes and you'll see the additional possibilities of mobile solutions. Once you're able to see these opportunities, you'll be ready for the next major milestone.

3) The World is Mobile: In this milestone, your company will understand that the world is detaching from the desktop. You'll be able to change core business processes with mobile solutions in order to enhance efficiency and increase ROI. The more you can mobilize your processes and technologies, the higher chance your organization will be successful for the future.

Important Thing to Consider: Company Culture and Change

People are inherently afraid of change. All corporations need to have a good internal communication program with its employees. They need to tell employees the benefits of mobility and the successes that come from implementing enterprise mobile strategies. It will encourage executives to give the program a chance, and will help win over skeptics. Overall, you need to move under a single organizational strategy and not under various strategies for individual business lines or departments. This can be done by implementing a mobile center of excellence to help your organization create a unified mobile strategy.


When the Apple store launched, people formed an opinion that mobile apps weren’t like traditional web projects. Most of the apps featured were games that cost 99 cents. People thought that it only took a couple of weeks to whip out an app. On the contrary, a mobile app is no different in scope or design than a complex SAP implementation. It can be very complex especially when you consider the user experience. People expect apps to be native and intuitive. One of the biggest challenges for organizations is realizing that there isn’t a difference between apps and traditional web projects. People must realize that creating the user experience takes a lot of time and research. This includes designers going out in the field to uncover efficiencies by observing your employees' work processes. For successful mobile apps, you need to engage in the user experience and user research. Happy users are the ultimate measure of user research’s importance.

Hopefully, you now understand the things to consider before implementing an enterprise mobile strategy. Your roadmap should help guide you through the process. Remember to consider the company culture and misconceptions before implementing enterprise mobile strategies. If you want to refresh yourself on the benefits of mobile solutions, read our blog post on creating an enterprise mobile strategy with real ROI.


Voice of the Customer cta button version 2

Subscribe to
our Newsletter!

Keep up with new insights from industry leaders on digital transformation, mobile app development, enterprise architecture, and tech innovation topics.