A good technology user experience is not like pornography: One can actually define it without seeing it, or at least attempt to do so.
As you may have noticed, the “Vendor Snapshot” deep dive reports that Spend Matters has been doing for the past year on technology providers have included a section on user experience (UI). In this section, we have rated UI on a number of factors. While it may seem that the first five ratings are subjective, they were all based on a comparison of the platform to other platforms, with a generalized baseline against a set of criteria for “good” user experience that the Spend Matters Analyst team has been developing for over a year.
But now that Spend Matters has released its first SolutionMap℠ — with many more to come — we decided it was time to put down a standard set of more specific definitions, across specific procurement technology modules, about what makes for a good user experience based on the criteria we ourselves use to evaluate UIs across the source-to-pay workflow.
Today, we’ll start our discussion by defining what general characteristics make for a good UI, and an effective user experience (UIX), primarily by sharing examples (without naming vendor names) and different use case scenarios that separate out a base-level UX from an advanced one.