What if you spent $100k on your enterprise app but nobody is using it?

63% of businesses consider enterprise mobility one of the greatest factors for their competitiveness. Meanwhile, according to SAP, 78% of enterprise apps are abandoned after first use.

What’s going on?

While building a practical guide to get results from enterprise mobility, we had to explore the true reasons behind this anomaly.
No pressure

Reason 1: No pressure

Use of mobile apps is optional.

Enterprises build mobile apps to save time and money. In theory, if employees can access core back-end systems on the go, the company becomes more efficient. In practice, employees have the choice whether or not to use the new app.

If you deal with invoices, you have to use company’s ERP or accounting software. If you are in sales, you must at least pretend to use the CRM or the director will come after you. With mobile apps, you can completely ignore them. As long as your data end up in the right system, no one cares if you put them in through mobile app at your customer site or through cumbersome ERP/CRM system in the office.
No emotion

Reason 2: No emotion

Consumer apps have spoiled us.

Log into your work PC. What do you see? A bunch of typical enterprise systems. Teams that built them did not have UI designers or usability experts on board. Still, as you have never seen anything better, you keep using it. The system’s complexity and slowness does not feel wrong or raise questions.

Now, unlock your smartphone. What do you see here? A bunch of shiny consumer apps, optimized to be as addictive and easy to use as possible. And then a dull and complex enterprise app, completely out of place. The same system that felt ok on your desktop feels wrong on a smartphone, because you HAVE seen many mobile apps that feel right.
No rationale

Reason 3: No rationale

What’s in it for me?

Enterprise IT systems are about data objects, fields, screens and process automation. They implement well-defined business logic and make companies efficient. We take the same approach to our enterprise mobile apps… and fail. Why?

Remember Reason #1? There is no pressure for employees to use the app. They must CHOOSE to use it. That happens in two cases: either users feel good to use the app, or the app solves problems that are personally important to them.

Now, look at Reason #2: it explains why a typical enterprise app isn’t fun to use. Do you think making the company efficient is a good rationale for users? Is this a problem they personally care about? That’s right: it is not. Give them something real. Salespeople hate to drive to the office just to drop off one paper. Field service technicians struggle to recollect what they did during the day as they enter work reports into the system in the eventing. Now it is about the users.
No support

Reason 4: No support

You are on your own.

IT helpdesks don’t know how to help you. Usually, they ask you to restart the system, then restart your device, then get a ticket number and wait. Bad enough in the office, terrible in the field.

Mobile apps work with back-end systems through several layers and are more complex than standalone enterprise systems. A lot can go wrong. You may need several support engineers to trace and resolve the issue. Meanwhile, your app user is cold, confused and upset, stuck at a client’s site with poor internet. The last thing he wants to hear is “please, reinstall the app”.
Makes sense, but how to solve all these issues? Use this guide as a practical tool for running your enterprise mobile app project.

What’s inside:
  • 5-min test: What are your chances to succeed?
  • 8 worksheets: How to make the app your users will love?
  • 5-min list: How to stay ahead of the game?

You can build a great enterprise mobile app. Start here:

Get our step-by-step Mobile Guide
Share this on: