Unfortunately, that is reality far too often. The rollout of a new software takes place without integrating those people that should eventual use it effectively– namely the employees. But rollout projects are always change projects because the use of a new application normally is connected with process changes in the functioning of the employees. But why changing well-tried? That is what many users ask themselves and start using the new software with old and familiar processes. It is obvious that this is doomed to failure and the result is rejection and frustration from all sides. The solution: target-group-specific communication starting at an early stage.