<?xml version="1.0" encoding="UTF-8"?>
<ArticleSet>
  <Article>
    <Journal>
      <PublisherName>Darzin International Company</PublisherName>
      <JournalTitle>Multidisciplinary Engineering Science Open</JournalTitle>
      <Issn></Issn>
      <Volume>3</Volume>
      <Issue>Serial Number 3</Issue>
      <PubDate PubStatus="epublish">
        <Year>2026</Year>
        <Month>07</Month>
        <Day>01</Day>
      </PubDate>
    </Journal>
    <ArticleTitle>Challenges of Communication Across Engineering Disciplines: A Qualitative Inquiry</ArticleTitle>
    <VernacularTitle>Challenges of Communication Across Engineering Disciplines: A Qualitative Inquiry</VernacularTitle>
    <FirstPage>1</FirstPage>
    <LastPage>15</LastPage>
    <Language>EN</Language>
    <AuthorList>
      <Author>
        <FirstName></FirstName>
        <LastName></LastName>
        <Affiliation></Affiliation>
      </Author>
    </AuthorList>
    <PublicationType>Journal Article</PublicationType>
    <History>
      <PubDate PubStatus="received">
        <Year>2026</Year>
        <Month>02</Month>
        <Day>17</Day>
      </PubDate>
    </History>
    <Abstract>&lt;p&gt;This study aimed to explore the major communication challenges experienced by engineers working across disciplinary boundaries in multidisciplinary engineering projects. A qualitative inquiry design was used to examine how engineers from different disciplinary backgrounds interpret, negotiate, and manage communication challenges in collaborative project environments. Participants were selected through purposive sampling from engineering firms, consulting companies, construction projects, technology organizations, and industrial project teams in Tehran, Iran. Data were collected through semi-structured individual interviews with 22 engineers representing civil, mechanical, electrical, software/computer, industrial, and chemical/process engineering disciplines. Interviews continued until theoretical saturation was reached, with saturation identified after the twentieth interview and confirmed through two additional interviews. All interviews were audio-recorded with participant consent, transcribed verbatim, and analyzed using thematic analysis. NVivo software was used to organize transcripts, develop initial codes, compare emerging categories, and support systematic retrieval of coded segments. Analysis generated five main categories: disciplinary language and epistemic framing, ambiguity at technical interfaces, coordination pressure under time and hierarchy, fragmentation of digital communication tools, and relational trust and boundary-spanning competence. Participants reported that communication problems often emerged not from unwillingness to collaborate but from differences in terminology, design assumptions, risk priorities, documentation habits, and expectations regarding decision authority. Cross-disciplinary misunderstanding was most visible at interfaces between design, implementation, safety, software, and project management functions. The findings suggest that communication across engineering disciplines is a socio-technical process shaped by professional language, disciplinary identity, organizational routines, project constraints, and the quality of boundary-spanning practices. Improving interdisciplinary communication requires more than formal meetings or documentation templates; it requires shared interpretive spaces, explicit interface management, translation-oriented leadership, and a project culture that supports questioning, clarification, and mutual learning.&lt;/p&gt;</Abstract>
    <ObjectList>
      <Object Type="keyword">
        <Param Name="value">engineering communication</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">interdisciplinary collaboration</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">qualitative inquiry</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">boundary objects</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">project coordination</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">Tehran</Param>
      </Object>
      <Object Type="keyword">
        <Param Name="value">thematic analysis</Param>
      </Object>
    </ObjectList>
    <ArchiveCopySource DocType="pdf">https://jmesopen.com/index.php/jmesopen/article/download/59/52</ArchiveCopySource>
  </Article>
</ArticleSet>
