---
name: forming-storming-norming-performing
description: Use when asked to explain or apply Tuckman's stages of group development — Forming, Storming, Norming, Performing — as a non-linear model for understanding where a team currently stands, not a fixed sequence every team must complete once.
---

# Forming, Storming, Norming, Performing

Forming, Storming, Norming, and Performing (FSNP) is a model of group
development, created by psychologist Bruce Tuckman, describing four
stages teams commonly move through as they develop from a set of
individuals into a functioning, high-trust team.

## The four stages

- **Forming** — team members get to know each other and start
  understanding their roles and responsibilities; typically marked by a
  mix of excitement and anxiety as everyone is new to each other and to
  the team's purpose. See [[icebreaker-questions]] for a concrete
  tool to support this stage.
- **Storming** — conflicts and disagreements start to surface as members
  challenge each other's ideas and ways of working, and may challenge the
  team's leader or its stated goals; an uncomfortable but often necessary
  stage rather than a sign of failure.
- **Norming** — the team starts to come together, establishing norms and
  rules for how they'll work together, and beginning to develop a shared
  sense of identity.
- **Performing** — the team becomes fully functional, working
  effectively together with high levels of trust and collaboration — the
  stage most people picture when they imagine "a good team."

## It is not strictly linear

A team can move back and forth between stages, skip a stage, or plateau
in one — a change in membership, a new project, or a significant
conflict can send a team that had reached Performing back into Storming.
Treating the model as a one-way, one-time sequence misreads what Tuckman
actually described.

## Why it's useful

Naming the stage a team is currently in gives a shared vocabulary for
what's happening — recognizing "we're in Storming" reframes friction as
an expected, temporary phase rather than a sign the team is failing,
and points toward what the team needs (clearer norms, better
facilitation) rather than blame.

## Common pitfalls

- **Treating the stages as strictly linear and one-time** — assuming a
  team that reached Performing will stay there regardless of membership
  or project changes misses the model's actual dynamics.
- **Treating Storming as a problem to suppress** — conflict during
  Storming is often a necessary part of establishing real trust and
  clarity; papering over it rather than working through it can leave a
  team stuck.
- **Skipping deliberate norm-setting** — assuming a team will
  automatically progress from Storming to Norming without any deliberate
  facilitation (see [[agile-reflection]]
  for tools that support this) can leave conflict unresolved instead of
  transformed into working norms.
- **Using the model to label people rather than the team's current
  state** — FSNP describes group dynamics, not a permanent judgment about
  individual team members.

## Learn more

- Bruce Tuckman, "Developmental Sequence in Small Groups" (1965) — the originating research.
- [[icebreaker-questions]] for a Forming-stage tool.
- [[agile-reflection]], [[ways-of-working]] for ongoing team-development practices relevant across all four stages.