# Team Development after Tuckman: How to Make New Teams Deliver Sooner

Author: Marin Niehues, Niehues Consulting · Published: 2026-03-16 · Updated: 2026-11-16 · Leadership & Teams
Source: https://www.niehuesconsulting.com/blog/tuckman-team-development/

New teams start delivering sooner when leaders shape the Tuckman stages deliberately and fix the goal and roles firmly in the first weeks. The model describes what happens in young teams. Delivery capability comes from the decisions leaders take at each stage.

Every reorganisation, every new product and every AI initiative begins with a team that did not previously exist in that form. The time until this team delivers reliably costs money: the capacity is paid for, the result is still outstanding. Shortening this ramp-up gains weeks in every initiative. The Tuckman model is the best-known frame of reference for it. It is often quoted and rarely used as a leadership tool.

**Teams pass through the Tuckman stages in any case. The difference lies in whether leaders leave them to chance or shorten each stage with clear decisions.**

## What does the Tuckman model say?

The Tuckman model holds that groups grow together in a typical sequence of stages: forming, storming, norming and performing, later extended by adjourning for the end of the team. The psychologist Bruce Tuckman published it in 1965 in the journal Psychological Bulletin. It was based on a review of 50 studies of many kinds of group, from therapy groups to groups in the laboratory. Tuckman described each stage on two levels, the relationships between members and the work on the task. In 1977, together with Mary Ann Jensen, he added the fifth stage in a review of the subsequent literature.

**The five stages and the leader's task**
Forming: members orient themselves and are polite and cautious. The task is still unclear. Leaders clarify purpose and roles along with the expected outcome.

Storming: differing views on the approach and on the distribution of influence collide. Leaders make conflicts about the work discussable and settle open questions quickly.

Norming: the team agrees on ways of working and accountability. Leaders put the agreements in writing and review them regularly.

Performing: the team solves problems independently and delivers reliably. Leaders protect its composition and focus.

Adjourning: the team completes its task or disbands. Leaders secure handover and knowledge.

## What research has added since

The model describes typical patterns and is no timetable. Research in the following decades has refined it in three respects, each of direct use to anyone leading project and delivery teams.

First, the stages do not run strictly in sequence. In 1988 Connie Gersick observed eight project groups from their first meeting to their deadline. The groups held on to their initial pattern of work for a long time and changed it fundamentally almost exactly halfway through the time available. Gersick described this as punctuated equilibrium. The practical consequence: deadlines and interim milestones shape a team's development more strongly than any calendar of stages. A team with an early, genuine interim result reaches a productive rhythm sooner.

Second, a team only learns when its members raise mistakes and objections openly. In 1999 Amy Edmondson studied 51 work teams in a manufacturing company and showed that psychological safety goes hand in hand with learning behavior, and learning behavior with performance. A storming phase conducted openly is therefore a sign of safety. A team that keeps every tension quiet stays stuck in polite orientation.

Third, familiarity is a measurable performance factor. A 2009 study by Robert Huckman and colleagues of software projects at a large Indian IT services firm found that teams whose members had worked together before delivered better results. A 1994 safety study by the US National Transportation Safety Board makes the point even more clearly. Of the major accidents studied for which crew data was available, 73 percent occurred on the first day the captain and first officer flew together.

**What research on team development shows**
50 | studies reviewed by Tuckman in 1965 for his stage model
51 | work teams studied by Edmondson in 1999 on psychological safety
73 percent | of the accidents studied with crew data occurred on the crew's first day together (NTSB, 1994)

## How long does team development take?

A newly formed team with a clear goal and fixed roles reaches a reliable delivery rhythm within eight to twelve weeks, as a benchmark from delivery practice. Without that clarity it stays between forming and storming for months. Duration is measured by characteristics rather than by the calendar: a team is delivery-ready when it keeps its commitments for the next cycle and resolves problems without escalation.

**Checklist: is your team delivery-ready?**
- Can every member state the team's outcome in one sentence, including its metric?
- Is it clear for every recurring decision who takes it?
- Does the team keep its commitments for the next cycle in at least three out of four cases?
- Are objections raised in meetings before they surface in the corridor?
- Does the team resolve conflicts about its approach itself, without escalating to line management?
- Is there a written working agreement that has been reviewed in the last eight weeks?

With four or more yes answers, the team is in norming or performing. With two or fewer it is in forming or storming, and leaders should start with the goal and decision rights.

## Making new teams deliver sooner

The most effective levers lie before the first working day and in the first two weeks. For each stage there is a leadership decision that shortens it.

**Shorten forming with a team launch.** In a one-day kick-off workshop the team agrees a team charter. It covers purpose, measurable outcome, roles and decision rules, together with the working rhythm and the definition of when a task counts as done. A first small deliverable after two to three weeks gives the team the early turning point Gersick described.

**Contain storming with clear decision rights.** Most conflicts in young teams revolve around influence and responsibility. They lose their sting when it is settled in advance who decides on priorities and who on technical questions. Conflicts about the work are discussed openly in retrospectives. Conflicts that turn personal are moderated early by the leader, before they escalate. How to recognize the stages of escalation is covered in the article on [conflict escalation after Glasl](/blog/glasl-conflict-escalation-model/).

**Consolidate norming with reviewed agreements.** Working agreements work when they are short and reviewed regularly. One page of rules, for example on availability and handovers, is enough if the team checks it briefly in every retrospective.

**Sustain performing through stability.** A high-performing team quickly loses that level when members are pulled away or allocated to many initiatives in parallel. Leaders protect the composition and limit the amount of parallel work. Which factors determine team performance over time is shown in the article on [building high-performance teams](/blog/building-high-performance-teams/).

