Mastering Forming Storming Norming Performing Adjourning

A team launches with energy, a kickoff deck, and a clear deadline. Two weeks later, people are talking past each other, work is getting duplicated, one manager is chasing updates in Slack, and someone is already frustrated about time off because nobody knows who can cover. That pattern is common in small and midsize companies, especially when a team is cross-functional and moving fast.

Most leaders read that kind of friction as underperformance. In practice, it's often the early life of a team. The useful question isn't “Who's failing?” It's “What stage is this team in, and what does it need right now?” That's where the forming storming norming performing adjourning model becomes practical. It gives managers a way to diagnose behavior, adjust leadership, and use modern HR systems to reduce avoidable friction around coverage, policy questions, and workload.

Why Your New Team Is Underperforming

A familiar example looks like this. Sales wants speed, operations wants consistency, HR wants policy clarity, and the founder wants all of it by Friday. The team is new, the goals sound aligned, and everyone is polite in the first meeting. Then deadlines slip because nobody is sure who owns approvals, who decides priorities, or how leave coverage works when two key people are out on the same day.

That isn't random. Bruce Tuckman introduced Forming, Storming, Norming, and Performing in 1965 as a framework for understanding how groups develop through role ambiguity, conflict, cohesion, and execution, according to the historical overview of Tuckman's stages. The reason managers still use it is simple. It explains why early discomfort is normal.

Misreading friction creates bigger problems

New managers often make one of two mistakes.

• They overreact to tension: They shut down disagreement too early, which pushes conflict underground.
• They under-manage ambiguity: They assume smart people will “figure it out,” which leaves roles, workflows, and decision rights fuzzy.

Both choices slow a team down.

Practical rule: Early friction usually means the team needs more clarity, not more pressure.

The model matters because it shifts your response. Instead of treating conflict, hesitation, or duplicate work as personal failure, you treat them as signals. If the team is still forming, they need structure. If they're storming, they need managed conflict, not forced harmony. If they're norming, they need reinforcement. If they're performing, they need protection from overload. And if they're adjourning, they need a clean close, not an abrupt handoff.

That lens helps managers stop diagnosing every rough patch as a people problem. Often, it's a stage problem.

The Five Stages of Team Development at a Glance

The full version of the model covers the whole team lifecycle, not just the productive middle. Tuckman and Mary Ann Jensen added Adjourning in 1977, which turned the framework into a five-stage lifecycle and made it more useful for project-based work where teams form and disband, as explained in this overview of the five-stage model.

What each stage looks like

Stage Team Behavior Manager's Focus Forming People are polite, cautious, and unsure about roles Set goals, clarify roles, define boundaries Storming Disagreements surface around priorities, ownership, and process Facilitate conflict, make decisions explicit, reduce avoidable friction Norming The team agrees on ways of working and starts to trust the process Reinforce norms, share ownership, support consistency Performing People operate with confidence and less supervision Remove blockers, protect focus, watch for overload Adjourning Work wraps up and the team starts disengaging from the project Capture learning, recognize contributions, hand off knowledge

The manager's role changes at every stage

This is what many leaders miss. The same management style won't work across the full cycle.

In forming, the team needs direction. In storming, they need containment and fairness. In norming, they need support for the habits that are starting to work. In performing, they need room to operate without unnecessary approval layers. In adjourning, they need structure again, this time for closure rather than setup.

Teams rarely struggle because the model is wrong. They struggle because the manager keeps using the leadership style that fit the previous stage.

A leave calendar, approval workflow, or policy knowledge base won't solve team dynamics on its own. But the right systems reduce ambiguity at the moments when ambiguity does the most damage. That's why tooling belongs in the conversation from the start.

Your Playbook for the Forming and Storming Stages

The earliest stages need the most visible management. People are still figuring out the work, the relationships, and the unspoken rules. If you're too hands-off here, the team fills the gaps with assumptions.

Research on team development describes forming as a stage where members are ambiguous about roles and avoid conflict, while storming is marked by explicit disagreement, frustration, and role conflict. It also notes that the performance dip is a predictable transition cost as the group defines its structure, according to this NIH discussion of group development.

What to do in forming

In forming, don't aim for inspiration first. Aim for orientation.

A manager's first job is to remove avoidable uncertainty. That means answering practical questions quickly: Who owns what? How will decisions get made? Which requests need approval? What happens if a key person is out? Where do people find policy answers without waiting on HR?

Use a short operating charter. Keep it simple enough that people will read it.

• Name the mission: State what the team is responsible for and what sits outside its scope.
• Assign decision rights: Be explicit about who recommends, who approves, and who executes.
• Set communication rules: Decide where updates live, when escalation happens, and what requires a meeting.
• Clarify leave and coverage: Show how time-off requests affect scheduling, deadlines, and backup ownership.

