You have been through a reorg. Or your company just acquired another one. Or three teams were merged into one for a new initiative. The people on your team are strangers, or worse, former competitors from rival departments. The org chart says you are a team. The reality says you are a collection of individuals who share a Slack channel and a vague mandate.
This is not the same problem as onboarding a new hire into an existing team. When a whole team forms at once, there is no existing culture to absorb into. Everything must be built from scratch: norms, trust, communication patterns, decision-making processes, and shared identity. The research on team development provides a roadmap, but most managers skip straight to execution and wonder why the team stalls at month two.
Tuckman Applied Practically
Bruce Tuckman's 1965 model of group development (Forming, Storming, Norming, Performing) remains the most widely cited framework for team evolution. A 2024 study of 178 students in collaborative assignments confirmed that teams progress linearly through all four stages, with the performing stage achieving the highest mean performance score (M=4.20) and the storming stage the lowest (M=3.67) (IJRISS, 2024).
The practical problem is that most managers know about Tuckman but do not have a week-by-week plan for guiding the team through each stage. Here is one.
Weeks 1 to 4: Forming
The team is polite, cautious, and deferential to the leader. People are assessing each other: Who is competent? Who is trustworthy? Who has influence? The primary need is clarity and safety.
- Week 1: Establish the team charter. Define the team's purpose, decision-making authority, communication norms, and meeting cadence. Do this collaboratively, not by dictating a document. Research by Hackman found that teams with clear norms established early perform better across the full lifecycle, with team structure accounting for a significant portion of the 74% variance in performance explained by enabling conditions (Leading Change Network).
- Week 2: Run 1-on-1s with every team member. Learn their working style, what motivates them, what they are anxious about, and what they need from you. These conversations build the relational foundation that will carry the team through storming.
- Week 3: Create a shared win. Assign a small, achievable project that requires collaboration. The goal is not the deliverable. The goal is for the team to experience working together successfully. Bandura's research on self-efficacy shows that early success experiences build confidence in the group's collective capability (Bandura, 1997).
- Week 4: First retrospective. Debrief the shared win. What worked? What was confusing? What norms need adjusting? This establishes the reflexive habit early. Teams that debrief improve performance by approximately 25% (Tannenbaum & Cerasoli, 2013).
Weeks 5 to 8: Storming
The politeness wears off. People start pushing back on norms, challenging each other's ideas, and jockeying for influence. This feels like failure but it is progress. Tuckman's original 1965 paper found that only 50% of studied teams exhibited a distinct storming phase, suggesting that some teams skip it by suppressing conflict rather than resolving it. Those teams get stuck.
The manager's job during storming is to normalize conflict and model healthy disagreement.
- Week 5: Address the first conflict directly. When tension surfaces (and it will), name it. "It sounds like there is a disagreement about approach here. Let's hear both perspectives." Research on psychological safety shows that how a leader responds to the first moment of tension sets the tone for the team's entire lifecycle.
- Week 6: Clarify roles and decision authority. Most storming-phase conflict is structural, not personal. People are unclear about who owns what and who decides what. Revisit the charter with specific attention to DACI or RACI frameworks for the team's key decisions.
- Week 7: Introduce structured debate. Assign someone to play devil's advocate on a proposal. This teaches the team that disagreement is a feature, not a bug. Google's Project Aristotle found that teams with high psychological safety (where disagreement is safe) showed 31% more innovation (Amazing Workplaces, 2025).
- Week 8: Second retrospective. Focus on interpersonal dynamics, not just task performance. "How are we working together? What is one thing we could do to make collaboration smoother?"
Weeks 9 to 12: Norming
The team starts settling into patterns. Roles are clearer. Communication flows more naturally. Trust is building. The risk at this stage is complacency: the team starts going through the motions rather than continuing to improve.
- Week 9: Set ambitious goals. Now that the team has a working rhythm, raise the bar. Katzenbach and Smith found that specific, demanding performance challenges are what fuse a team together: "The combination of purpose, performance goals, and mutual accountability becomes the disciplined habit that distinguishes successful teams" (HBR, 1993).
- Week 10: Cross-train. Have team members teach each other their specialties. This builds cognitive diversity awareness and reduces bus factor risk. It also deepens mutual respect by making each person's expertise visible.
- Week 11: Introduce external feedback. Bring in a stakeholder or customer to give the team feedback on their work. External validation (or challenge) strengthens the team's shared identity and sense of purpose.
- Week 12: Third retrospective with a forward look. Review the full 90 days. What worked? What would you do differently if forming a new team again? What are the team's operating norms going forward?
The Fastest Forming-to-Performing Accelerant
The 90-day plan above works. But there is a way to compress the timeline. Research on shared challenge experiences shows that teams who face adversity together early in their formation develop trust faster than teams who only collaborate on routine work. The military has known this for decades: basic training bonds strangers into cohesive units through shared hardship, not shared PowerPoints.
QuestWorks, the flight simulator for team dynamics, applies this principle to workplace teams. A 25-minute quest puts a newly formed group through a shared challenge that requires immediate collaboration: communicating under pressure, making collective decisions, supporting each other through setbacks. The shared experience builds trust in a single session that would take weeks of normal work interaction to develop.
Teams can quest together starting day one of formation. QuestDash surfaces behavioral patterns from the session: who communicated effectively, where coordination broke down, how the group made decisions. Leaders get aggregate trends and strengths-based XP highlights through a weekly team health report. HeroGPT provides private AI coaching in Slack that never shares upstream. Sessions run on its own cinematic, voice-controlled platform with groups of 2 to 5. Slack is the integration layer for install and onboarding.
$20/user/month, 14-day free trial.
A newly formed team that runs a quest in week one and debriefs together has already started building the trust, communication patterns, and shared identity that the 90-day plan targets. The plan still matters. The quest accelerates it.
Try it free
