Turning Weekly Friction Into Productive Collaboration

A global clinical research organisation was experiencing a level of communication friction between teams that was affecting how work got done. A pre-workshop survey made the situation visible in a way that internal conversations had not: 80 per cent of participants said they experienced this friction on a weekly basis.

The causes were identifiable. Workload pressures meant people were operating with little margin. Priorities were not always aligned across teams, so what felt urgent in one part of the organisation was not always recognised as urgent elsewhere. Roles were not clearly enough defined to prevent the kind of ambiguity that leads to duplication, dropped handoffs, and frustration. The result was a heavy reliance on long email chains and a pattern of cross-departmental issues that circled without resolution.

Communication friction in a clinical research environment is not just a culture issue. It has direct implications for project timelines, regulatory compliance, and the quality of work that reaches clients. When teams are spending energy navigating internal friction rather than focusing on the work, the consequences are felt in ways that matter commercially and professionally. Organisations that invest in how their people work together are not spending on a soft skill. They are protecting the quality and efficiency of everything else.

Red Mountain designed and facilitated a workshop that gave teams structured space to understand each other's constraints, not just their stated positions. The session was built around the reality that most communication breakdowns are not caused by bad intentions but by differences in context, priority, and role clarity that nobody has ever explicitly named.

Participants were asked to engage with the friction they experienced, explore its causes together, and work towards practical changes in how they communicated and collaborated. The workshop was designed to be directly applicable, not conceptual. People left with specific tools and approaches they could use the following week.

The participant feedback was exceptional. Every person who attended rated the session 10 out of 10 for usefulness. Eight out of ten said they could apply what they had learned directly to their work.

More meaningfully, teams that had defaulted to email began having direct conversations. Cross-departmental issues that had previously circled without resolution started being addressed at source. The change was not structural, it was behavioural, and it happened because the teams involved finally had a shared language for talking about how they worked together.