HKSM

A stage-based model of team development: forming, storming, norming, performing, and adjourning. Project leaders use it to gauge team maturity and select targeted actions that speed the journey to high performance.

Key Points

• Describes predictable stages teams pass through: forming, storming, norming, performing, and adjourning.
• Progress is not strictly linear; teams can regress after changes such as new members, scope shifts, or leadership changes.
• Use observable behaviors and outcomes to identify the current stage, not gut feel alone.
• Leadership style, facilitation techniques, and team-building activities should adapt to the current stage.
• Works for co-located, hybrid, and fully remote teams with attention to different cues.
• Complements tools like the team charter, working agreements, decision frameworks, and coaching.

Purpose of Analysis

• Diagnose the team’s current stage to choose the most effective interventions.
• Set realistic expectations for ramp-up time with sponsors and stakeholders.
• Plan targeted team-building, conflict management, and coaching to reduce delivery risk.
• Support decisions on meeting cadences, decision rights, role clarity, and autonomy.

Method Steps

• Prepare: review the team charter, project goals, and current delivery metrics.
• Observe: note behaviors in meetings, decision clarity, conflict patterns, trust indicators, and collaboration quality.
• Assess: map observed behaviors to a dominant stage while acknowledging overlaps.
• Select interventions by stage:
  • Forming: run a structured kickoff, clarify purpose, roles, and decision-making, and establish working agreements.
  • Storming: facilitate healthy conflict, define decision rights, refine working agreements, and build psychological safety.
  • Norming: stabilize processes, encourage peer accountability, and celebrate small wins.
  • Performing: delegate authority, remove impediments, and protect focus and flow.
  • Adjourning: plan knowledge transfer, recognize contributions, and capture lessons learned.
• Implement: run workshops, coaching sessions, and process tweaks aligned to the stage.
• Monitor: track behavior changes and performance trends; reassess after significant changes.

Inputs Needed

• Team charter, objectives, scope, and success criteria.
• Working agreements, RACI or decision frameworks, and communication plan.
• Observation notes from meetings, retrospectives, and one-on-ones.
• Performance indicators such as throughput, quality trends, predictability, and engagement feedback.
• Stakeholder and customer feedback on collaboration and responsiveness.
• Context changes: onboarding/offboarding, reorgs, policy shifts, or major risks realized.

Outputs Produced

• Updated working agreements and clarified decision rights.
• Refined roles and responsibilities or RACI updates.
• Targeted action items for team improvement and coaching plans.
• Conflict management agreements and meeting facilitation adjustments.
• Recognition and motivation plans aligned to stage.
• Transition and knowledge handover plans when approaching adjourning.

Interpretation Tips

• Forming: polite interactions, uncertainty about goals and roles, dependence on the leader.
• Storming: visible disagreements, competing priorities, unclear decision authority, test of boundaries.
• Norming: emerging routines, shared norms, growing trust, constructive feedback.
• Performing: self-management, high trust, predictable delivery, issues resolved quickly at the team level.
• Adjourning: focus on closure and transition, mixed emotions, reduction in experimentation.
• Subteams may be at different stages; tailor interventions locally while aligning on shared norms.
• For remote teams, watch digital cues such as response times, chat tone, and meeting participation.

Example

A new cross-functional team launches after a reorganization. After the kickoff, meetings become tense and decisions stall. The project manager recognizes storming behaviors and facilitates a workshop to define decision rights, refresh the team charter, and create conflict-resolution rules. Over the next month, routines stabilize (norming), throughput improves, and the team begins self-managing dependencies (performing).

Pitfalls

• Treating stages as labels rather than guides for action.
• Assuming linear progression and ignoring regressions after changes.
• Applying generic team-building instead of targeted interventions.
• Over-facilitating and reducing team autonomy during performing.
• Neglecting onboarding and offboarding impacts on team dynamics.
• Skipping adjourning activities and losing lessons learned or morale benefits.

PMP Example Question

A new cross-functional team is experiencing frequent disagreements about decision rights and priorities after kickoff. To apply the Tuckman ladder and speed progress, what should the project manager do first?

1. Facilitate a session to establish working agreements and clarify roles and decision-making.
2. Assign additional technical training to improve individual competencies.
3. Enforce stricter change control and warn that conflicts will be escalated.
4. Reassign team members who disagree to different projects.

Correct Answer: A — Facilitate a session to establish working agreements and clarify roles and decision-making.

Explanation: The team shows storming behaviors. Clarifying norms, roles, and decision rights helps move to norming and then performing. Training or punitive measures do not address the core team-dynamics issue.