Central Success Factors for the Software Implementation
What were the challenges during the implementation phase?
One challenge of the implementation was that we were carrying out the project during the Coronavirus pandemic. The entire project life cycle, from planning to implementation of Clarity to project completion, was therefore completely virtual. This stage went very well, because the team structures both at itdesign as well as here internally were such that everyone proactively participated. This can be seen just from the fact that we were able to carry out the implementation of Clarity in the planned timeframe.
In addition, we had to reconcile the varying structures and requirements of the different companies of the REHAU Group, especially REHAU Industries, and Meraxis. In the end, we also had to find out a way of mapping our sometimes complex internal structures with the new Clarity construct, so that we could ensure that the absolutely necessary features were in good working order.
What were the success factors for the implementation of the new tool?
The essential success factors for the introduction of a completely new tool are having a clear goal, good communication with a training at the end, sound project planning, specialist expertise, stringency, and having fun carrying out the project.
How did the Proof of Concept help you decide on the solution and proceed with the implementation?
We implemented Clarity in Clarity itself. This was the original project and was assigned project number P00001.
Before you can convince others of the worth of a new tool, you first have to be convinced of this yourself. In the course of implementing Clarity directly as our first project, we became sufficiently convinced of its merits, so that we were able to convince others afterwards with the same level of enthusiasm as true believers.
The methodology of a Proof of Concept is ultimately to ensure that you are not sold a bill of goods. However, it was important for us to ensure from the start and in a very early project phase that Clarity offered everything we needed.
itdesign was at our side during the implementation. This has also turned out to be a positive experience, because our colleagues at itdesign are very reliable, they know what they are talking about, and you can tell that they enjoy what they do every day.
Proof of Concept
Save time and money, minimize risks, and have a sound basis for decision – the Proof of Concept (PoC) is our recommendation for your software selection.
How did you manage to implement Clarity at two companies at the same time?
The two sister companies REHAU Industries and Meraxis operate in two completely different areas. Of course, the two companies have a lot in common when it comes to project management, but there are also different aspects, approaches, and perspectives.
However, it turned out to be no problem at all for us to add Meraxis to the implementation project, because we were able to address the sometimes varying concerns without any problems by using the individual customization options of Clarity (e.g., blueprints and templates).
To what extent did the agile approach help you during implementation?
It made a lot of sense for us to break down the project goal into relatively small components, i.e., sprints or phases. This allowed us to start the implementation and processing in a topic-focused manner and not get lost in the big picture. In the end, this process helped us to launch very quickly with an initial installation of Clarity that was configured just the way we needed it.
You and the project team attached great importance to a well developed communication and training concept. How has this enriched your Clarity implementation?
In order to complete the implementation of Clarity, it was of course necessary to inform and train our internal colleagues accordingly.
We conducted this training in the form of two-hour presentations. These were supplemented by short training videos that we made in house, which explained the features of the tool in a focused manner. We distributed these internal training videos through our PMO Daily site, as we termed it, on our intranet.
Ultimately, we were also able to ensure a high level of acceptance of Clarity by holding weekly Q&A sessions in which colleagues could dial in with their problems, which we could then try to solve ad hoc.
What are some important experiences you had during the implementation phase?
Basically, we realized that things turned out to be much simpler than we would have expected from our own specifications, which was something new to us. Let me just mention the risk analysis by way of example: This risk management module in Clarity is very simple and intuitive to use. We wanted to map our old structure in the tool – a highly complex format. And this is where Clarity ultimately helped us to simplify our process.
In this way, Clarity and itdesign have also helped us to grow as a company and institute best practice approaches, influences, and suggestions from the outside world into our own company.