Framework

Tuckman's Stages of Team Development

Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.

Tuckman's Stages of Team Development Find this on the mind-map

Introduction

Back in 1965, an American psychologist named Bruce Tuckman sat down and asked a question that hadn't really been asked properly before: do teams actually develop in a predictable pattern, the same way a person moves through stages of growth? He studied how groups formed, clashed, settled, and eventually clicked, and out of that came a simple, sticky idea — a team isn't a fixed thing you assemble once. It's a group moving through stages, and each stage produces its own behavior, its own friction, and its own demand on you.

How It Works

Stage 1: Forming. The team is new, or newly reshuffled, and people often haven't worked together before. Everyone's polite but cautious, unsure of the goal, and leaning on you for direction. Your job here is to set clear goals, assign roles, and help people actually get to know each other.

Stage 2: Storming. Once people have spent real time together, differences in style and approach start surfacing. Arguments, power struggles, resistance to assigned tasks. Your job is to build trust, mine for conflict instead of avoiding it, and keep reconnecting the team back to the shared goal. Healthy disagreement makes the work better; destructive power struggles don't.

Stage 3: Norming. Differences get resolved and a routine forms. Trust rises, communication gets more honest, collaboration improves. You can step back a bit here — celebrate milestones, and keep an eye out for conflicts that have gone underground rather than actually away.

Stage 4: Performing. The team is productive and largely self-directed, holds a strong sense of shared purpose, and people are willing to swap roles and try new approaches. Your job shifts to handing out leadership opportunities, clearing strategic blockers, and spending your own time further out on the horizon.

Stage 5: Adjourning. The project ends and the team disbands or gets reassigned. Feelings run mixed — pride in the work, loss at the ending. You celebrate the achievement, capture what was learned, and help people find their next roles.

In practice, this is never a straight line. Teams jump back and forth between stages, skip stages entirely, and re-enter storming the moment membership, scope, or leadership changes.

Individual members can even sit at different stages at the same time. Treat this as a guide for reading your team, not a rulebook to check off.

Why It Matters for Leaders

As a new manager, you probably assume your job is to drive outcomes and manage operations. The harder, more valuable job is turning a group of people into a high-performing team — and that's a journey with stages, not a single event.

Without this model, you'll read normal stage behavior as a personal failure. Conflict in week six looks like a hiring mistake instead of storming. A quiet, deferential team in week one looks like alignment instead of forming. Get the diagnosis wrong and you'll reach for the wrong fix.

The most common failure sits in storming. Conflict feels like something to smooth over, so you avoid it, and the team stays stuck there. Teams don't norm by waiting it out. They norm by working a disagreement through to an actual decision, out in the open.

The opposite failure lives at the other end. If you kept a team alive through forming and storming by directing hard, you often can't stop directing once the team hits norming or performing. Over-managing a capable team slows it down and drains its motivation.

Knowing the stage also tells you where to spend your own time. In forming, your time goes into clarity and introductions. In performing, it goes into strategy, growth opportunities, and clearing high-level blockers. Same leader, completely different job.

Your chat with Kyoshi about the Tuckman's Stages of Team Development framework

What to do next

Test your knowledge of Tuckman's Stages of Team Development

Take the quiz →

Practice Tuckman's Stages of Team Development

Apply Tuckman's Stages of Team Development to a real situation

Skills related to Tuckman's Stages of Team Development

Frameworks related to Tuckman's Stages of Team Development

Dunning-Kruger Effect

Dunning-Kruger Effect

Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.

Goldilocks Principle

Goldilocks Principle

Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.

Hawthorne Effect

Hawthorne Effect

People change how they behave when they know they're watched — your attention is an intervention that changes what you see.

Maslow's Hierarchy of Needs

Maslow's Hierarchy of Needs

Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.

McKinsey 9-Box Model

McKinsey 9-Box Model

A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.

Multipliers and Diminishers

Multipliers and Diminishers

Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.

Situational Leadership

Situational Leadership

There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.

The 6 Human Needs

The 6 Human Needs

Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.

The Architecture of High-Performing Teams

The Architecture of High-Performing Teams

Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.

The Bannister Effect

The Bannister Effect

One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.

The Five Dysfunctions of a Team

The Five Dysfunctions of a Team

Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.

The Inner Drive

The Inner Drive

A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.

The Pygmalion Effect

The Pygmalion Effect

What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.

The Thomas-Kilmann (TKI) Model

The Thomas-Kilmann (TKI) Model

Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.

Books related to Tuckman's Stages of Team Development

Coaching for Performance

Coaching for Performance

Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.

Elevate

Elevate

Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.

First, Break All The Rules

First, Break All The Rules

A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.

Multipliers

Multipliers

Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.

Team Topologies

Team Topologies

Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.

The Coaching Habit

The Coaching Habit

Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.

The First-Time Manager

The First-Time Manager

The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.

The Five Dysfunctions of a Team

The Five Dysfunctions of a Team

Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.

The Making of a Manager

The Making of a Manager

Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?

The Manager's Path

The Manager's Path

Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.

Turn the Ship Around!

Turn the Ship Around!

A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.