iPad 34% Faster Than Workstation or Laptop, For Key ERP Functions

We test the tablet form factor in parts of the enterprise where one might expect it to be faster..and it is!

Up to 40% of corporate users could improve productivity

Used new Enterprise iPad Toolkit from iOptimal

In which parts of the enterprise does the iPad offer the best productivity gains? We set out to find the answer to that question, and the answer is: 20%, 40%, and 34%.

We chose a set of five common data entry screens from a corporate ERP suite – Financials, MRP, CRM, and Human Resources – from vendors such as SAP, Oracle, Lawson, and Salesforce.com. These screens were chosen as a cross-section representing (as best as possible) the thousands upon thousands of legacy database applications used in organizations across the world.

We built “iPad optimized” versions of those screens, which exactly duplicated the data entry functions in the standard Windows/keyboard versions. To build the iPad version we used the new iPad-enterprise prototyping tool just released by our partner firm iOptimal.

We chose these five functions carefully, to represent what we call the “40/20 rule." 40% of corporate users – generally managers, supervisors, and engineers – use only 20% of the ERP functions. By a happy coincidence, those 40% of users – our target audience – are also the ones that most likely to use a tablet, since they are generally people who “move around the office a lot” and have difficulties using laptops and workstations. Also by happy coincidence, the 20% of functions needed by these people are functions which don’t require large amounts of keyboard use, thus are well-suited for mobile tablets.

Converting that 20% subset of of ERP functions to the iPad should create significant time savings and a lot of happy users (and happy IT managers as well, since happy users become enthusiastic supporters for IT departments).

The Results

For our five representative tests, we had people perform the correct functions as fast as possible. We timed them by watching keystrokes and time motion study (using a stopwatch). On average these functions were 34% faster to perform on the iPad, for identical data entered, compared to the laptop or workstation.

Why Faster?

Quite simply, the screens typically used by supervisors and engineer lend themselves well to touchscreen interface. Using iPad user interface standards concepts, we were able to greatly reduce clutter on the screens, use finger gestures to quickly select options (more quiickly and intuitively than the mouse), eliminate almost all keystroke entry, and use location-based optimization to auto-fill and rearrange some fields.

The net result was, faster use.

Easier To Use

In addition, the screens were dramatically more enjoyable to use. Old style ERP is often quite crowded and complex to work with, with multiple layers of menu and complex coding structures; we took the opportunity to clean it up.

Caveats

• Some people might claim that the windows/laptop screens, if they were re-designed and improved, would show a lot of improvement as well. This is likely true. But the fact is, most ERP software isn’t being re-designed. So if the iPad serves as a catalyst to force us to clean up our designs, well, that’s a valid success.


• Note also that this 34% number does not include the fact that users can “carry the iPad everywhere” and would no longer need to walk back to their desks, re-log-in, or deal with charging a laptop. For some users, the iPad is faster simply because it can be carried all day long and eliminates more of the paper forms which still plague many organizations. If this mobility improvement was taken into account, this would add even more to the iPad’s speed advantage for this test. We are working to get an estimate of this number.


• Let’s reiterate that the iPad is unlikely to be faster (and might be slower) for functions that require heavy data entry or typing. For these functions, a keyboard is an advantage, and data-entry users who sit at their desks during the day won’t get much advantage from the mobility of a tablet.


• Finally we should note that these are preliminary results. We'd like to conduct this test again under more rigorous conditions. Nevertheless it does support what many users recognize intuitively: that a touch tablet with a highly tuned interface can increase the efficiency of business users.

Added note (9/14): People say we should do this test again, with a bigger sample set and with more "disinterested observers." Maybe even a media extravaganza! Great idea.

Strategy 3: Pick Subset of Features for iPad Conversion

How to develop a mobile strategy for your organization, part 3:

Focus resources on a subset of your features

As we said earlier, there is a specific group of high-value users -- on-premises managers, executives, scientists, doctors, etc. -- who are the most likely users for iPad versions of your ERP applications.

