The Procure-to-Pay User Experience (Part 1) [PRO]

AdobeStock/Nmedia

The history of enterprise software systems is fraught with implementation failures. This is especially true in the ERP and MRP space, which have contributed to some of the biggest supply chain failures in history (including Hershey Foods, Adidas and Foxmeyer). But not all failures are catastrophic. The majority are just the result of (significant) project overruns in terms of time and money or the inability to deliver critical features or functions in the original system specification. And this is more common than one may think. Some estimates put the rate of project overruns in IT as high as 85%. That’s problematic.

Why are there so many failures? The reasons are many. Some are the result of poor change management; others are the result of the selection of inappropriate process automation for the company; and still more are the result of limited or low-quality information. If one goes through the list of possible reasons, we see there is one commonality across the majority of failures: the user experience. Poor change management leaves users confused. Inappropriate process selection frustrates users as it increases time and effort (rather than decreasing it), and low-quality information makes users question why they are migrating to a new system at all. (And when significant system features or functions fail to be implemented at all, that’s the worst user experience.)

That’s why the user experience (UX) is important, and why Spend Matters has dedicated so much time to this topic (first on sourcing, and now on procurement). The reality is that if users does not use a solution to do their jobs, the solution does not generate value. And the ultimate key to adoption is often the user experience.

For full access to this PRO content: