Challenges and Solutions During the Implementation Process
What challenges did you face during the implementation?
One big challenge is always ensuring that you are bringing along the users. We are introducing something new, and it looks different. It’s no longer the world as we had come to know it. How do I convince these users? Who do I need to focus on? And of course, we had to take different approaches in the different business units. In the introductory phase, it was important for us to understand the individual business units and know how they work. But other affected stakeholders, such as the recipients of TC invoicing, also had to be addressed accordingly.
Another challenge was the conversion from Excel, PowerPoint, and MS Project to Clarity. These tools were embedded to different degrees depending on the department. So, we had to harmonize a lot with the Clarity implementation.
Another key challenge was getting top management on board. Of course, there is always a high cost factor when launching new software, while the benefit cannot simply and directly be expressed in monetary terms.
How did you tackle these challenges?
What was critical to overcoming these challenges was the Proof of Concept that we carried out. Here we were able to test all our requirements in practice and see whether the system worked as it should. It was also very important that we involved the relevant stakeholders and users as early as possible and conducted very intensive training.
What also supported the process was that we had a certain agile working method. In other words, it was important to us to take the users with us and to satisfy their requirements as quickly as possible using concrete solutions.
We also recognized that it is important to establish so-called champions for the individual units, who would act as regular points of contact and communicate the benefits of the software. They are the first persons who can be reached for questions and handling problems in the business units, and they are responsible for introducing and pointing out new features to people.
What was particularly important when convincing management?
We showed how difficult it was to make costs and revenues transparent and to compare them without Clarity. And, of course, top management wants to know whether we are staying within our budgets, whether we are profitable, and if what we are doing is contributing to this or not. So: Are all costs generated by engineering and by our corporate functions covered by the end of quarter billing? Or are we operating in the red, necessitating us to take urgent action?
At this point, we quickly recognized the added value of Clarity, and we were also able to convince the management to introduce the new software.