Daily Archives: July 24, 2019

Still Looking for that Supply Management Usability Guide!

Long-time readers will know that there are a lot of guides out there as to what a good Supply Management solution for Sourcing, Procurement, etc. should do — including a lot of advice on this topic here on SI and over on Spend Matters, but not many guides. And while the doctor did write rather extensively on the topic of usability in Sourcing, Supply Management, Procurement, and P2P over on Spend Matters Pro, there are still very few guides for usability. (Searches in major search engines still come up few and far between, even after our first post on the topic here on SI seven years ago).

As per our last post, if the provided software was so obvious and easy to use that even a fifth-grader could figure it out, then the issue of “ineffective instructions” is a small one. But the reality is that, even with most platforms that are attempting to adopt consumer-style interfaces, most procurement and logistics software is still reasonably complicated due to the complex nature of what a Procurement or Logistics package capable of supporting global trade needs to do.

The thing is, even though the functionality is well understood, the best way to lay out the functionality, and underlying workflow, is not well understood in comparison and, unfortunately, if one company builds an interface that is too close to a competitor’s for some standard functionality, instead of the formation of a standard, in America, we get a frivolous lawsuit (courtesy of the patent pirates). So even though there should be design standards, there usually aren’t.

And even when the best-of-breed providers finally figure it out, since most of their UIs are built on decade(s) old technology, updating the UI is no easy feat. Especially when the new generation of employees, the millennials, are expecting consumer like interfaces. But who has anything close to this? Coupa with parts of the core platform (which has been built and re-built repeatedly to be easy to use around core Procurement functionality) and advanced sourcing (built on TESS 6 built from the ground up to be eminently configurable); Zycus is on the right path with their dew drop technology, but it will take a while to upgrade the entire platform; Vroozi with their mobile-first philosophy is quite usable for what it does; Keelvar with their configurable automation-based workflows; and GEP with their new user-centric UI vision are not just a few examples, but the majority of examples.

In comparison in the S2P game, Ivalua is getting close with their configurable workflows, but it’s still not obvious how to configure the platform to make it obvious to junior users; Wax Digital is one platform on one code base and pretty simple (but based on older Microsoft tech that takes time to upgrade); Determine, based on the old b-Pack platform is very configurable, but older technology and far from a modern look-and-feel; and Synertrade is really outdated (but very powerful).

And if we go beyond the big names, when it comes to the smaller vendors, except for a few of the newer best-of-breeds, like Bonfire and ScoutRFP, usability has always been a second concern and while a few of the smaller vendors are updating their UI (like EC Sourcing which should be much more modern with a year), most vendors are definitely not there yet.

Hence, since most platforms aren’t consumer like, and not likely to be figured out 100% by junior users without training, we still need that Supply Management Technology usability guide — especially since none of the platforms mentioned above with “modern” interfaces have the same workflows for the processes they support.

And what about the poor organizations who still have a mishmash of five generation one or two systems with inconsistent interfaces and workflows? What hope do they have of making sense of the full inter-related capabilities of their systems? Very little.

And while the doctor knows more than ever that the very nature of software, which is always evolving, makes such a guide difficult (and that this particular challenge is compounded by the fact that America still allows software to be patented so the pirates can plunder), but there should be at least some standard workflows and processes that all sourcing, procurement, and logistics software should attempt to follow in a reasonably standard way. It would make things easier for all supply chain partners, minimize unnecessary stresses and bumps, and help us evolve the profession as a whole. But alas, it will probably be another seven years before we get close to a real usability guide.