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.