Most forming-stage confusion shows up in small operational moments. Someone books leave during a critical handoff. Another person assumes coverage exists when it doesn't. A new employee has a policy question and asks three different people, then gets three different answers. Those frictions don't feel strategic, but they shape trust fast.

What not to do in forming

Avoid the common manager move of saying, “Let's stay flexible.” Flexibility without structure creates politics. The most assertive people start defining the rules by habit, and quieter team members adapt around them.

Also resist overloading kickoff meetings with values language while skipping logistics. Teams bond faster when the basics work.

A useful support for this stage is manager training on conflict signals and role clarity. If you're seeing tension early, it helps to review practical methods for handling conflict at work before disagreements harden into personal narratives.

How to handle storming without panicking

Storming begins when people stop being polite enough to stay vague. That's progress, even when it feels messy.

The wrong response is trying to eliminate conflict. The better response is to structure it. Ask people to argue about work in visible ways, with evidence, trade-offs, and clear decisions. Don't let conflict sprawl into side channels.

Use this sequence when the team enters storming:

• Surface the actual dispute: Is this about goals, roles, process, or workload?
• Separate preference from policy: Some disagreements need judgment. Others need one clear rule.
• Decide in public: If you make the call privately, the team keeps debating the missing context.
• Record the outcome: Capture responsibilities, deadlines, and fallback coverage.

Here's a practical midpoint check that often settles unnecessary conflict: open the team calendar, the leave schedule, and the project deadlines at the same time. Half of what sounds like interpersonal friction is really unplanned dependency risk.

A short explainer can help reset the team before discussion gets abstract.

“Conflict in storming is useful only if the team leaves with clearer roles and better decisions.”

When managers do this well, the team doesn't avoid storming. They move through it faster because the disputes become specific, bounded, and actionable.

How to Accelerate Through Norming to Performing

Norming starts when the team no longer has to negotiate every interaction. People know how work moves, who covers what, and how to raise a problem without creating a drama loop. The manager's job changes here. You stop being the primary source of structure and start reinforcing the structure the team is building together.

How norming becomes real

Norming isn't team harmony. It's repeatability.

You can tell a team is entering this stage when fewer decisions need manager intervention and more work gets resolved through agreed routines. Handoffs are cleaner. Meetings are shorter. People stop relitigating every request because they know the process.

At this point, managers should codify what's working.

• Document working agreements: Turn informal habits into visible team norms.
• Build predictable coverage: Use shared calendars so approved leave is visible where the team already works.
• Create backup ownership: Every critical process should have a clear secondary owner.
• Keep one-on-ones focused: Don't use them only for status updates. Use them to spot friction before it spreads.

A strong one-on-one rhythm becomes more valuable here because the team looks smoother from the outside than it may feel internally. If managers need a structure for those conversations, a practical one-on-one meeting agenda helps keep discussions focused on workload, blockers, and support needs rather than generic check-ins.

Reduce administrative drag

Norming often stalls when operational friction keeps interrupting the team. Managers think the team has a culture problem when the actual problem is that basic coordination still depends on memory and manual chasing.

Examples include:

Friction point Better operating habit Leave requests arrive without context Review requests with team availability and overlapping absences visible People ask policy questions in chat Route answers through a consistent policy source Coverage gets arranged informally Assign backup owners in advance Calendars don't reflect approved leave Sync approved time off automatically to team calendars

The point isn't software for its own sake. The point is reducing the number of tiny uncertainties that pull the team backward into storming.

What performing actually requires

Performing is the stage managers want, but many teams reach it briefly and then lose it because nobody protects it. High-performing teams don't just work hard. They operate with confidence, autonomy, and enough slack to absorb normal disruption.

That means the manager's role becomes selective. Intervene less often, but intervene earlier when signs of overload appear. Watch for patterns such as repeated last-minute coverage scrambles, key people avoiding time off, or one reliable employee becoming the default backup for every urgent task.

Manager check: If the team can deliver without you in every decision, but can't take leave without causing stress, they're not performing yet. They're overextended.

Sustain output without burning people out

Modern HR tooling proves most vital. Calendar syncs reduce surprise absences. Approval workflows reveal coverage risks before time off is granted. Absence histories and summaries can highlight patterns that deserve a human conversation, especially when a normally steady employee starts taking scattered days off or repeatedly delays rest.

A performing team also needs clear permission to recover. Good managers don't only ask, “Can we cover this leave request?” They also ask, “What happens if we keep postponing rest because this person feels indispensable?” That's how burnout starts in growing teams.

Use a simple cadence:

• Weekly: Review upcoming absences against deadlines and handoffs.
• Monthly: Look for recurring workload pressure points and overloaded roles.
• Quarterly: Reconfirm whether team norms still fit the work, especially after scope changes.

