Procurement in the public sector

Visma Proceedo is a system used mostly by employees in the Swedish public sector to buy things needed for work or by the organisation. The system includes everything from management of product catalogues, and placing and approving orders, to handling and approving deliveries and invoices. In such a vast system, several designers are needed who focus on different things. My responsibility was the part of the system handling the purchases and deliveries.

Examples of actions for the product as the…

…UX Designer

In some cases, things were added to the shopping cart by different people over a period of time. When it’s finally time to send the order, some items might be out of stock at the supplier, or been removed entirely from the product catalogue. Before this project began, talks had to develop both a better overview of the items in the shopping cart and a tool for replacing items in it. However, these were seen as two different projects and not a part of the same solution. 

Design of a shopping cart page

Purpose: Improve efficiency and effectiveness in order placement
Method: Collaboration with a major customer
Participants: System administrators, system owners, end users

Outcome:

A new view of the items in the shopping cart showing clearly which items need replacement. The view included a function for finding and replacing items in the cart

Decrease in customer shipment costs as problematic items were discovered before the order was sent instead of in the order response where replacement items otherwise would need to reordered with increased order handling cost associated.

…Experiment designer and data analyst

Optimising the function for finding the right product to buy in the system is something that is worked on continuously. However, it is something where regular user interviews will not give enough data for understanding the challenges. In order to do that, data collected during regular usage is needed. Hence, using the already implemented system for collecting analytics data this was investigated. Data was collected about not only how many search events were needed or time it took between first search and purchase, but also of the search words used and the products bought as a result of the searches. 

Customer data from a qualitative and quantitative point of view

Purpose: Improve product search
Design: Qualitative and quantitative analysis of customer data
Participants: 5 differently sized customers volunteered data from their users

Outcome:

An initial idea for improvements was scrapped before a line of code was written as the data proved that it wouldn’t be successful.

The customers who were presented with the findings about their setup were able to amend things under their control that improved the product search function for their users.

A framework for evaluating future improvements of the function was documented and the knowledge spread internally within the company by creating presentations and documentation.