Abstract
Interdisciplinary research is increasingly recognized as a key method to tackle complex societal challenges and stimulate creativity to find innovative solutions. Our key goal when starting our collaboration was to come to innovative ways of treating chronic pain. An ambitious goal that requires out-of-the-box and high-risk-high-gain research. However, interdisciplinary research in practice can be uneasy and will not always be successful. This paper describes a case story focussing on the challenges we faced building an interdisciplinary team. One of the most important lessons is that researchers from different disciplines may think they speak a universal ‘language of science’, but a thorough understanding of each other's ways of working, research paradigms, methods, and concepts is necessary before they can start working together on solving scientific questions. In fact, if researchers cannot understand each other's language, they cannot expect patients to understand scientific language either. Lastly, for academics to engage with a non-scientific audience and vice-versa, we need to find and create places to meet and find ways to interact effectively. Language is the medium through which all these interactions take place. It is therefore essential that language takes a central place in the process of collaboration across disciplines, interdisciplinary research, patient participation and public engagement. In this case story, we share our experiences in creating a common language, summarized in five steps (1: creating the team; 2: metaphor-forced introduction to disciplines; 3: creating common ground; 4: outreach; 5: integration). Metaphors play an important role in this process. We will demonstrate how we reflectively progressed through these steps while enhancing interdisciplinarity, (scientific) innovation and public engagement. This five-step journey can be used as a process-tool for any other high-risk-high-gain research team seeking to innovate through interdisciplinarity – with the risk of becoming a brilliant failure.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.