Consumerize or Die

Expectations of how simple and easy-to-use enterprise software should be are rapidly changing. iPhone and Android devices are so easy-to-use and common that they are raising the bar on how easy-to-use enterprise software applications need to be. And this in my opinion is a good thing.

It’s high time for enterprise software vendors to simplify their applications in the same way that the iPhone and Android have been simplified for consumer use. A mad rush to one-up the competition and add features or functionality has left us with bloated corporate applications. ERP, HR, training, CRM, and payroll applications seem to be more of a patchwork of screens and reports than a flowing portal to corporate information. Software vendors who wish to thrive in the future should take note and make some major investments in changing their software and their thinking in the following areas.

Simplified User Experience

Most corporate end users have been exposed to well-designed consumer software. Is it too much to expect corporate applications to have self-evident user interfaces that are fast, convenient, and functional? Or applications that are built for lay people and not only techies? Kludgy interfaces need to give way to intuitive and easier-to-use ones where information flows from a single point of data entry to secure storage and then to all places that are authorized to consume the information. In other words, I should enter a person, place, or quantity in one and only one place, and the software should handle the complexity of storage and access behind the scenes.

Data flow and real-time access

Offline and batch integrations just won’t cut it anymore. Onboarding an employee in payroll shouldn’t require a batch to run for the employee to be hired in benefits or time and attendance. Instantaneous access to real time information is the only acceptable norm for enterprise systems. Web services have existed for many years to provide for secure information exchanges so there’s just no excuse for offline batch information transfers. Corporate data flow from the information owner to the information consumer can happen immediately. Anything less is just not hip enough to be considered current.

Mobile-First Strategy

Data access should be 24/7 and from any type of device with a minimum of hassles. Often the most convenient option for a user is access via mobile devices. Application users may opt to use the full-site option where mobile functionality doesn’t exist or if it is more convenient to use the full site. To satisfy users’ expectations, enterprise software vendors need adopt a mobile-first strategy and accommodate the convenience of mobile access by careful planning and skilled development of their applications to leverage the strengths of mobile devices. Leading vendors will focus efforts toward mobile use wherever it is practical and will provide full-site options for functionality that doesn’t lend itself to smaller screen formats.

Unfortunately for enterprise software vendors, much work has to be done. It’s just not a matter of cut-and-paste or an application of “lipstick on a pig” to make my suggestions a reality. This effort will require much user interface rework and tradeoffs will have to be made between features and simplicity. In the end, vendors that make these investments will be rewarded with less demand for support and, even more importantly, happier end users.

So, enterprise software vendors: get onboard with simplified software, real time access, and a mobile-first strategy or become obsolete because soon your customers will expect nothing less from you.

Are you ready for a storm of cloud-based software?

Knowing the right questions to ask when buying anything is essential. Sourcing cloud-based software is no exception. Cloud software can be tricky to evaluate because it’s bundled as a service to eliminate complexity. As a result, vendors are conditioned to provide little or no transparency to buyers. We are all too familiar with what happens when we make assumptions, right?

When you evaluate cloud software, break down each part of the service bundle and consider it individually. Here are tips to help you avoid a storm-cloud-based software solution.

Be sure to understand how the infrastructure is managed.

Cloud-based software is most often a shared infrastructure similar to the way we share public highways and bridges. This is called a multi-tenant configuration. The challenge is that heavy traffic and congestion at certain times can be a fact of life. Just as public transportation is not always suitable or convenient for transporting wide and heavy loads or private secure cargo, cloud-based solutions may not be suitable or convenient for supporting every unique business requirement. Larger and more sophisticated organizations can still make use of cloud solutions because the most sophisticated cloud vendors optionally support dedicated virtual machines for database, application, or even web servers. These configurations can eliminate many of the typical limitations of a shared infrastructure. If you need this today or in the future, choose a vendor that has the flexibility to customize the infrastructure to meet your needs.

On the infrastructure side of the cloud service, you should consider the following points before buying:

  • Will the vendor support a private connection with guaranteed bandwidth to eliminate traffic and congestion from other clientele?
  • What additional layers of security protection are optionally available?
  • How is the service updated for new functionality and compliance?
  • What are the intervals for applying maintenance releases and updates?
  • What are the service-level guarantees for uptime that are provided by the vendor?
  • What are the security policies for protecting your information from malware or other threats?
  • What level of reliability and redundancy is built into the service infrastructure?
  • Can the service be optionally configured to support dedicated hardware, virtual instances, or even in hybrid environment for companies with unique business needs?

Gauge how the system is going to perform in real life situations.

This one could really zap you if you’re not careful. Thoroughly evaluate performance, or you could be dead in the water and loosing revenue. Think in terms of your peak usage times or peak season and then make sure your cloud vendor understands your needs and can keep up with the influx of system activity that your company and others may need the cloud infrastructure to support. Get performance guarantees in writing.

Evaluate the functionality to be sure that it will serve your business needs.

Most of us instinctively think in terms of the web front-end functionality for this new cloud software we’re getting. But it’s not enough to just evaluate this piece alone with cloud solutions. Cloud vendors bundle the front-end that you see with the back-end functionality that you can’t see or touch. You need to know what is going on behind the scenes so you can ferret out what might be missing. Ask questions like:

  • What devices, OS’s, and browsers does the vendor support?
  • What level of customization can be supported to adjust the product to more closely match your requirements?
  • Can you manage the customization or is this only handled by the vendor? How are customizations supported?
  • How are integrations with third-parties handled?
  • What about single sign-on or items like active directory integration?
  • How do you access your data or even download your data for safekeeping?
  • What functionality is not real-time and subject to scheduling?
  • How are alerts managed?
  • What are your options for reporting and analytics?

