JH
Jonathan Haber

Adjourning: close the team with intention

How a team ends shapes how each member begins the next one.

Key takeaways

  • What it is: How a team ends shapes how each member begins the next one.
  • Why it works: Teams that dissolve without closure — through project cancellation, reorganization, or simple silence — leave members with unresolved group experience that can carry into the next team as distrust or disengagement. Intentional closure acknowledges the shared work, surfaces what was learned, and signals that the relationships have real value.
  • Evidence: Plausible mechanism, limited direct outcome data.
  • Avoid: Letting the team quietly disperse when the project ends — no retrospective, no acknowledgment — which leaves learning on the table and people feeling disposable.

Why it works

Teams that dissolve without closure — through project cancellation, reorganization, or simple silence — leave members with unresolved group experience that can carry into the next team as distrust or disengagement. Intentional closure acknowledges the shared work, surfaces what was learned, and signals that the relationships have real value.

How to do it

  1. 1Schedule a retrospective that covers both what the team built and how it worked together.
  2. 2Explicitly name what individuals contributed so the recognition is specific, not generic.
  3. 3Capture lessons-learned in a document that travels with the people, not just the project.

What the evidence says

Mechanistic

Psychological research on group endings (Tuckman added this stage in 1977) and grief literature both support the idea that unprocessed endings generate residual attachment responses that affect future engagement.

Honest caveat: The psychological impact of team dissolution is under-studied empirically; the mechanism is plausible from broader group dynamics and transition research.

References
  • — Tuckman, B. W. & Jensen, M. A. C. (1977). Stages of small-group development revisited. Group & Organization Studies, 2(4), 419–427.

Common mistake

Letting the team quietly disperse when the project ends — no retrospective, no acknowledgment — which leaves learning on the table and people feeling disposable.

IX Coach guides you through a structured closing session — what to say, what to ask, and how to make the ending feel like a real completion rather than a stop.

Practice this with IX Coach →

Related practices