• These users are highly influential within the organization, so it's a great strategy to get their buy-in to this new platform
• They have been frustrated with ERP in the past because it didn't fit well with their fast-moving, professional status
• If IT departments can provide iPad-based systems, these users can be converted from skeptics to champions for the IT agenda, which is a big win for corporate IT
• Finally, these users use a certain subset of features from a typical ERP system. They use features that are "supervisory" in nature, usually not with a high degree of data entry or clerical functions

This is great news, because it points us to a simple, powerful strategy for succeeding with iPad ERP conversions. For your organization's mobile strategy, it makes sense to:

• Pick a subset of features from your ERP, Enterprise, or line-of-business application suite (whether purchased off the shelf from a vendor, or written as a custom application). Pick only those features used by your target group
• Focus on converting those high-value features "first" with your targeted resources
• Focus on quality over quantity; you must make these iPad versions significantly better, or in some cases, completely different from your legacy interfaces

This makes sense because with the iPad we don't want to just do a quick conversion of old, legacy designs. The touchscreen-mobile paradigm is a significant break from the character-based, screen-and-keyboard-based computing. To properly master this paradigm takes concentrated effort and is not straightforward. Our team and others are busily developing basic techniques for this conversion, but every organization will have its special needs that will require careful thought.

By narrowing your resources on a smaller number of features initially, you not only avoid getting too spread out (and rushing through a half-way version) but also get earlier wins with a few targeted, high-value, influential users who will then provide more internal support for the project.
Example: Creating an "iPad version" of an accounts payable system

1. First convert the accounts payable approval functions used by managers and VPs. These users are often mobile. Use the iPad or iPhone features to make this AP approval functions simpler to use and "touch centric". Make the old boring financial software interface better...make it intuitive and instantly understandable.
2. Don't include the payable entry screen in this first version. Payables entry is typically data-entry centric and used by accounts payable clerical workers or managers, and these people are already comfortable using workstations for their workday, and should not be the first choice for an iPad interface.

Design 2: Faster Without the Keyboard

Designing ERP software for the iPad, part 2:

Be relentless in eliminating keyboard use

Over time we're realized that, for our target user group, properly designed iPad applications don’t need much keyboard entry. In fact we have found that a tablet using "non keyboard” entry techniques is faster than a workstation using old-fashioned keyboard entry.

Our target group of users don't need the keyboard because they don't generally do data entry...they are more likely to be supervisors or managers "on the go" in their facility.

For example:

HR Data Entry Clerk

• Enters large volumes of employee data
• Sits at desk most of day
• Optimal system: Workstation/Keyboard

HR Department Manager

• Selects options from pull-down lists, reads emails
• Walks around most of day (to interview candidates or talk to managers)
• Optimal system: iPad

Finally it should be repeated that the lack of a keyboard on a tablet computer is not a flaw. Keyboards are essentially useless on the tablet form factor. This is why Apple computer chose, years ago, to bet on a touchscreen interface, and why most of the older, industrial tablets (used in healthcare, shipping, etc) are pen-based, and also why future tablet computers, we predict, will de-emphasize keyboard use, even if they include a physical keyboard to satisfy user demand.

Design 1: Not Just "As Good" But Dramatically Better

Designing ERP software for the iPad, part 1:

Make iPad version dramatically better than legacy systems.

ERP apps that are being ported over to the iPad/iPhone platform shouldn't aim to just duplicate the functionality of windows/keyboard platforms. iPad versions should be dramatically better, in the sense that they should leverage the unique features of this unique platform. They should take advantage of:

• Mobility
• Real-time business optimization
• Mobile capable workflow
• Slick user interface
• Form factor
• Location-based optimization of all types
• Bar code scanning, bluetooth data collection, video, audio, and photo

We hope to get into more detail in later posts.
Does this mean that any and all types of corporate applications should be converted to excellent iPad versions? Probably not. There is a certain class of users who are well suited to tablets. These target users have a certain set of functions they need. Any vendor porting enterprise applications to the iPad needs to start by choosing those target user functions, and create a "mini" version of the application for iPad.