How can we ensure proper UX validation in the procurement process of new software?
In my work at Økonomistyrelsen (Danish Ministry of Finance), I discovered that UX is often overlooked in procurement processes. In most cases, UX is something that is tested in a general usability set-up, for instance, as a heuristic evaluation. While doing a general user test of possible procurement is good, such evaluations rarely reach the specific requirements’ core. Furthermore, testing is time-consuming. Thus, doing effective and precise testing is very valuable. However, looking towards academia for answers, there were few. So, I developed the framework presented below based on the research studies that were done and combined with my experience working with procurement processes at Økonomistyrelsen (Danish Ministry of Finance).
Functional and Non-Functional Requirements
While the procurement material always lists functional requirements, the non-functional requirements are often either downsized or not developed. However, developing the non-functional requirements to accompany the functional requirements can save time from heavy test sessions and yield more accurate test results. In the end, the procuring agent will get the most suitable product – and the user tests will yield more accurate results.
The following presentation demonstrates the framework to ensure proper UX validation when procuring software.
