Lately, I have spent the majority of my time with enterprise teams that are looking at mobile more holistically. While this is a welcome change, as I have been harping on the need for a focused mobile strategy for some time, the turn is incremental. Now there is a feeling that a mobile strategy needs to be developed, but the change has become – build the strategy around a vendor. This is not strategy. If you survey your organization, look at the competitive landscape. Then derive a set of features and capabilities that your organization would like to take advantage of. Then, you’ve got it half right.
The mobile sphere embodies more than just some smartphones, and when looked at from the perspective of what your company wants to provide to the market and to internal employees, the right set of requirements for technology selection begin to form. But this is not enough. You need expert advice from battle-hardened technologists who have put out applications successfully. That guidance will keep your app from falling into the “so what” category to a greater extent, than if you make a go of it on your own.
There is also a great need for creativity. Not just some goofy gimmick, but real, valuable, interesting capability, that brings through what the app is supposed to achieve. In my next installment, I’ll hit on some of the methods to get at these areas that can help you start further down the road than your competition.
Tags: Deep Dev, mobile projects, mobile strategy, Parmelee
I agree Ken. Mobility is something most organizations aren’t familiar with and having a partner that can provide the right set of tools and, perhaps more importantly, expertise in deployment and management is key to a successful enterprise mobility strategy.
Reply