team-lifecycle

name

team-lifecycle

description

Use when a team is going through a transition — forming (new team), storming (conflict emergence), norming (establishing ways of working), performing (high function), or adjourning (team disbandment/transition). Also for resets after reorgs, new member integration, or when a team is stuck in a dysfunctional phase. Trigger phrases include "our team is changing", "new team member joining", "team reorg transition", "how do we reset our team", "team dissolving", "adjourning a team". Based on Tuckman's model applied to work teams with practical guidance for each phase. Complements team-charter, team-check-in, and stakeholder-manage.

Team Lifecycle Management

Guide a team through its natural lifecycle transitions: Forming → Storming → Norming → Performing → Adjourning, with specific interventions for each phase. Also covers resets after reorgs, new members, major scope changes.

Why this matters: Teams don't start at high performance and they don't stay there automatically. Each phase has characteristic challenges. Understanding the phase helps the leader provide the right support at the right time. A forming team needs different leadership than a performing team needing a reset.

When to apply

Trigger this skill when:

• A new team is created (new product, new group of people)
• The team is in conflict and seems stuck ("storming" phase symptoms)
• The team has settled into routines but isn't elevating performance ("norming" plateau)
• A high-performing team is being disrupted (new member, new leader, new strategy)
• A team is being dissolved or significantly downsized ("adjourning")
• After an org reorg — teams reshuffled, new reporting lines, new mission
• Key member leaves or joins — how to integrate smoothly
• The user says: "We can't seem to get past arguing about process" (storming) or "We're good but we've plateaued" (norming→performing transition)

Skip when:

• The team is clearly in the performing stage and stable (no intervention needed)
• The transition is purely administrative (name change only, no substance change)

The five phases — characteristics and leader actions

Phase 1: Forming — "Who are we and why are we here?"

Team state: Polite, tentative, dependency on leader for direction. High uncertainty about purpose, roles, boundaries. People testing limits.

Leader's job:

• Provide clear purpose and direction (use team-charter)
• Reduce ambiguity: who's on the team, what's the mission, what are the boundaries
• Structure early interactions (kickoff meetings, clear initial tasks)
• Be highly available and directive initially

Symptoms of incomplete forming:

• "I don't know what my job is"
• "What are we supposed to be doing this quarter?"
• "Who decides X?"
• Too many questions, too little action

Skill intervention: Run team-charter immediately. Set the foundations explicitly.

---

Phase 2: Storming — "I don't like how you work"

Team state: Conflict emerges. Roles clash. Disagreements about goals, priorities, processes. Power struggles. Sub-teams form. Some成员 withdraw, some dominate.

Leader's job:

• Normalize conflict as part of team development (it's not a failure, it's a phase)
• Facilitate difficult conversations about roles, norms, decision rights
• Ensure psychological safety so conflict stays task-focused, not personal
• Mediate when conflict becomes destructive
• Reinforce team identity over sub-group identity

Symptoms of storming:

• "Bob never includes me in decisions"
• "Our meetings are a waste of time"
• "Carol and Dave are at each other's throats"
• "I don't trust her to do her part"
• Side-channel complaints, not surface-level resolution

Skill intervention:

1. Run team-style-inventory to surface style mismatches fueling conflict
2. Run team-check-in with focus on roles/norms gaps
3. Use team-charter to reset agreements if they were never clear
4. read-the-room on a contentious meeting to understand subtext
5. If interpersonal: feedback-frameworks for specific feedback; coaching-mode for development conversations

Do not: Avoid the conflict, let it fester, or "wait it out" without intervention — storming that isn't resolved calcifies into permanent dysfunction.

---

Phase 3: Norming — "We've figured out how to work together"

Team state: Roles clarified. Norms established. Conflict reduced (sometimes too reduced — harmony over truth). Team identity solid. Increased cohesion, cooperation, trust.

Leader's job:

• Document the implicit norms that have emerged (team-charter update)
• Guard against premature harmony — ensure dissent is still welcome
• Strengthen team processes (meetings, decisions, information sharing)
• Focus on team effectiveness, not just comfort
• Start introducing stretch goals to test the norms

Symptoms of norming:

• "Our meetings run smoothly"
• "We know who does what"
• "We have a rhythm"
• But: "We don't challenge each other anymore" or "We've stopped arguing about the right things"

Skill intervention:

• team-charter to document the settled norms
• team-check-in at longer cadence (6–8 weeks)
• Introduce challenging work that stretches the team's capability to avoid plateau
• patterns-watch for the individual members — are they growing or coasting?

---

Phase 4: Performing — "We're a high-performing team"

Team state: High autonomy. Strong trust. Effective processes. Focus on external goals, not internal relationship management. Can handle complex, ambiguous work. Role flexibility — people step outside formal roles as needed.

Leader's job:

• Delegate aggressively; stay out of the way
• Protect the team from external disruption
• Ensure strategic direction remains clear
• Invest in team development (skills, tools, relationships)
• Plan for succession and continuity
• Guard against burnout (high performance teams work too hard)

Symptoms of performing:

• "We know what we're doing"
• "We handle problems without escalating"
• "We finish each other's sentences"
• "We're in flow most of the time"
• External stakeholders praise the team's output

Skill intervention:

• team-check-in less frequently (8–12 week cadence) but keep it — performing teams still drift
• team-close-gap for specific process improvements
• wins-log for team achievements
• psychological-safety check-ins to ensure safety hasn't eroded with success
• report-career-architect for individual growth plans — performing teams need individual growth to sustain

