insights! #25: A hackathon for software selection as an alternative to a criteria catalogue?

In today's insights! episode, Joubin Rahimi has Nam Hoang Dong as a guest. The two digitalisation experts take a look at the perennial topic of 'software selection' and its pitfalls. Which innovative methods can be used to align software selection with both the team and the company. Learn how Nam approached the topic, for example, in this episode.

Reminiscing, Joubin brings up a quote from Nam, from his time at Esprit, on software selection, which stuck with him. He said that "software selection isn't just about the features, it's about the team, how mature it is and what it can handle with which software". Taking that into account, a replatforming can be successfully carried out together. Joubin compares the quote to the idea that there's no point wanting to build a Ferrari without having mechanics with the necessary skills.

In the software selection process for a new ERP system, Nam took innovative approaches in terms of methodology at his previous employer Esprit. Not only was a classic criteria catalogue with several requirements for the software set up, but a hackathon was also carried out. Of the 7 technology companies involved in the tender process, 3 were invited to the store for a hackathon to solve various challenges together with the team.

This method for software selection has proven itself in the following ways:

1. Everyone involved got to know each other personally. According to Nam, this also reflects one of the most important points, because software can be rebuilt as needed, but the cultural and personal component isn't modifiable, yet is decisive for success. 

2. When solving tasks together, it becomes clear how flexible the team and the software are and where the limits of the application lie. This brings transparency to the strengths and weaknesses of the software.

Accordingly, a classic list of criteria is important, but collaboration in practice shapes shared success. Nam gives an example that illustrates this. Almost every requirements catalogue lists the criterion "good usability of the backend system". If you ask 10 employees what good usability should look like, you will get 10 different answers. This shows that software requirements that are weighted subjectively should not be the sole decision criterion. The software must be put to the test in terms of flexibility and quality, because in retail it is primarily about implementing new functions and the like as quickly as possible. This allows retailers to respond to market changes and remain competitive. In addition, the chemistry between the external service provider and the company, or the team working with it, must be right.