A couple of months ago, after we sang Bye, Bye to Monochrome UIs, we indicated that we were beginning a series that chronicles what makes a good UI, and more importantly, a good UX (User Experience) in a modern Sourcing or Procurement system. This is critical because systems that are not useable do not get widely adopted, and systems not widely adopted never deliver the promised value.
In our first post on What Makes a Good UI where we noted that the full series was being published over on Spend Matters Pro [membership required] as it is the result of a deep long-term multi-blogger collaboration (led by the doctor and the prophet) designed to identify what should be (and not what ay given vendor will try to promote based on what they have), and sponsored by Spend Matters, we outlined some of the fundamental requirements of a UI / UX for any Supply Management application which include, but are not limited to:
- integrated, pervasive, guidance
- … that is based on true expertise and historical use
- “touch-less” automation wherever possible
- extremely context aware
- mobile support and mobile first in the field
- messaging as a competitive advantage
(And if you want deep coverage on these topics, see the first instalment of our full series on Measuring the Procurement Technology User Experience: More Than Just a Pretty Screen over on Spend Matters Pro [membership required].)
But, as we stated, these were just the absolute base-line requirements. In Parts II and III of our full series, we outline the next set of core functionality that should be pervasive across any Supply Management platform that you acquire. And in future articles, we dive into e-Negotiation, e-Auctions, Optimization, Spend Analytics, SXM, CLM, Requisitioning and Shopping, Procurement and Catalog Management, and Invoicing … just to start. But we’re getting ahead of ourselves.
One of the core requirements we reveal, and dive deep into, in Part II in our article on Smart Systems and Messaging, Chat, and Collaboration is smart systems.
As per our article, smart systems drive integrated guidance leveraging new “AI” techniques -— better termed automated reasoning (AR), as software isn’t truly intelligent —- that adapt and learn over time. They do this by mixing semantic technology, sentiment analysis, key-phrase driven expert systems and other machine learning techniques with history to determine what the user is doing and what the user wants to do.
For example, a smart system in sourcing will detect if there has been a full event/process before run by a user or similar peers in an organization, and allow the user to instantiate a new instance (by copying the template or previous event). Or, in the case of one-time requisition in which competition could benefit the outcome, a smart system can detect an automated spot-buy event that can be run against prequalified suppliers hands off, which the system suggestions.
And that’s just the beginning of what a smart system could, and should, do for you. For deep insights into not only where the bar is today (as leading providers start to release first versions of these guided systems), but where the bar will be by 2020, check out our post, which also dives deep into the Messaging, Chat, and Collaboration functionality [MCC] that a modern system should support. [Hint, more than just integrated e-mail or first generation chat!]
And stay tuned for the next part, coming later this week, on the final set of core requirements that we feel a modern Supply Management System cannot be without!
P.S. If you are a vendor invited to the Sourcing, SRM, CLM, or Spend Analysis Solution Map, this is a series you do NOT want to miss!