Warning: Performing teams can become insular, resistant to new members, over-confident. Inject new perspectives occasionally.

---

Phase 5: Adjourning — "This team is done"

Team state: Work completed or cancelled. Team解散 or significantly restructured. Members transition to new assignments. Emotional processing — loss, uncertainty about next role.

Leader's job:

• Acknowledge the ending; celebrate achievements
• Help members transition to new roles/teams
• Capture learnings before people disperse
• Document work for successors
• Support emotional closure (especially for long-tenured teams)

Symptoms of unmanaged adjourning:

• "What happens to me now?"
• "All our work is lost"
• "No one thanked us for what we did"
• Knowledge loss, no handoff

Skill intervention:

• Run a final team-check-in focused on "what did we learn?" and "what should we carry forward?"
• Use stakeholder-manage to archive team-as-stakeholder relationships if the team is dissolving
• Document key decisions in decision-log for future reference
• wins-log team achievements
• report-career-architect for members' next roles if manager-led

---

Resets and re-entry

Sometimes a team doesn't start fresh but needs a reset — going backwards or sideways to re-establish foundations.

Reset triggers

• New member joins (return to partial forming)
• New leader (team revisits purpose, norms)
• Scope change significant (>20% shift)
• Major conflict that broke trust
• Missed major commitment

Re-entry mapping (where do we go?)

• New member → Forming (add person to existing team; may regress to Storming briefly)
• New leader → Forming (new direction; re-charter recommended)
• Major scope change → Revisit Charter (Update Goals; Roles may adjust; Norms may need changes)
• Major conflict → Storming → run conflict resolution, then re-norm via team-check-in
• High performer → Adjourning → focus on transition, not performance

Skill guidance: If reset impact is major (new leader + new scope), treat as re-forming: run team-charter anew. If minor (one new member), run team-check-in with focus on integration questions.

Practical toolkit by phase

Forming toolkit

• team-charter — establish goals/roles/norms explicitly
• user-profile for team lead — set leadership tone
• strategy-doc if team owns a product area — link team goals to product strategy
• stakeholder-register for key external contacts

Storming toolkit

• team-style-inventory — surface style mismatches
• read-the-room — diagnose meeting dynamics
• feedback-frameworks — structure difficult conversations
• coaching-mode for leader coaching members
• psychological-safety assessment and building
• team-check-in with conflict-resolution focus

Norming toolkit

• team-charter — document settled norms
• team-check-in — regular cadence maintenance
• patterns-watch — watch for stagnation signals
• leadership-os for leader self-reflection on team state

Performing toolkit

• team-close-gap — targeted process improvements
• wins-log — capture team achievements
• report-career-architect — individual growth to sustain team
• influence-without-authority if team needs to work across org

Adjourning toolkit

• wins-log (team retrospective format)
• stakeholder-manage (archive relationships)
• report-career-architect (transition planning for members)
• team-check-in format adapted for retrospective

The team lifecycle checklist

Forming: [ ] Purpose clear? [ ] Roles assigned? [ ] Norms explicit? [ ] First win achieved? Storming: [ ] Conflict surfaced? [ ] Style differences understood? [ ] Roles clarified? [ ] Safety established? Norming: [ ] Charter documented? [ ] Cadence set? [ ] Processes stable? [ ] Dissent still welcome? Performing: [ ] Autonomy high? [ ] External focus? [ ] Growth plans in place? [ ] Succession ready? Adjourning: [ ] Achievements celebrated? [ ] Learnings captured? [ ] Transitions supported? [ ] Archive complete?

Operating principles

• Phases are not linear. Teams cycle back: performing team gets new member → storming again (briefly). Normal.
• Leader's role shifts. Forming: directive. Storming: facilitator. Norming: coach. Performing: delegator. Adjourning: supporter.
• Don't skip storming. Teams that suppress conflict achieve harmony without trust — fragile.
• Psychological safety is the enabler across all phases. Without it, storming becomes toxic, norming becomes superficial, performing unsustainable.
• Charter early, check-in often. The 3X3 loop (charter → check-in → close-gap) is the engine that keeps a team from regressing.
• Adjourning matters. Unmanaged endings poison future teams; managed endings build reputation and learning.

Composition with other skills

• team-charter — primary tool for Forming and Resets
• team-check-in — primary tool for Norming and Performing maintenance
• team-close-gap — turns check-in diagnoses into action during any phase
• team-style-inventory — particularly valuable in Storming (style conflicts surface)
• psychological-safety — prerequisite if safety is low; can be run during Storming or as preventative in Forming/Norming
• stakeholder-manage — if team boundaries change (new stakeholders added/removed)
• report-career-architect — for team members during Adjourning transition
• wins-log — capture team wins in Performing phase; retrospective in Adjourning

Anti-patterns to flag

• Forming leader absent. "Go figure it out" → chaos, storming without direction
• Storming avoidance. Leader suppresses conflict to keep peace → unresolved tension, passive-aggression
• Norming complacency. "We're fine" → plateau, no improvement, stagnant skills
• Performing micro-management. Leader won't delegate → team dependency, burnout
• Adjourning neglect. "We just disband" → knowledge loss, morale drop, no learning captured
• Phase rigidity. "We're a storming team" (self-fulfilling label) — phases describe behavior, not identity
• Ignoring team size. Small teams (3–4) cycle phases faster; large teams (10+) may have sub-teams at different phases