In Basel, should managers encourage technical disagreements within their teams?
Across pharmaceuticals, life sciences, Rhine logistics and international R&D in Basel, frontline managers must reconcile different areas of expertise and competing constraints. The practical question is specific: does encouraging disagreements about work improve decisions, or expose the team to further conflict?
What the literature establishes
Carsten K. W. De Dreu and Laurie R. Weingart (2003, Journal of Applied Psychology) distinguish task conflict from relationship conflict in a meta-analysis. Their findings show that both categories are, on average, negatively associated with performance and team member satisfaction. Technical disagreement is therefore not, by itself, an indicator of a well-functioning team.
Why the nature of the work matters
Karen A. Jehn (1995, Administrative Science Quarterly) offers an important distinction: the observed effects of task conflict vary according to whether work is routine or non-routine. Her study suggests that some disagreements can be useful in non-routine tasks, without attributing the same benefit to relationship tensions. Discussing an experimental hypothesis and challenging an execution instruction therefore do not necessarily call for the same managerial judgement.
The premature conclusion
One might conclude that conflict should be encouraged in R&D and discouraged in operations. That rule would go too far: a disagreement about a method can become personal, while an operational objection can reveal a genuine risk. Managers have more to gain by distinguishing what is being challenged, the supporting evidence and how the objection is expressed than by seeking a supposedly optimal level of conflict. (our executive and employee training programmes)
What the evidence cannot prescribe
These studies do not constitute a trial of a management method in Basel companies and do not establish that generating more disagreements would improve results. Conflict categories, often assessed through participants' perceptions, do not by themselves describe how exchanges unfold. In regulated activities, structuring discussion is no substitute for quality procedures or formal reporting channels.
A practical check in Bâle
As a possible practical exercise within SHR's « Management de proximité » programme, managers could examine technical disagreements over two weeks at a local interface: laboratory and quality, production and Rhine logistics, or a Basel team and international R&D. For each disagreement, record in an authorised register the issue challenged, the evidence considered, the person responsible for resolving it and the resulting decision or escalation, without copying sensitive data. Then calculate the proportion of recorded disagreements that received a reasoned, traceable response, and repeat the measurement after introducing this handling rule. This tracks how objections are addressed, not whether they disappear or, on its own, whether performance improves. To go further: explore the Frontline Management training in Basel in the canton of Basel-Stadt, or browse our executive and employee training programmes in Switzerland.
In pictures: Frontline Management in Basel
- frontline management
- Basel
- research
- training basel