Engineering products increasingly involve the collaboration of engineers from many different disciplines from mechanical engineering to software engineering and systems engineering as well as non-engineering experts, like data scientists, natural scientists or mathematicians. Each discipline has its own terminology, tools and methods, as well as a different mindset and logic by which work is structured. At present the terminology, tools and methods used in an organization have often come from the original discipline of the product. This paper reports the practical challenges in managing engineering design processes where multiple disciplines are involved. It outlines the implications for the development of tools and methods to bridge the disciplinary boundaries. The use of methods is not unproblematic even within a single discipline, as many methods proposed by academia are too complex for industry and practitioners cherry pick the parts of methods they like. The understanding and use of methods is strongly influenced not only by the discipline, but the specialisation and its school of origine, as well as the company context, while some participants, like chemists, have no experience of engineering methods at all. Challenges in the uptake of methods of do not only come from the method itself, but also a divergent underlying understanding of the purpose of the product, the technical system and the process by which it is generated. The paper argues that to increase the uptake of methods in organisations an active effort is required to develop a shared understanding of the methods in general and the mind set behind a specific method as well as the details of the method.