Understand the true cost of using the cloud service.

Take the time to truly understand the pricing model and your true costs. Don’t solely rely on the sales proposal and estimate provided by the vendor. Find out:

  • How is the pricing incrementally adjusted for growth or shrinkage in the use of the service? Is it adjusted based on transactions or number of covered users or not at all?
  • How is data storage and bandwidth consumption managed? Are limits imposed or do charges kick in at certain thresholds?
  • What pricing guarantees can be provided to ensure that your price continues to be fair down the road?
  • Does the vendor offer a scaled down use of the service after cancellation? What are the charges for this usage?

Check out the bricks and mortar behind the cloud service.

What services are available conveniently and affordably from the vendor? Don’t assume. For example, PeopleGuru’s payroll cloud service bundles services for ACH origination, garnishment processing, check printing, new hire reporting, and federal-state-local tax filing with a dedicated account management team but many of our competitors don’t. Clients that are used to these traditional payroll outsourcing conveniences that switch to a cloud service without a bricks and mortar support operation have the unique challenges of staffing up to support these functions in-house. So, be sure to understand what services your cloud vendor is offering:

  • How is the vendor’s support operation structured?
  • What level of support is provided during your implementation process?
  • Does the vendor have a structured process for guiding your through the implementation?
  • What tools does the vendor provide to facilitate data conversion into their product?
  • How is training delivered?
  • Are self-help tools available?
  • Is technical support immediately available when you need it, or do you have to wait 48 or even 72 hours for a response to an email?
  • Will you have a dedicated account management team and an escalation point of contact, or will you have to wait in a call queue to get the next available representative at a call center?
  • Did you check two or three client references?

By considering the infrastructure management, real life performance, functionality, true cost, and bricks and mortar, you’ll avoid storm-clouds and will be able to identify the best cloud-based solution for your organization’s unique needs.

Avoiding the “Saashole”

Software-as-a-Service (“SaaS”) is a software delivery model where the product and its associated data are hosted in the cloud, and users gain access to the application via a web browser. In recent years, many business applications including accounting, customer relationship management, enterprise resource planning, and human resource management have moved from on-premise licensed installations to SaaS as a primary delivery method. Gartner Group estimates that SaaS revenues will reach a projected $21.3 billion by 2015.

I should say upfront that I am a big fan of SaaS. Its simplified product and service model yields lower retail costs, improved vendor profitability, and makes customer support more convenient for everybody. Unfortunately this sometimes means that all customers have to be shoe-horned into “the box” of canned functionality. A “one size shoe that fits all” solution may work well for some organizations, but it often doesn’t for all. Organizations that have customization needs or unique integration requirements will find that SaaS is too restrictive for them and in turn may end up in the “Saashole” trap. There are often better choices for these organizations such as hosted or an on-premises license.

Here are my tips for avoiding the “Saashole” trap:

Review service level agreements for reasonable up-time guarantees and response time measures for all major application functions. SaaS applications are cloud-based, meaning a shared infrastructure of web servers, applications servers, and database servers that are accessible via the public internet. SaaS does not offer exclusive use to a single organization so performance can be impacted by what other users are doing at any given time.

Does the vendor support the browser and platform that you desire? Now days SaaS is accessed using a web browser. Are you patient enough for browser-only access? Is your intended use conducive to browser access? Is your internet connection stable and fast enough?

Choose a vendor with a more evolved reporting capability that shields end-users from system complexity. SaaS vendors commonly use a large data repository comingling customer data as this is most efficient and affordable for them. This multi-tenant design requires programming to separate customers logically and adds complexity to data reporting. Techniques like de-normalized database views and metadata layers facilitating intuitive data relationship, grouping, and summaries go a long way to enhancing the productivity of reporting. Ultimately the best approach eliminates all reporting complexity by abstracting the data relationships from the end-user. This yields point-and-click report definitions, grouping, and summaries in the most user-friendly format available.

Make sure the vendor’s “box” of capability is big enough for your needs. A single code base is another key tenant of SaaS. A lot of SaaS providers have application policies to customize look and feel, and in some cases, parts of the customer experience, so that doesn’t necessarily mean that every customer is stuck with the exact same user experience. But it what it does mean is that code customization for the unique needs of a single customer is not supported. Keep in mind that mature products tend to have a bigger “box” of capability that allows more organizations to be easily supported by the product.

Don’t get “Saasholed” into a long-term contract without cancellation options. Yes it is true thatSaaS has a subscription pricing model, but many vendors impose minimum contract terms or early termination penalties. It’s no fun to be pigeon-holed with a contract for a product that is not working well for you. And what if your organization requires change? You must consider your future needs as well.

Don’t overlook your system integration points, data imports, and data exports. In our business of HR, Benefits, and Payroll, getting data in and out of the system in a secure and efficient manner is an essential requirement for our clientele. Employee loads, time imports, carrier feeds, G/L files, and published web service integration points are just a few examples. Does the SaaS solution you are considering meet your integration requirements?

The key to every successful SaaS implementation is matching customer requirements to the capability of the solution. Before making a buying decision, conduct enough due diligence to know if the solution is a good fit for your unique requirements. Like with so many things in life, the proof of the pudding is in the eating. One sure way of avoiding the “Saashole” trap is to try the service before signing a long-term contract.