How to Succeed at Collaborative Research: A Practical Guide for Teams
L. Michelle Bennett, Howard Gadlin, and Sawsan Khuri. Bristol, UK: Bristol University Press. 2025. 292 pages, including index.
Index Terms — Collaborative research, conflict management, interdisciplinary teams, professional communication, research collaboration
Reviewed by Adarsh Mittal, Nvidia (adarshm9031@gmail.com).
Review published 15 April 2026
As someone working in large scale engineering systems where communication issues directly affect execution, coordination, and sometimes even system correctness, I approached this book with an expectation that it would go deeper into technical and professional communication practices. The book is positioned around collaboration in research environments where it does a reasonable job explaining why communication matters in these settings. However, I found that while the intent is strong, the execution is mixed, especially when evaluated from a practical communication perspective.
One strength of the book is how consistently it frames communication as more than just information exchange. It emphasizes that collaboration requires alignment across perspectives, disciplines, and expectations, which is accurate. The discussion around interdisciplinary teams highlights how even basic terminology can lead to misunderstandings. For example, the case where a team realized late in their project that they had different interpretations of what environmental data meant is a good illustration of this problem. This is quite realistic. In engineering systems as well, different teams may use the same term but mean different things depending on context, abstraction level, or system boundaries. The book does well to surface this issue, and the idea of pausing work to realign definitions is practical, though idealized in how smoothly it is presented.
Another area where the book provides useful insight is in discussing communication on a scale. The section describing how leadership decisions often fail to reach execution layers stood out as particularly relevant. The example where governance teams make decisions but fail to communicate them effectively, leaving operational teams confused or demotivated, is something I have seen multiple times. This is one of the more concrete observations in the book, and it reflects a real communication bottleneck that exists in large systems, whether academic or industrial. The recommendation to have dedicated roles such as integration specialists or coordinators also makes sense, though again the discussion stays high level without going into how these roles operate in practice.
The book also makes a strong case for the importance of trust and psychological safety as prerequisites for effective communication. It breaks down trust into components like competence, reliability, identity, and motive, which is a useful framework. From a conceptual standpoint, this is well explained. However, the connection between these ideas and actual communication mechanisms is not always fully developed. For instance, it is clear that lack of trust impacts communication, but the book does not provide enough concrete guidance on how to design communication processes that can operate even when trust is low or still developing. In real systems, especially early-stage collaborations or cross-organization efforts, trust is often incomplete, and communication structures need to compensate for that.
One of the recurring patterns in the book is that communication is discussed indirectly through related concepts like collaboration mindset, leadership, or team dynamics. While this is understandable, it sometimes makes the content feel less focused from a technical communication perspective. For example, the idea of adopting a collaborative mindset and balancing task and relationship dimensions is explained in detail, but it remains abstract. There is limited discussion on how this translates into concrete communication artifacts such as documentation standards, decision logs, escalation paths, or structured feedback loops. For a book that aims to support professional communication, this felt like a missing layer.
The treatment of conflict is one area where the book adds some value, though again it could have gone further. The argument that conflict is necessary and can be productive is well made . The distinction between task-related and relationship-related conflict is also useful. However, the handling of conflict is mostly described by mindset and behavior, rather than communication techniques. For example, there is limited discussion on how to structure disagreement in meetings, how to document conflicting viewpoints, or how to resolve disagreements in distributed teams. These are practical aspects that would have strengthened the material.
Similarly, the chapters on diversity and difference highlight that diverse teams bring multiple perspectives but also introduce communication challenges. This is accurate, and the book correctly points out that diversity does not automatically lead to better outcomes without structure and effort. However, the guidance again remains general. There is less focus on concrete communication strategies for managing diversity in practice, such as establishing shared vocabularies, standardizing communication formats, or managing asynchronous communication across cultures and time zones.
One section that I found more practical is the Collaboration and Institutional Agreements appendix. The structured questions around defining roles, communication mechanisms, authorship, and decision making are useful. This is closer to what I would expect from a professional communication guide. For example, explicitly asking how routine communication will happen, how decisions will be made, and how conflicts of interest will be handled forces teams to think through communication upfront. In real systems, having these agreements early can prevent many issues later. I think the book could have benefited from expanding this structured approach into other areas, rather than limiting it mostly to the appendix.
Another interesting aspect discussed is the challenge of sharing credit and recognition in collaborative environments. The book highlights how traditional evaluation systems often favor individual contributions, creating tension for collaborative work. This has direct implications for communication, as unclear credit attribution can lead to conflicts, misalignment, and reduced willingness to collaborate. The book touches on this but does not fully explore how communication practices can mitigate these issues, such as transparent contribution tracking or explicit authorship criteria.
The mentoring chapter also brings in an important dimension of communication, particularly in terms of guidance and feedback. The idea that individuals may need multiple mentors for different aspects, including technical and interpersonal growth, is valid. However, again the discussion is more descriptive than prescriptive. There is less emphasis on how mentoring interactions should be structured from a communication standpoint, especially in distributed or large-scale teams.
Overall, I would say that the book is strong in building awareness around the importance of communication in collaborative research environments. It does a good job identifying key challenges such as misaligned terminology, lack of information flow, trust deficits, and conflicts arising from diversity or credit sharing. Many of the examples, such as the environmental data misunderstanding or the leadership communication gap, are realistic and help ground the discussion.
At the same time, the book feels more like a conceptual guide than a practical manual for technical or professional communication. For readers early in their careers or those new to collaborative environments, it can provide a useful foundation and vocabulary for thinking about these issues. However, for more experienced practitioners, especially those working in complex engineering or system level environments, the lack of detailed communication frameworks, concrete examples of failure scenarios, and operational practices limits the book’s usefulness.
In particular, I would have liked to see more discussion around communication under constraints, such as time pressure, incomplete information, or organizational boundaries. These are common in real world systems, and communication in such contexts often require structured approaches rather than relying on mindset alone.
In summary, How to Succeed at Collaborative Research: A Practical Guide for Teams makes a meaningful contribution in highlighting the central role of communication in collaboration by bringing several important concepts together in a coherent way. However, there remains a gap between conceptual understanding and practical application. With more emphasis on actionable communication strategies, real world case studies, and detailed examples of success and failure, the book could become significantly more impactful for a technical and professional audience.