An App Isn't A Mobile Strategy - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

10:57 AM
Maribel Lopez
Maribel Lopez
Connect Directly

An App Isn't A Mobile Strategy

You might only need part of an app, or just one piece of data, on a mobile device to make a process better.

A company's mobile strategy won't be successful if it starts by saying, "We need to mobilize our apps," or asking "What devices should the company support?" All too frequently, this is where the conversation starts.

The success of the iPad has increased the urgency to deliver mobile apps in the enterprise even more than when companies were simply delivering to smartphones. However, developing mobile apps isn't a strategy, and IT will be buried if it takes an "app at a time" approach to the demand for mobility. A successful mobile strategy requires companies to evaluate what business processes are working, what needs to be changed, and how mobile can improve how the business runs and executes its strategy. The move to mobility provides an opportunity for IT to redesign company processes and applications.

There are at least three areas firms should consider when building a mobile strategy.

First, IT needs to mobilize a process or a part of a process, and not necessarily an application. A process could be executed entirely within one application, or it could rely on data within multiple applications. For example, a sales person may need a mobile app that shows data from a CRM systems as well as an order tracking system. If the data resides in multiple applications, it's likely better to build a composite mobile application.

[ Tablets can be a game-changer for IT managers. Read iPad's Success Demands IT Change Its Thinking. ]

Second, if IT decides to make an application available in a mobile environment, what parts of that application should be mobile? A business will fail if it tries to recreate the PC experience on a mobile device. The screen size is smaller, the menu-driven navigation of the PC doesn't exist in mobile apps, and mobile offers different navigation options such as touch and voice. Successful mobile apps offer a subset of the functionality found in a desktop application. It could be that an executive wants mobile ERP, but it's unlikely. It's more likely that an executive wants to accomplish some task that takes a small piece of ERP, like approving a purchase.

Third, not all apps should be mobilized. Many apps are too complex for mobile use, and IT needs to consider what would be valuable to have "on the go." The mobile push is also a chance to define just how many people actually use a process or app, and perhaps consolidate some. Replacing paper forms with electronic forms is often an easy call. In some cases, the most successful early deployments haven't been apps at all but are data--such as price books, brochures, and presentations--that have been made accessible through mobile platforms. United Airlines uses iPads to replace a briefcase of maps. Mobile dashboards are also a big hit with the executive crowd.

Where should you begin? The business has to define a core set of processes and data that are required to run the firm. IT can then look for ways that mobile can benefit these apps. A business must understand how its employees want to interact with the company. What data makes sense to access to on a device? Remember, an app doesn't have to look or act like a consumer app, and it can have very focused, limited functionality. An app can enable a single process such as an expense approval, call for a piece of data such as inventory, or deliver a subset of an entire app such as ERP.

Processes that benefit from location, communications, and real-time data capture are a logical starting point when prioritizing potential mobile projects that could provide a big benefit. Consider, as always, areas where mobile can improve revenue or cash flow. For example, it makes sense to mobile-enable apps and data that improve billing cycles, increase inventory turns, and accelerate sales. The business should also look for areas where employees can gain insight with real-time data delivered to and from the field. For example, supply chain data and CRM data can arm sales and service people with valuable information.

With the right strategy, IT will be able to deliver a portfolio of the right quick hit mobile apps that demonstrate business value.

The Enterprise Connect conference program covers the full range of platforms, services, and applications that comprise modern communications and collaboration systems. It happens March 26-29 in Orlando, Fla. Find out more.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
2/22/2012 | 3:55:46 PM
re: An App Isn't A Mobile Strategy
It's refreshing to see someone sober mobile enthusiasm with a dose of realism. I couldn't agree more with the sentiment expressed here.

One of my biggest pet peeves is when a company defies reason and makes an app that simply is too complicated for mobile available on mobile platforms. The poor execution such endeavors typically have literally chases me away from that app. It would be encouraging if more companies out there spent more time considering a mobile strategy and invested more in conceiving the scope of their mobile strategy.
User Rank: Apprentice
2/22/2012 | 3:00:30 PM
re: An App Isn't A Mobile Strategy

Thank you for putting it so plainly. These heady days of Mobile remind me of the early days of the web, when companies scrambled to "just get something up there" without giving any thought to what would be most useful and beneficial from a business or customer standpoint. A whole new crop of decision makers (and some of the same old ones) appear to be making the same mistakes with mobile. Getting an app and posting it on the app store does not necessarily mean customers or employees will use it. You first need to do some homework, and too many companies, I fear, are racing to get an app without giving any consideration to the costs or benefits.

Your business may or may not need an app, but if you are unable to clearly define why you are investing in app development other than to say "everyone else is doing it," then I would argue that a copycat product will probably not give you the bump in business that you are hoping for. It may just be considered table stakes to stay in the game, but in order to derive benefit from app development, your app should at least help your customers as much or more than your existing channels do. More research may be needed before you go down that path.
User Rank: Apprentice
2/22/2012 | 12:30:00 AM
re: An App Isn't A Mobile Strategy
This always helped me when I was making apps http://howtofixstuff.blogspot....
2021 Outlook: Tackling Cloud Transformation Choices
Joao-Pierre S. Ruth, Senior Writer,  1/4/2021
Enterprise IT Leaders Face Two Paths to AI
Jessica Davis, Senior Editor, Enterprise Apps,  12/23/2020
10 IT Trends to Watch for in 2021
Cynthia Harvey, Freelance Journalist, InformationWeek,  12/22/2020
White Papers
Register for InformationWeek Newsletters
The State of Cloud Computing - Fall 2020
The State of Cloud Computing - Fall 2020
Download this report to compare how cloud usage and spending patterns have changed in 2020, and how respondents think they'll evolve over the next two years.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you.
Flash Poll