In the Enterprise we tend to over-complicate even the simplest of things. A simple process becomes convoluted, onerous and even unmanageable once the enterprise bureaucracy takes over.
Let me give you three simple steps to guide your efforts towards building a strawman mobile strategy. Please note this is at the simplest level and there is much detail within each step… but for now this a good starting point:
- Business Alignment: Your mobile strategy should exist to enable (ie. help out) you larger corporate strategy. As such, your mobile strategy needs to be developed within the context of your enterprise vision and overall business objectives.
- Use Case Development: The first step to help you identify key areas where mobility could be most impactful. For example, if your business objectives include lowering costs through your supply chain then you will look at use cases in that area which you can explore and develop further. Spend the time understanding the users, their needs and the high level value of these use cases.
- Prioritize Based on Value and Impact: Once you have identified 5 – 10 – 15 use cases go ahead and prioritize them on their value, impact to the organization and implementation feasibility (technical and budgetary). This is step where you dig deeper on the value and costs of each use case since at some point after the use case you will have to get the money to do it.
What is missing here?
You probably noticed technology is barely mentioned here. I believe it is important (especially working for the company I work for)… however, technology should not drive this initiative. Instead, it should be part of the entire process as appropriate. For example, you don’t want to finish the exercise and realize you need to retrace your steps to determine the impacts of technology (architecture, systems, etc).
They go together… but technology does not drive the discussion (it informs it).
Remember this is about value and business outcomes! That is what mobility is all about.
