A Team Doesn't Become High-Performing Overnight
Every high-performing team passed through a phase that looked, from the outside, like it was falling apart. That phase isn't a warning sign. It's the schedule.
The team that seems to be struggling with conflict in its second month isn't necessarily failing. It may simply be exactly on time.
The last entry in this series argued that leadership effectiveness depends on matching style to the readiness of the specific person in front of you — a fundamentally individual, one-relationship-at-a-time idea. But leadership rarely happens to one person at a time. It happens inside a group, and groups have their own developmental timeline, one that unfolds according to its own logic regardless of how well any single leader adjusts to any single member.
That timeline is the subject of this entry: how a collection of individuals who happen to share a task actually becomes a team capable of performing well together — and why that transformation reliably passes through a stage that feels, to most leaders experiencing it for the first time, like evidence that something has gone badly wrong.
Psychologist Bruce Tuckman's model describes team development as a predictable sequence of stages — forming, storming, norming, and performing, later joined by a fifth, adjourning. Forming is polite and cautious; storming is where real disagreement and competition for roles surfaces; norming is where the group establishes working agreements; and performing is where the team finally operates with real trust and efficiency. The critical insight is that storming isn't a malfunction to route around — it's a necessary phase that most genuinely high-performing teams pass through, not skip.
Conflict is a stage, not a failure · The sequence can't be rushed · A leader's job shifts at each stage
Tuckman's Sequence
Bruce Tuckman proposed his model in 1965, based on a review of existing research on small-group development, and it has held up remarkably well across decades of subsequent study. The sequence describes four original stages, with a fifth added later.
Forming: cautious, polite, dependent
In the earliest stage, members are getting oriented — to the task, to each other, and to whatever authority is present. Behavior tends toward politeness and caution; people are testing boundaries quietly rather than asserting positions directly, and there's a notable dependency on the leader to provide direction, since the group hasn't yet developed its own shared norms to lean on.
Storming: friction that actually needs to happen
As members become more comfortable, the politeness of forming gives way to real friction — disagreement over roles, competition for influence, and often direct pushback against the leader's authority or the task's framing. This is, by a wide margin, the stage most often mismanaged, because it looks like the team unraveling rather than developing. In fact, storming is where the genuine differences in perspective, working style, and priority that were suppressed during forming's politeness finally surface — and surfacing them, uncomfortable as it is, is a precondition for actually resolving them rather than papering over them indefinitely.
What makes this stage so consistently misread is that it genuinely does resemble failure from the inside. Productivity often dips, communication turns sharper, and it can feel, to a leader experiencing it for the first time, like evidence that the team was assembled poorly or that something has broken that wasn't broken during the calmer forming stage. The uncomfortable truth is closer to the opposite: a team that never storms at all has often simply never tested whether its apparent harmony can survive real disagreement, which tends to catch up with it later, at a less convenient moment.
Norming: the group builds its own rules
Provided storming isn't avoided or artificially suppressed, the group typically moves into norming: a stage where roles settle, working agreements form, and a genuine sense of shared identity starts to replace the earlier dependency on the leader for direction. Trust builds specifically because the group has now been through real disagreement together and found a way through it, rather than simply agreeing on the surface without ever testing whether the agreement would hold under pressure.
Performing: high trust, low friction, real autonomy
In this stage, the team operates with enough shared trust and clarity that it can focus almost entirely on the task itself, rather than on managing internal relationships or roles. Decision-making becomes faster and more distributed; the leader's role shifts from directing or mediating to removing external obstacles, since the internal ones have largely already been resolved.
Adjourning: the stage most models forget
Tuckman later added a fifth stage to account for teams that have a defined endpoint — project teams, task forces — describing the process of winding down, reflecting on what was accomplished, and managing the emotional reality that a team that developed real cohesion is now dissolving. Ignoring this stage, treating a team's dissolution as purely administrative, tends to waste a genuine opportunity to capture what was learned before the group's collective memory disperses.
Leaders uncomfortable with visible conflict sometimes try to suppress storming directly — enforcing artificial harmony, shutting down disagreement quickly, rewarding surface-level agreement. This doesn't eliminate the underlying friction. It defers it, usually to a worse moment, since the same unresolved differences in role, priority, and working style don't disappear just because they weren't allowed to surface on schedule.
What This Means for a Leader's Role
Tuckman's model connects directly to the situational leadership covered in the previous entry, but at the group level rather than the individual one. A leader's job genuinely differs by stage: providing clear direction during forming, when the group has no established norms of its own yet; facilitating rather than suppressing during storming, helping disagreement surface constructively instead of destructively; stepping back to let the group's own norms take hold during norming; and shifting toward removing obstacles rather than directing during performing, once the team has developed enough internal trust to largely run itself.
Misreading which stage a team is actually in is one of the more common and costly leadership mistakes this model exposes — treating a storming team as though it were already performing, for instance, by stepping back and removing structure exactly when the group still needs a firm hand to work through its friction productively.
Name which stage the team is actually in
Not which stage you'd like them to be in — the honest current state, based on how members are actually behaving with each other.
Expect storming, don't suppress it
Treat visible disagreement over roles or priorities as a sign of real development, not a signal that something has gone wrong.
Facilitate the friction toward resolution
The goal isn't ending disagreement quickly — it's helping the group work through it to something durable, rather than papering over it.
Loosen your grip as norming takes hold
Continuing to direct closely after the group has developed its own working agreements slows the shift into genuine performing.
Don't skip adjourning for teams with an endpoint
A deliberate close — reflecting on what worked, what didn't — captures learning that otherwise disperses along with the team.
The team that avoids storming entirely hasn't skipped a difficult phase. It's postponed it — usually to a moment with far less room to recover from it.
What Comes Next
Tuckman's model explains how a team develops the internal cohesion to perform. It says less about what actually sustains that performance once cohesion exists — what makes people continue contributing at a high level, beyond the basic mechanics of trust and role clarity. The next entry in this series turns to that question directly: the shift from transactional leadership, built on a straightforward exchange of effort for reward, toward transformational leadership, which asks what happens when a leader tries to create genuine motivation, vision, and commitment instead.
Is your team actually in the stage you think it's in?
Misreading forming for performing, or storming for failure, is one of the most common and costly team-leadership mistakes.
Explore the Self-Boost Diagnostic Center →- How Do You Actually Lead a Group? The Ideas Behind Leadership
- The Leader as a Hero: When Leadership Was About Who You Are
- Leadership Is Not Who You Are — It's What You Do
- Do People Need to Be Controlled? Theory X vs. Theory Y
- There Is No Perfect Leadership Style
- A Team Doesn't Become High-Performing Overnight
- What If Leadership Is About Creating Motivation?
- What Happens When the Leader Serves the Team?
- What If Nobody Is Really "The Leader"?
- After 100 Years of Leadership Theory, What Actually Makes a Team Work?
Links activate as each episode is published.
No comments:
Post a Comment