Schulungen rund um Clarity und itd Advanced Resource Planning mit Ihren Expert*innen von itdesign

Clarity Successfully Introduced: How the Implementation works

A clearly structured process, full transparency, and an experienced itdesign team – this is how your Clarity implementation becomes a success.

Process of the Clarity Introduction

Getting to Know Clarity and itdesign in Live Demos

We start with a short introductory meeting and a tailored web demo of Clarity. This gives you a quick and realistic impression of how well the solution meets your requirements. If needed, we deepen specific topics in focused deep-dive sessions – efficient, targeted, and non-binding.

  • Tailored introduction instead of a standard demo
  • Early clarification of core functional and technical requirements
  • Right stakeholders involved from the beginning
  • Realistic assessment of value and fit

Preparation in the Scoping Workshop

In the scoping workshop, we create the foundation for your implementation project: we cluster and prioritize requirements, clarify open questions, and jointly define what should be implemented in the first step. The result is a clear and comprehensible project framework that provides orientation for both sides.

  • Clearly defined project scope
  • Prioritized requirements as a decision-making basis
  • Realistic effort estimation
  • Clean foundation for further planning
itdesign ist der Partner für Ihre Clarity PPM-Software in Europa
itdesign ist der Partner für Ihre Clarity PPM-Software in Europa

Testing and Deciding in the Proof of Concept

Together, we build an MVP – a testable and tangible representation of your central use cases in Clarity. You experience and test the tool under real conditions without investing in licenses beforehand. The proof of concept provides maximum decision-making confidence and already forms the basis for the later implementation. Of course, we support you during the test phase and share our best practices.

  • Testing with your own processes and use cases
  • Well-founded decision-making without license costs
  • Early assessment of feasibility and value
  • Results can be directly used for implementation
Josef Zellner, Zollner Elektronik AG
The most important reason behind running a PoC was that it allowed us to put the software and the service provider to the test in advance so that we could answer the important questions that we had at the time. For us, the Proof of Concept was an important confidence-building measure that, in my opinion, should definitely be carried out when implementing any major software package.
Josef ZellnerDirector Multi Project Management
Zollner Elektronik AG
Stephan Watzka, DENSO AUTOMOTIVE Germany GmbH
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.
Stephan WatzkaDirector Engineering R&D
DENSO AUTOMOTIVE Deutschland GmbH
Lucas Klein, Organisation Manager in the Digital Efficiency division, TeamBank AG
In addition to the technical and functional validation, the proof of concept also acted as internal marketing for Clarity. It enabled us to make the tool tangible for future users at an early stage and increase the acceptance for the introduction of a new software.
Lucas KleinOrganizational Manager for Digital Efficiency
TeamBank AG
Dr.-Ing. Uwe Kernchen, REHAU Industries
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. 
Dr.-Ing. Uwe KernchenHead of Project Management Office
REHAU Industries SE & Co. KG

Clarity Implementation in Agile Sprints

Once you have decided in favor of Clarity, implementation proceeds iteratively in clear, well-plannable delivery cycles. We focus on Clarity’s standard functionalities with targeted configuration and add individual enhancements if needed. After each sprint, we jointly review results so that you always know the status of the project.

  • Quickly usable functions after each sprint
  • High transparency regarding effort and progress
  • Flexible adaptability through iterative methodology
  • Optimization of PPM processes with support from itdesign
itdesign Clarity PPM Team Meeting
Clarity implementation in agile sprints
Trust Center von itdesign

Further Development: Creating Sustainable Value

After go-live, we continue to support you – either closely or on demand. Together, we ensure that Clarity evolves with your requirements and generates sustainable long-term value.

  • Reliable partner even after go-live
  • Sustainable system development
  • Fast support in daily operations
  • Access to best practices from numerous projects
Dr.-Ing. Uwe Kernchen, REHAU Industries

Best Practices for Software Implementation

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.
Dr.-Ing. Uwe KernchenHead of Project Management Office
REHAU Industries SE & Co. KG
Lucas Klein, Organisation Manager in the Digital Efficiency division, TeamBank AG

Best Practices for Software Implementation

Taking an iterative approach to implementing Clarity can significantly boost acceptance of the tool among future users. At TeamBank, we found that it’s very helpful to gradually introduce individual functions that are aimed at replacing our existing processes. This allows employees to get used to new ways of working and makes them more likely to embrace them. Over time, the range of functions can then be continuously expanded.
Lucas KleinOrganizational Manager for Digital Efficiency
TeamBank AG
Stephan Watzka, DENSO AUTOMOTIVE Germany GmbH

Best Practices for Software Implementation

We need the acceptance of all users, and to this end we show them where and how added value is created – including beyond the boundaries of your business unit. It is important to sensitize users to these topics and to look at the topic holistically.
Stephan WatzkaDirector Engineering R&D
DENSO AUTOMOTIVE Deutschland GmbH
Unternehmensgruppe Theo Müller, Rolf Schmidt

Best Practices for Software Implementation

I would recommend that any company that wants to establish new processes (or tools) implement a six-month live phase for testing the processes. This allowed us to determine which optimizations and further requirements we still needed to implement for the introduction of digital approval.
Rolf SchmidtHead of Project Management Center of Excellence
Unternehmensgruppe Theo Müller

Critical Success Factors During the Implementation Phase

Realistic Expectations Regarding Duration and Effort

Depending on the scope, the introduction takes between three and twelve months. To ensure timely decisions, you should plan about 0.5 to 1 FTE on the customer side – this secures pace and quality. Make sure the necessary personnel resources are available during the project period.

Involving the Right Group of People

Ensure that the right and empowered roles are part of the implementation project and can free up capacity. Important roles include: project management, tool owner, process owner, champions, administrator, and training lead.

Additional Critical Success Factors

Other key factors include thorough preparation for workshops, early involvement of the works council, and active internal communication. Positive ambassadors from various departments and access to all relevant internal information are also helpful.

Our Services for a Successful Start

From process consulting and hosting to operations and training: Learn more about how itdesign supports you during the implementation phase. Benefit from 20+ years of experience with Clarity implementations.

itdesign's Consulting team
Your battery is almost empty.