Why the 4 stages of team development are still the best way to fix a toxic office

Why the 4 stages of team development are still the best way to fix a toxic office

Teams are messy. You've probably felt that awkward silence in a first meeting where everyone is too polite to say anything real. Or maybe you’ve been in a "war room" where people are basically shouting over each other because nobody agrees on who is actually in charge. It feels like chaos. But usually, it’s just psychology.

Back in 1965, a researcher named Bruce Tuckman realized that these headaches aren't random. He noticed a pattern. He called them the 4 stages of team development, and even though the workplace has changed from filing cabinets to Slack channels, the human brain really hasn't changed at all. We still go through the same uncomfortable dance every single time we start a new project.

If you understand these stages, you stop panicking when things get tense. You realize that the "Storming" phase isn't a sign of a failed team—it’s actually a sign of progress.

The polite "Forming" stage is actually a lie

The first phase is Forming. Honestly, it's the fakest stage.

Everyone is on their best behavior. It’s like a first date where nobody wants to admit they have messy habits. People are looking to the leader for direction, asking simple questions, and avoiding any kind of controversy. You'll see a lot of "Whatever you think is best" or "I'm just happy to be here."

But don't get comfortable.

In this stage, the team is just a collection of individuals. There is no "we" yet. According to Tuckman’s original paper, Developmental Sequence in Small Groups, this phase is all about testing the boundaries of interpersonal and task behaviors. People are trying to figure out what the "rules" are without actually asking.

If you’re leading a team here, you have to be direct. Don't be vague. If you don't set clear goals now, the next stage is going to hurt a lot more than it needs to.

✨ Don't miss: Is US Stock Market Open Tomorrow? What to Know for the MLK Holiday Weekend

Why you should actually want your team to start "Storming"

Most managers freak out when the honeymoon ends.

Suddenly, people are disagreeing about the project's direction. There’s friction. Someone thinks the deadline is impossible, and someone else thinks their teammate isn't pulling their weight. This is Storming. It's the most critical part of the 4 stages of team development because it’s where the real work happens.

If you don't storm, you end up with "groupthink." That's when everyone stays quiet to keep the peace, and then the whole project fails because nobody pointed out the obvious flaws.

Think about the Challenger disaster or the Bay of Pigs. Historians and psychologists often point to a lack of healthy conflict as a primary reason for those failures. When teams are afraid to "storm," they make terrible decisions.

How do you know you're in it?

  • Power struggles.
  • Vocal frustration.
  • Sub-groups forming at the water cooler (or in private DMs).

The goal isn't to stop the fighting; it's to make the fighting productive. You have to move the conversation from "You're doing it wrong" to "How do we actually solve this?"

"Norming" is the sweet spot of stability

Eventually, the dust settles. This is the Norming phase.

🔗 Read more: Big Lots in Potsdam NY: What Really Happened to Our Store

People start to accept their teammates for who they are—flaws and all. You start to hear things like, "I know Sarah is picky about the formatting, so I’ll just double-check it before I send it to her." That’s a massive win. It means the team has stopped fighting the reality of their situation and started working with it.

The big shift here is moving from "I" to "We."

In this stage, the team starts developing its own "tribal knowledge." You have inside jokes. You have unwritten rules about how meetings run. You’re actually listening to each other. But there's a trap here: teams can get too comfortable in Norming and stop pushing for excellence because they don't want to rock the boat again.

"Performing" is when the magic actually happens

This is the holy grail. Performing.

Not every team gets here. In fact, many teams get stuck in a loop between Storming and Norming forever. But when a team hits the Performing stage, they are a well-oiled machine. They don't need a manager to tell them what to do every five minutes. They anticipate problems. They trust each other enough to have a heated argument at 10:00 AM and go get lunch together at 12:00 PM.

The leader’s role shifts entirely here. You go from being a coach or a director to being an observer and a resource. You get out of the way.

The missing piece: It's not a straight line

Here is what the textbooks usually get wrong about the 4 stages of team development: they make it look like a ladder. You climb one, then the next, and you're done.

💡 You might also like: Why 425 Market Street San Francisco California 94105 Stays Relevant in a Remote World

That’s not how reality works.

If a new person joins the team, you instantly drop back to Forming. If the budget gets cut or the goalposts move, you're right back in Storming. It’s more like a cycle or a pendulum. You can be a "Performing" team on Tuesday and a "Storming" team on Wednesday because a client sent a nasty email.

Acknowledge that. Tell your team, "Hey, we're back in the Storming phase because of this new change, and that's okay." Normalizing the struggle takes the sting out of it.

What to do right now

If your team feels "off," stop looking at the spreadsheets and start looking at the humans.

  • Identify your current stage. Be honest. Are you all being too nice (Forming)? Are you annoyed with each other (Storming)?
  • Force the "Why." If you're in the Storming phase, call it out. Hold a meeting specifically to air grievances about the process—not the people.
  • Update the "Social Contract." If you're in the Norming phase, write down your "ways of working." It sounds corporate, but having a shared document that says "we don't send Slack messages after 6 PM" saves lives.
  • Let go. If you're lucky enough to be in the Performing phase, stop micromanaging. You'll only frustrate the high-performers and push them back into Storming.

Understanding the 4 stages of team development isn't about memorizing a 1960s psychology paper. It’s about having a map for the chaos. When you know where you are, you don't feel lost. You just keep moving toward the next stage.

Stop expecting a new group of people to "just work." It's a process. It's supposed to be hard. And honestly, the friction is usually where the best ideas come from anyway.