Performing isn't a reward the team earns once. It's a condition you maintain by keeping work visible, coverage planned, and recovery normal.

Managing the Adjourning Stage with Purpose

Many teams finish strong and then close badly. The project ends, people roll to new work, and nobody captures what should happen next. That creates two losses at once. The company loses knowledge, and the team loses closure.

The adjourning stage matters because it involves the termination of task behaviors and disengagement from relationships, not just the final due date. Best practices include capturing lessons learned, formally recognizing accomplishments, and ensuring knowledge transfer, according to this explanation of adjourning and team closure.

Treat closeout like real work

Managers often protect kickoff time but neglect wrap-up time. That's backwards. The closing phase determines what the next team inherits.

A useful adjourning checklist includes:

• Document decisions: Record what was built, changed, approved, and deferred.
• Transfer ownership: Make it explicit who now owns ongoing tasks, support, or maintenance.
• Capture lessons learned: Note what slowed the team down and what made work easier.
• Recognize contributions: Thank people specifically, not with a generic wrap-up note.
• Confirm next assignments: Reduce uncertainty about where team members are going next.

Closure matters in distributed teams

Remote and hybrid teams are especially vulnerable to weak adjourning. When people don't share a physical office, endings get compressed into a final call and a few Slack messages. That may feel efficient, but it leaves loose ends everywhere.

Use a formal final review with documented outputs. Include staffing assumptions, leave coverage lessons, policy exceptions that came up during the project, and any operational fixes the next team should adopt. If people are rolling immediately onto another assignment, a short transition brief is often more useful than a long retrospective.

A team that closes cleanly starts the next project faster because it doesn't have to rediscover its own lessons.

Adjourning isn't sentimental management. It's operational discipline.

How Smart HR Tools Support Team Development

Team development is often treated as a soft-skills topic. In real organizations, it's also a systems topic. Teams move faster when managers can answer policy questions, review leave requests with context, and spot coverage risk before it becomes conflict.

Stage-by-stage support from modern systems

In forming, the biggest need is clarity. A policy assistant or searchable knowledge base helps new team members get consistent answers on eligibility, balances, carryover, and leave rules without waiting for HR. That reduces ambiguity before it turns into frustration.

During storming, managers need context. Leave approvals become much easier when the request sits next to team availability, overlapping absences, and minimum coverage concerns. That changes the conversation from “Why was my request denied?” to “Here's the coverage issue we need to solve.”

In norming, automation reduces drag. Shared calendar syncs mean approved leave appears where the team already plans work. Balances and approval histories live in one place, which cuts back on side messages and informal exceptions.

In performing, reporting matters more than administration. Monthly summaries, payroll-ready exports, and trend visibility help managers see where workload concentration may be building. You still need judgment, but you're no longer managing by memory.

In adjourning, records matter. Staffing history, absence context, and handoff documentation help the next team understand what happened and what needs continuity.

One example of a tool in practice

One option is AI-powered HR solutions from Redstone HR, which centralize PTO, sick leave, approvals, policy answers, calendar sync, and reporting in one system. In a growing company, that kind of setup helps managers handle everyday team friction with more consistency because employees can self-serve basic policy questions and managers can review requests with coverage context rather than guesswork.

That doesn't replace management. It supports better management.

Use a simple test when evaluating tools for the forming storming norming performing adjourning lifecycle:

• Can employees get policy answers without creating HR bottlenecks?
• Can managers see coverage risk before approving leave?
• Does the tool sync with calendars and communication systems the team already uses?
• Can HR export clean records for payroll, compliance, and project closeout?

If the answer is yes, the system is doing more than administration. It's helping the team move through each stage with fewer preventable setbacks.

What to Do When Your Team Gets Stuck or Moves Backward

A team doesn't move through these stages once and stay there. Team development is not always linear, and teams may move backward or cycle again when goals, membership, or leadership change, as noted by MIT Human Resources on stages of team development.

That matters because regression is normal after a reorg, a new manager, a major scope shift, or even one key new hire.

A quick reset for stalled teams

If the team is stuck in storming, don't schedule a motivational offsite first. Re-establish working agreements, decision rights, and coverage rules. In such situations, teams benefit from less inspiration and more clarity.

If a performing team slides backward after adding someone new, run a mini-onboarding plan for the team, not just the hire. Reconfirm roles, communication norms, backup ownership, and leave approval expectations. Existing teams often regress because the old rules were never written down.

Use the model as a diagnostic tool. Ask what changed, what became ambiguous, and what the team now needs from management.

Redstone HR helps growing teams manage the operational side of team development with clearer leave policies, approval context, calendar sync, and cleaner handoffs. If your managers are still juggling coverage and policy questions through spreadsheets and chat, Redstone HR is worth a look.