I realized that mobility conversation should not always be about the usual concepts such as platform support, cross-platform deployment, application store, device capabilities and so on. I think we should take this conversation from a client i.e. device specific discussion to a more strategic and core infrastructure discussion, because Mobile applications are not created in a vacuum. Let me explain:
1. Consider Mobile not simply another set of devices for IT to manage with a “fit to screen” application…but many of our clients should see it as a new model for engagement.
2. Many industries especially Retail, Insurance and health care are manically focused on Mobilizing not just their application but also their ‘engagement’ with partners, clients, employees etc.
3. So this just cannot be as simple as positioning a tool, a consulting services or a platform to solve that problem, it has to be more than that. We have to think about the ‘Unintended Consequences’ of this new system of engagement. These the ‘Unintended Consequences’ include but are not limited to:
a. Multichannel approach – How do now manager infrastructure/data/analytics etc. from this channel and put it in right context?
b. Middleware infrastructure, security infrastructure, network infrastructure – Can my current model handle and suited for new set of requirements. Security is big here, more on this later.
c. Exponential growth in request/response Volume and Transactions – We at IBM understand this better than anyone; after all we have been solving this problem over 3 decades or more. But this time is the volume bigger than ever before… I think so!
d. My overall design, development and other system management processes --- How do I incorporate the system management components of these new system that I will need to bring on line monitor/manage them and ensure that is included a robust design to handle and grow linearly.
e. And so on…
My point is we cannot attack the issues with just with MEAP/MADP tools. I also think that there are times when we get engaged in “feature fights” instead of focusing on larger strategic issues.
I also think that Industry specific knowledge may be vital in understanding our core issues and addressing solutions. Let me explain with an example, - Mobile Payment for example has been in news lately. Mobile Payments is an interesting area, as it impacts commerce that very life line of that “Moment of Engagement” that we speak of.
Allow me to paint a picture:
1. One Billion consumers will have a smart Phone by 2016 ( source: Forrester Research). US alone will have 257 million smartphones and 126 million tablets --- think of these many POS ( point of sale) systems
2. Retailers, entertainment, infotainment, Travel industry and many more want that piece of action and real estate of the smart device.
3. These transactions need to be fast, secure, and with minimal or no FCIs – failed customer interactions.
4. The Industry also wants it to be cost effective by not paying the various intermediaries such as PayPal, Google wallets, Apple Passbook (soon to come), and more.. PLUS the cost of payment transactions charged by Visa/MasterCard of the world. Many industries are looking to form a consortium to address this cost. The trend is started by ‘Retail Industry” they have recently form “MCX”(you should Google it!) A consortium to deal with just billions of dollar in commissions and fees. If this takes off then I would imagine airlines. Entertainment etc. may want to embark on either same journey or consortium.
5. The last “2 feet” problem – which is the interaction/speed between the device and end user.
I think – we should focus on strategic imperatives and not spend time in focusing on features because. Besides features in mobile space is very volatile.
From project perspective : We need to all understand features such as security, scalability and mobile application design imperatives. Because I can address the problem with a solution not with a feature. For instance I can discuss on device encryption, application authenticity testing, federated security policy integration for Security. We can device a strategy to ensure that we separate the application logic with integration logic and application push during install rather than “over the air’ transfer, speed up the response lookup with multi-tier caching.. And so on. All to address the Unintended Consequences’ we discussed earlier.
Strategically: We should shift our old school thoughts from “Moment of Truth” ( if you remember the SAS use case) and focus on “Moment of Engagement”
Tactically : We should shift from “feature fight” to a addressing a solution for “Unintended Consequences” problem.
Thoughts?
:)
Nitin
No comments:
Post a Comment