LEAD 6323 Module 4 Group Dynamics and Conflict Analysis Example

Report the Genome or Wait for the Culture? Group Dynamics and Conflict on a Public Health Laboratory's Outbreak Response Team

Student Name

American College of Education

LEAD6323: Organizational Behavior and Culture

Module 4 Assignment

Instructor Name

November 2, 2026

Introduction

The course's first three papers dealt with the laboratory as a whole: its culture, its jobs and its chain of approvals. This paper turns to a team. Last summer, during a Salmonella cluster linked to a regional restaurant chain, the laboratory formed an outbreak response team of two microbiologists, two sequencing scientists, a quality assurance specialist and a liaison epidemiologist from the health department. The team split over a single question and took weeks to recover. I analyze what happened using research on group development, conflict and psychological safety.

What Happened

Within four days, whole-genome sequencing showed that isolates from nine patients were closely related, strong evidence of a common source. The sequencing scientists wanted the result reported to the epidemiologist immediately, as a preliminary finding, so the health department could interview patients about the restaurant. The senior microbiologist argued that laboratory policy required culture confirmation and serotyping of all isolates before any report, and that a premature link could damage a business unfairly. The meeting grew heated. A sequencing scientist said the microbiologists were "protecting a procedure instead of people"; the microbiologist replied that the new unit did not understand regulated reporting. The epidemiologist, caught between them, waited. The preliminary report went out two days later, after I intervened, and two more cases occurred in the interval. For weeks afterward the two groups avoided each other.

A Team That Never Formed

Tuckman (1965), reviewing studies of small groups, described a developmental sequence of forming, storming, norming and performing, in which groups orient themselves, pass through conflict, establish shared norms and then work effectively. The outbreak team was assembled in a day and expected to perform at once. It had no time to form or to agree on norms, so it met its first serious disagreement without any shared understanding of how the team would decide. The storming that followed was predictable: members fell back on the norms of their own sections, which differed sharply.

Task Conflict Turned Into Relationship Conflict

The disagreement began as task conflict, a dispute about the work: whether to report before confirmation. Within minutes it became relationship conflict, personal and emotional: who understood public health and who was protecting turf. De Dreu and Weingart (2003), meta-analyzing research on conflict in teams, found that relationship conflict was strongly and negatively related to team performance and satisfaction, and, contrary to what many textbooks suggest, that task conflict was also negatively related, especially in complex decision-making tasks. Disputes about the work did less damage, they added, in teams where those disputes stayed apart from personal friction. The team's problem was not that it disagreed about reporting; it was that the disagreement fused immediately with each group's view of the other.

Why No One Spoke Up

Two members said little during the meeting: the quality assurance specialist, who later told me the policy actually allowed preliminary reports to public health partners with a clear caveat, and the second sequencing scientist, who had a compromise in mind. Edmondson (1999), studied 51 factory teams and reported that where people trusted they would not be embarrassed for owning up to an error or asking an obvious question, the group did more of the reflecting, asking and experimenting that counts as learning, and those learning groups performed better. The outbreak team lacked that safety. In a laboratory where errors are treated as personal failures, as Module 1 found, offering a policy interpretation that contradicted a senior colleague in a tense meeting felt risky, and the information that could have resolved the dispute stayed unspoken.

The Epidemiologist's Position

The team's only member from outside the laboratory saw the conflict differently. The liaison epidemiologist told me afterward that she had wanted the preliminary result badly, because patient interviews lose value with every day that passes, but felt she had no standing to take sides in a laboratory argument. Her silence was a structural problem, not a personal one: the team had no agreement about whose needs the laboratory's reporting decisions were meant to serve. In a public health laboratory, the epidemiologist is in effect the internal customer for every outbreak result, and a team that leaves the customer waiting while it argues about procedure has lost sight of its purpose.

What the Team Needed

The analysis points to three missing elements. First, a decision rule set before the crisis: who decides what is reported, and when, if team members disagree. Second, a way to keep task conflict separate from relationship conflict, such as a facilitator who restates arguments in terms of the decision, not the people. Third, enough psychological safety that the members with relevant information would offer it, which depends on the team leader explicitly inviting dissent and treating it as useful.

Recommendations

The laboratory and the health department have agreed on four changes. A standing outbreak response protocol now specifies that preliminary sequencing links may be shared with the epidemiologist with a written caveat, and that the laboratory director decides if the team cannot agree within four hours. Outbreak teams will be drawn from a trained roster that meets quarterly during quiet periods, giving members time to form and norm before a crisis. Each team meeting will open with a two-minute statement of the decision to be made and close with a round in which every member is asked for any concern not yet raised. And after each outbreak, the team will hold a short debrief focused on what the team learned, not on who was right.

My Own Part

The analysis would be incomplete without my own role. I learned of the dispute a day after the meeting and resolved it by decision, which ended the delay but did nothing for the team's learning and left each side feeling overruled. Had the team known in advance that disagreements would come to me within four hours, the delay would have been shorter and the conflict less personal.

Repairing the Relationship

Rules prevent the next conflict but do not repair this one. I met separately with the senior microbiologist and the sequencing scientist, then together, and asked each to describe what the other's concern had been. The microbiologist acknowledged that the delay mattered for patients; the sequencing scientist acknowledged that the concern about naming a business prematurely was legitimate. They now co-lead the quarterly roster meetings, a small sign that the conflict has become something the two groups share rather than something that divides them.

Conclusion

The outbreak team's breakdown was not caused by bad people or by disagreement itself. It came from a team that had never formed, a technical dispute that fused with long-standing tension between subcultures and an environment where members with key information did not feel safe offering it. Research on group development, conflict and psychological safety explains each element, and the recommendations address each. Module 5 will take these lessons into a plan for changing the laboratory's culture as a whole. The next outbreak will test whether the protocol and roster work; the team has agreed to review the first one jointly, whatever the result.

References

De Dreu, C. K. W., & Weingart, L. R. (2003). Task versus relationship conflict, team performance, and team member satisfaction: A meta-analysis. Journal of Applied Psychology, 88(4), 741-749. https://doi.org/10.1037/0021-9010.88.4.741

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350-383. https://doi.org/10.2307/2666999

Tuckman, B. W. (1965). Developmental sequence in small groups. Psychological Bulletin, 63(6), 384-399. https://doi.org/10.1037/h0022100