**Plan adjourning.** When an initiative ends, a planned handover secures operations and knowledge. If the team stays together as a unit and takes on the next task, the entire ramp-up for the follow-on initiative disappears.

## Which mistakes prolong team development?

Team development is prolonged mainly by frequent changes in membership, by teams that are too large and by members who contribute only small fractions of their time. Each of these mistakes pushes the team back towards orientation.

- **Restaffing as a rescue attempt:** in 1975 Frederick Brooks formulated the rule for software projects that adding people to a late project makes it later. New members need onboarding, and existing members lose time to coordination.
- **Teams that are too large:** with every additional member the number of relationships in the team grows disproportionately. The 2020 Scrum Guide gives ten or fewer people as its guideline.
- **Split membership:** someone spread across three teams belongs to none of them. Core members should spend at least half their time in the team.
- **A goal without a metric:** without a measurable outcome there is no yardstick for settling conflicts about priorities.

Every new member changes the group, and the team briefly returns to forming and storming. Structured onboarding with a fixed contact person shortens this return considerably, as the article on [onboarding as a productivity lever](/blog/onboarding-productivity/) describes.

**Three ways to set up a new team**
Criterion | Leaving the team to itself | Team-building event | With Niehues Consulting
Goal and outcome | Emerges in the course of work | Formulated in general terms | Measurable outcome fixed before the start
Roles and decision rights | Emerge from conflict | Not addressed | Set out in the team charter
First deliverable | Open | Open | Planned in the team charter as an early interim result
Handling conflict | Unmoderated | Atmosphere improves, causes remain | Causes resolved through responsibility and goal
Measurement | None | Satisfaction with the event | Commitment reliability and cycle time per iteration

## What does Tuckman mean for cross-functional teams and AI initiatives?

For cross-functional teams and AI initiatives, the model means that clarifying roles and decision rights before the start matters even more than in teams from a single discipline. Business experts and data specialists each bring their own vocabulary and time horizon, and IT adds another. Storming arises here over who decides on business requirements and who on technical implementation. A product owner from the business with a clear mandate shortens this stage most effectively. Prerequisites and typical pitfalls are covered in the article on [introducing cross-functional teams](/blog/cross-functional-teams-prerequisites-and-pitfalls/).

## Niehues Consulting as your partner for teams that deliver

[Niehues Consulting](/) sets teams up to deliver early and supports them until they reach a reliable rhythm. Marin Niehues works as delivery manager, project manager or product owner and combines organization design with day-to-day delivery. He is a management consultant with a delivery perspective, with projects ranging from VC-backed scale-ups to DAX 40 groups, in 20+ countries on six continents.

The approach follows the Niehues Delivery Model with its phases Understand, Build and Embed. Two of its review questions matter most when setting up new teams. Who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? A team that has answered both questions in its first week shortens forming and storming markedly. How structure and delivery work together overall is described in the article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/). The starting point is a free 30-minute initial consultation via [the contact page](/#kontakt).

**Ramp-up time is a leadership task**
The Tuckman model describes what happens in young teams. A team becomes delivery-ready sooner when the goal and decision rights are fixed before the start, an early interim result sets the rhythm and leaders keep the composition stable.

**Sources**
- Tuckman: Developmental sequence in small groups, Psychological Bulletin, 1965
- Tuckman, Jensen: Stages of small-group development revisited, Group & Organization Studies, 1977
- Gersick: Time and transition in work teams, Academy of Management Journal, 1988
- Edmondson: Psychological safety and learning behavior in work teams, Administrative Science Quarterly, 1999
- Huckman, Staats, Upton: Team familiarity, role experience, and performance, Management Science, 2009
- National Transportation Safety Board: A Review of Flightcrew-Involved Major Accidents of U.S. Air Carriers, 1978 through 1990, Safety Study, 1994
- Brooks: The Mythical Man-Month, 1975
- Schwaber, Sutherland: The Scrum Guide, 2020

## Frequently asked questions

### What are Tuckman's stages of team development?

The stages are forming, storming, norming and performing, with adjourning added in 1977. They describe the path from orientation through the struggle over goals and influence to agreed ways of working. Independent performance follows, and at the end the team disbands.

### Is the Tuckman model scientifically valid?

The model is based on a review of 50 studies and describes typical patterns reliably. Later research shows that the stages do not run strictly in sequence and that deadlines strongly shape development. It works well as a frame of reference for leaders and poorly as a timetable.

### Can a team skip the storming stage?

A team cannot skip storming, but it can shorten it markedly. Conflicts over goals and responsibilities can be pre-empted when these points are decided before the start. A team with no friction at all usually keeps objections to itself and learns more slowly.

### What happens when a new member joins the team?

With every new member the team briefly returns to forming and storming, because roles and influence are rearranged. Structured onboarding with a fixed contact person and a review of the team charter shorten this phase.

### How can you tell which stage a team is in?

The stage shows in observable behavior. Cautious politeness and many questions point to forming, recurring debates of principle to storming, the team's own working rules to norming, and commitments kept without escalation to performing.

### What is the ideal team size?

A delivery team should have ten or fewer members, which is also the guideline in the Scrum Guide. Every additional person increases coordination effort disproportionately, so larger initiatives are split across several small teams with clear interfaces.

### What is the leader's role in each Tuckman stage?

The leader provides direction and structure in forming, moderates conflict and settles open questions in storming, consolidates agreements in norming and protects focus and composition in performing. As the team matures, the role shifts from steering to safeguarding the conditions for work.

### What is a team launch workshop?

A team launch workshop is a kick-off, usually lasting one day, in which a new team agrees its team charter. It produces the purpose and measurable goal, plus the roles with their decision rules and the working rhythm. It is the single most effective lever for shortening forming.
