UPI Study › Courses › Foundations of Leadership › Free lessons › Lesson 11.5 Free with a free account
When Teams Clash: Turning Tension into a Smoother Workflow
Foundations of Leadership · Chapter 11: Conflict & Diversity ModuleSection 11.5 · lesson 78 of 90video coming soon
← Managing and Problem-Solving Conflicts in OrganisationsNext lesson: Cultural Variations and Workforce Diversity in Conflict →
In this lesson
Turning tension into a smoother workflow - deliberately, because it does not happen on its own.
- Locate conflict within the team development arc
- Recognise five recurring team conflict patterns
- Convert friction points into workflow improvements
- Explain why psychological safety is the foundation
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,481 words). Read along, or search it.
Conflict & Diversity Module
When Teams Clash
Teams are the fundamental unit of performance in a modern organisation. They are also the primary arena of workplace conflict. That is not a coincidence, and it is not a flaw in how teams are built. It follows directly from interdependence, from diversity, and from compressed interpersonal exposure. This section looks at conflict inside teams. How it tracks team development, and what patterns recur. And how a leader converts that tension into better workflow.
The Arena
Storming Is Not a Malfunction
Bruce Tuckman's model of team development, published in nineteen sixty-five, is still the standard frame. Forming, Storming, Norming, Performing, and Adjourning. Conflict intensity is not flat across those stages. It peaks sharply at Storming, then falls. And here is the claim that gets misread. Storming is not a deviation from healthy team development. It is an inherent and necessary phase that high-performing teams must pass through. Which reframes what the leader is trying to achieve during it. Not a shorter Storming stage. A well-facilitated one.
Stage by Stage
What the Conflict Looks Like at Each Point
Each stage produces a different kind of conflict, and asks something different of the leader. At Forming, the conflict is invisible. Surface politeness, with covert uncertainty about roles and expectations underneath. The leader's priority is clarity on goals, roles and norms, plus enough safety for honest engagement. At Storming, disagreements come into the open. Direction, roles, working methods, and interpersonal friction. The priority is to facilitate rather than suppress. Channel the energy toward productive disagreement, and stop it escalating into the personal. At Norming, conflict falls as shared norms emerge, and residual tensions become manageable. The priority is to reinforce those norms, and to address lingering grievances before they calcify. At Performing, conflict is primarily task-focused and functional, and the team self-regulates. The priority here is to step back, and intervene only on serious issues. And at Adjourning, anxiety-driven conflict re-emerges as dissolution approaches. The priority is acknowledging achievements, facilitating closure, and supporting the transition out.
Failure Mode
The Leader Who Skips Storming
Storming is uncomfortable, so the instinct is to shorten it. There are two ways to try, and both do damage. The first is suppression. The disagreements about direction, roles and method do not go anywhere. They go underground. And they resurface later as relationship conflict, with no traceable origin anyone can address. The second is abdication. Leaving the disagreement entirely unfacilitated. Open disagreement then escalates from method to person. And the team learns something durable and wrong. That raising a difference is dangerous here. The window that matters is the transition from Storming into Norming. The leader's job in it is to channel conflict energy toward productive disagreement. Not to end the disagreement. Because norms that were never argued for do not hold when they are tested.
Five Patterns
Recurring Team Conflicts and Their Fixes
Beyond the developmental arc, five specific patterns recur, each damaging workflow in its own way. Communication silos, where members or subgroups withhold information, deliberately or through structural fragmentation. Coordination failures multiply, and blame conflict grows in the gaps. The response is structured information-sharing protocols, shared dashboards, and regular cross-subgroup check-ins. Silo-driven conflict is particularly prevalent in remote and hybrid teams. Not because people withhold more, but because the informal channels that used to close those gaps have atrophied. Role ambiguity and overlap is the second. Unclear ownership, or two people claiming the same domain. Conflict over territory, credit and accountability is then entirely predictable. The response is a RACI matrix, explicit role contracting at team formation, and role reviews as the work evolves. Third is competing priorities and resource conflict. A marketing representative and a developer in the same product team carry different functional allegiances. The response is shared objectives and key results that transcend those allegiances, plus explicit escalation agreements. Fourth is unequal contribution conflict, which is the quietest of the five. Perceived or real workload inequity generates resentment that goes unexpressed, and then erupts disproportionately. Transparent workload tracking and explicit team agreements about expectations are the counter. And fifth is a clash of working styles, over deadlines, detail, collaboration and communication. Those differences produce friction unless they are explicitly surfaced and negotiated, usually in a team charter discussion.
The Conversion
Friction Points Become Flow Outcomes
The proposition of this section is that team tension can be deliberately converted into workflow improvement. Communication silos become shared protocols. Role ambiguity becomes a clear RACI. Competing priorities become aligned objectives. And a blame culture becomes an accountability culture. But the arrow in the middle of that list does not draw itself. This conversion does not happen automatically. It requires intentional leadership facilitation. Tension left alone does not become a protocol. It becomes a habit of quietly working around each other, which looks calm and costs a great deal. Four evidence-based practices do the converting. Team charters, structured retrospectives, conflict as a learning mechanism, and psychological safety.
Practice One
Argue About It Before It Matters
A team charter is a collaboratively developed document. It makes explicit the team's shared purpose, values, working norms, communication protocols, and conflict resolution agreements. The value is not really in the document. It is in the timing. A charter surfaces and negotiates potential sources of friction before they have generated any conflict. Which is when they are cheap to negotiate, because nobody has taken a position yet that they now have to defend. Hackman's work, in two thousand and two, found teams with robust charters experience significantly lower relationship conflict. And significantly higher psychological safety. Note which type of conflict falls. The destructive one.
Practices Two, Three
Retrospectives, and Learning From the Aftermath
The second practice is the structured retrospective. A regular, facilitated review of what is working, what is not, and what should change. It was developed in agile software development, and has proven effective well beyond that setting. Its value is that it works as detection, not only as repair. A retrospective surfaces low-level tensions before they escalate. And it converts recurring friction into an actionable improvement commitment, with someone's name attached. The third practice concerns the aftermath specifically. High-performing teams treat a resolved conflict as a learning opportunity. They conduct a structured after-action review, asking what systemic or behavioural change would prevent recurrence. That transforms the conflict aftermath from a source of lingering resentment into a source of adaptive improvement. And it communicates something to everyone watching. That conflict here is taken seriously, and responded to constructively.
The Foundation
Nothing Above Works Without This
The fourth practice underwrites the other three. Amy Edmondson's landmark research, from nineteen ninety-nine, identified psychological safety. The shared belief that the team is safe for interpersonal risk-taking. She found it to be the single strongest predictor of team learning behaviour. And by extension, of a team's capacity to manage conflict constructively. In psychologically safe teams, members raise concerns early, while those concerns are still small. They acknowledge mistakes openly, rather than managing them privately. And they challenge one another's thinking without it being received as an attack. Leaders build psychological safety primarily through modelling. By being the first to admit uncertainty. The first to acknowledge an error. And visibly willing to be challenged by someone junior to them. Permission of this kind is demonstrated. It cannot be announced.
Case
The Orion Product Team
The Orion product team, at a healthcare technology company, shows the practices working together. Nine people. Engineers, clinicians, user experience designers, and compliance specialists. Within six weeks of formation, the team was in intense Storming-stage conflict. Engineers and clinicians disagreed fundamentally on product priorities. Designers felt ignored in sprint planning. And the compliance specialist was perceived as obstructive. In week seven, the team leader ran a half-day team charter session. Each member shared their professional priorities, their success criteria, and their biggest concerns about the project. For the first time, the engineers understood the clinical stakes driving the clinicians' positions. And the clinicians understood the technical constraints behind the engineers' pushback. Then came the ongoing structure. Bi-weekly retrospectives, addressing what was working and what was creating friction. Role responsibilities mapped with a RACI matrix. And a shared decision-making protocol. Clinical safety and regulatory compliance were non-negotiable constraints. Everything else required consensus, or failing that, the team leader's adjudication. By month four, relationship conflict had largely dissipated. Task conflict continued, particularly between engineering and design. But the team now experienced it as productive rather than threatening. And they met their first product milestone three days ahead of schedule.
Consolidate
Generative, Not Merely Survivable
Notice what Orion did not do. It did not resolve its conflict. It converted it. Structured facilitation produced the shared understanding and working agreements the team then ran on. Relationship conflict fell, and task conflict stayed. That combination is the target state, not a compromise on the way to something quieter. Which is worth saying plainly, because the intuitive goal is a team that does not argue. But a team that is not arguing at month four never went through Storming at all. The disagreements it skipped are still there, unlocated, and they will surface as something else. The leader's real contribution here is timing more than technique. Charters before the friction. Retrospectives during it. After-action review once it resolves. Every one of those practices is ordinary. The sequence is what makes them work.
About Foundations of Leadership at UPI Study
Foundations of Leadership (Business 205) is a self-paced online course of 90 video lessons in 12 chapters, from the roots of leadership theory and the trait, situational and transformational approaches to power, decision-making, communication, teams, conflict, diversity and global leadership. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Business courses Every course with PRO →
Compare: Management and leadership courses · Foundations of Leadership vs Leadership and OB
Why take it here
Why students take Foundations of Leadership with UPI Study
Where the credit goes
Universities that work with NCCRS
Foundations of Leadership carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About When Teams Clash: Turning Tension into a Smoother Workflow
Why does conflict peak during the storming stage of team development?
What happens if a leader suppresses conflict in a new team?
What is a team charter and how does it reduce conflict?
How does a RACI matrix help prevent team conflict?
About the Foundations of Leadership course
How many college credits is Foundations of Leadership?
How much does Foundations of Leadership cost and what is included?
Which universities accept UPI Study credits?
How long does Foundations of Leadership take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Foundations of Leadership.
90 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →