The 7 myths of CMDB projects

A CMDB? We tried that. It doesn't work!
If the CMDB project is not treated as a project, the CMDB is doomed to failure right from the start. The impression: building a CMDB is impossible. We will show you how to make the benefits for your entire company visible to everyone. New motivation for the project is guaranteed.

A CMDB cannot be kept up to date!
It is always a question of preparation. Create a plan for the right data, priorities and responsibilities with numerous expert tips. You will see: An up-to-date CMDB is not magic.

It only costs time and money
That's right! A CMDB initially means additional effort. Read the e-book to find out why it's still worth it and what potential savings your company can expect.

All data must be in the CMDB!
There are also several options here. Use our suggestions to find your "point of truth" - the right mix of different data sources for your company.

We have a discovery. That's enough for documentation.
That does sound tempting. But it will also lead to big problems. Would you like to know why Discovery does not replace a CMDB? And why Discovery and IT documentation complement each other perfectly. You'll find the answers in the e-book.

Let the trainee document. That's quite enough.
You can probably guess that this is not the best solution. Our e-book provides an overview of the necessary roles and responsibilities in a CMDB project.

Setting up a CMDB? We can do that on the side.
At the latest, once the project has failed, it will be recognized: It doesn't work "on the side". It is a project. A structured approach is important. We explain what you should pay attention to.