Peter just got his first team. Five people, a new project, three months to deliver. The first two weeks, everyone is on a first-name basis, having lunch together and sharing excitement. By week four, the analyst Clara clashes with the developer James over the solution architecture. Week five, two people complain that Peter doesn't make decisions fast enough. Week six, Peter is asking himself: "Where did I go wrong?"
The answer is: nowhere. What Peter is experiencing was described by psychologist Bruce Tuckman back in 1965. And it has a name.
Tuckman's stages of team development
Tuckman analyzed dozens of studies on group dynamics and identified four stages that virtually every team goes through. He later added a fifth, but the original four are what really matter.
Forming: polite sizing-up
People get to know each other, figure out the rules, try to make a good impression. Conflicts are minimal because nobody wants to take a risk. It feels pleasant, but productivity is low. The team is not yet a team. It is a group of individuals who happen to attend the same meetings.
Storming: the storm that has to come
This is where things break open. People start pushing their opinions, disagreements emerge about priorities, roles, and work styles. Some conflicts are task-related (how to solve a problem), others are personal (who has what authority). Emotions rise, and so does frustration.
Here is the counterintuitive part: the storming phase is normal and necessary. A team that never goes through it will never build real trust. Think of it like exercise. Muscles have to be overloaded before they grow stronger. Conflict within a team works the same way.
Norming: finding shared rules
After the storm comes calm, but this time it is authentic. The team develops norms for collaboration, not the formal ones from the onboarding presentation, but the real ones: who responds quickly, who needs space, how disagreements get resolved. People start to understand each other's strengths.
Performing: real output
Only teams that successfully pass through storming reach this stage. Work flows, conflicts are resolved quickly and without personal attacks, roles are clear. Research by Marcial Losada and Emily Heaphy (2004) found that high-performing teams have a ratio of positive to negative interactions of roughly 6:1. Not because they avoid disagreements, but because they handle them constructively.
Why most teams get stuck in storming
Tuckman's model looks like a straight line. In practice, teams often loop back. A new member, a change in scope, a crisis, and you are back at the start. But the main reason teams get stuck is different: the manager tries to suppress the storming.
Picture this. Two team members disagree on an approach. The manager steps in immediately, decides for them, and says "let's move on." The conflict disappears from the surface but remains unresolved. Next time it returns in a different form. And the time after that. The team oscillates between forming and storming without ever moving forward.
What role do you naturally play on your team, and how does it shape the group's dynamics? A team roles test based on Belbin's model can help you find out.
Thomas-Kilmann's 5 conflict styles in a team context
In 1974, Kenneth Thomas and Ralph Kilmann described five conflict-handling styles based on two axes: assertiveness (how strongly you push your own position) and cooperativeness (how much you consider the other person). In a team setting, each style takes on a distinct shape.
| Style | Assertiveness | Cooperativeness | In a team it looks like... |
|---|---|---|---|
| Competing | high | low | "I'll decide this myself, we don't have time for debate." |
| Collaborating | high | high | "Let's sit down and find a solution that works for everyone." |
| Compromising | medium | medium | "We'll take part of your proposal and part of mine." |
| Avoiding | low | low | "It'll sort itself out." (It won't.) |
| Accommodating | low | high | "Fine, we'll do it your way, I don't mind." |
In a team there is a rule that is less obvious in one-on-one conflict: your style affects the whole team, not just you. When a leader chronically competes, the team learns to accommodate or avoid. When a leader chronically avoids, conflicts escalate because nobody addresses them.
When conflict is productive and when it is destructive
In the 1990s, Karen Jehn of the Wharton School distinguished two types of team conflict, and the difference matters a great deal:
Task conflict is disagreement about how to get the work done. Which technology to use, what the right strategy is, how to interpret the data. A moderate level of task conflict actually benefits the team because it forces people to think, argue, and challenge assumptions.
Relationship conflict involves personal friction, dislike, and feelings of disrespect. This type of conflict is almost always destructive. It lowers trust, raises stress, and causes people to stop sharing information.
The problem? Task conflict easily slides into relationship conflict. James says "that proposal doesn't make sense" and Clara hears "you don't make sense." The transition from a factual disagreement to a personal attack is often subtle and fast.
How personality shapes your conflict style
In the Big Five model, two dimensions matter most for conflict behavior in teams: agreeableness and extraversion (specifically its assertiveness facet).
High agreeableness leads toward accommodating and avoiding. Agreeable people naturally try to maintain harmony. They tend to be well-liked on their teams, but they risk never voicing their true opinions. Research by Timothy Judge and colleagues (2002) showed that agreeableness negatively correlates with salaries, partly because agreeable people negotiate less and confront less.
Low agreeableness correlates with a competing style. These individuals have no trouble expressing disagreement, but in a team they can come across as permanent opposition. Interestingly, in the short run they tend to be more effective negotiators. Over the long run, however, they damage team relationships.
High conscientiousness has a surprising effect: conscientious people lean toward compromising. They want things to work, and they are willing to give ground if it leads to results. At the same time, they insist on standards, so when it comes to quality they compete.
Neuroticism complicates the whole dynamic. People with high neuroticism experience conflicts more intensely and take longer to recover. In a team this means that one sharp exchange of opinions can affect one member for days, while another forgets about it by lunch.
Curious where you fall on these dimensions? The Big Five personality test measures all five traits and shows how they play out in everyday life, including how you handle disagreements.
Practical tips for managers
- Normalize storming. Tell the team that disagreements are part of the process. The sentence "it's normal that we disagree right now - it means we care about the outcome" has surprising power.
- Separate task conflicts from relationship conflicts. When a discussion starts drifting toward personal attacks, name it. "Let's get back to the substance. Which option do you prefer and why?"
- Do not decide for the team too early. Before you say "we'll do it this way," give people room to argue their positions. A decision the team co-creates is one they will follow more willingly.
- Watch the quiet members. Every team has people who go silent during conflict. That does not mean they agree. It means they are avoiding. Ask them for their perspective, but in a safe setting - one-on-one, for example.
- Look for patterns. If two people repeatedly clash, the problem is probably not the specific topic. It is more likely a communication style mismatch or unclear roles.
Practical tips for team members
- Frame disagreement in factual terms. Instead of "that's a bad idea," try "I see a risk here, specifically..." Criticizing an idea and criticizing a person sound similar, but the impact is completely different.
- Recognize your default style. Do you avoid confrontation? Do you tend to push your way no matter what? Becoming aware of your own pattern is the first step toward changing it.
- Do not interpret disagreement as an attack. When a colleague questions your proposal, try seeing it as an interest in the quality of the outcome. That is not always easy, but most of the time it is closer to the truth.
- Say what you need. "I need a day to think it over" is a perfectly valid response. So is "I need more context on why you see it differently." Communicating your needs explicitly reduces friction.
When conflict spirals out of control
There is a line beyond which team conflict stops being a growth opportunity and becomes toxic. You can recognize it by several signals: people stop communicating directly and talk "through" someone else, personal insults appear, someone starts deliberately sabotaging a colleague's work, or the team splits into factions that refuse to cooperate.
In these situations, you cannot just wait it out. Amy Edmondson of Harvard (2018) shows that without psychological safety - the belief that you will not be punished for speaking honestly - teams retreat into defensiveness and stop functioning. Restoring psychological safety after a destructive conflict takes deliberate effort: naming the problem, setting communication ground rules, and sometimes bringing in an outside facilitator.
The most useful thing you can do for your team is not to prevent conflict. It is to learn to stay in it long enough to extract what it offers: better decisions, deeper understanding, and stronger bonds between people who have worked through something difficult together.