2.4Team cohesion & dynamics
The essentials in 30 seconds
- Tuckman: forming, storming, norming, performing — each stage needs support.
- Foundation: trust + psychological safety: speaking up, proposing, erring without fear.
- Reflex: cohesion does not mean no disagreement, but debating then moving forward together.
Running mini-case — bonding Salim's team
After the Karim / Lina conflict, the team is tense: everyone works in their corner, nobody dares flag mistakes. Salim understands his team is in the "storming" phase (Tuckman): normal, but to support. He sets up common rules, a mutual-help ritual and a displayed right to err to rebuild trust.
This same case returns in the course, the diagram, the script and the 48h challenge.
1. A team is built (Tuckman)
A team is not a sum of individuals: it is a dynamic. Tuckman's model describes 4 stages: forming (discovering each other), storming (confronting each other — this is where Salim's team is), norming (finding its rules), performing (producing together). Knowing where you are helps support rightly: frame in forming, arbitrate in storming, empower in performing.
Like dough that rises: the storming phase matures, provided it is not smothered.
2. Trust and psychological safety
The performing foundation is trust — and psychological safety: being able to speak up, propose, err without fear. The manager nurtures it by example, listening, fairness and recognition. Salim welcomes mistakes as learning, encourages Lina's questions and values Karim's expertise.
Cohesion does not mean absence of disagreement, but ability to debate then move forward together. A bonded team sustainably overperforms.
🔎 Concrete example — Freeing speech (Salim's case)
Welcome mistakes as learning.
Encourage questions and disagreements without humiliating.
→ ritual: 15 min "useful mistakes" every Friday.Result: freed speech, innovation and learning (Aristotle project).
Lesson: celebrate team successes, not only your own.
Section vocabulary reinforced definitions
- Tuckman model
- Development stages: forming, storming, norming, performing.
Simple example: Salim's team moves from storming (conflict) to norming (common rules).
What it is not: a value judgment — storming is not a failure.
Reflex: locate your team each quarter and adapt support.
- Psychological safety
- Climate where everyone can speak up, propose and err without fear: the foundation of performance.
Simple example: Lina dares say "I do not understand" without being mocked.
What it is not: accepting everything or never correcting.
Reflex: thank each question and each early-flagged mistake.
- Cohesion
- Strength of bonds: trust, mutual help, sense of belonging.
Simple example: Karim helps Lina 30 min per week, recognized in the team check-in.
What it is not: absence of disagreement nor mandatory outings.
Reflex: create mutual help + collective recognition each week.
- Trust
- Foundation: it is built by example, fairness, reliability and listening.
Simple example: Salim keeps his follow-up commitments and applies the same rules to all.
What it is not: a slogan on the wall with no acts.
Reflex: do what you say, say what you do, recognize your own mistakes.
In practice — Strengthening cohesion
- Locate your team (Tuckman): forming, storming, norming or performing.
- Adapt support: frame, arbitrate, co-build rules, empower.
- Nurture psychological safety: encouraged speech, mistakes = learning, fairness.
- Create bond and collective recognition; celebrate team successes.
Ready-to-say script — setting common rules (2 min)
"After these tense last weeks, I suggest we give ourselves simple rules: everyone can ask any question with no mockery, any early-flagged mistake is good news, and we help each other 30 minutes per week in pairs. Karim helps Lina on files, Lina shares her checklists. We test for one month, we adjust together. Agreed?"
Say it in a short meeting, then display the 3 rules on the wall or in a pinned message.
Copy-paste template — team charter
OUR STAGE (Tuckman): ............
OUR 3 RULES: 1) ............ 2) ............ 3) ............
MUTUAL HELP: pair ............ / slot ............
RIGHT TO ERR: flagged early = learning, never mocked
RITUAL: 15 min "useful mistakes" on ............
CELEBRATION: collective success of the month: ............Micro-business (2-3 people)
One mutual-help rule and a 10-min ritual are enough: closeness does the rest.
Remote / hybrid
Short video ritual + no-judgment question channel; celebrate in writing for absentees.
Algerian SME
Plan a simple friendly moment (shared tea, meal) with no high cost to create bond.
Intercultural
Make explicit that asking questions and admitting a mistake are strengths, not weaknesses.
✓ Best practices
- Locate the Tuckman stage and support.
- Nurture speech and welcomed mistakes.
- Celebrate collective successes.
✗ Common pitfalls
- Wanting to avoid storming.
- Punishing or ridiculing.
- Confusing cohesion with absence of disagreement.
Key takeaways
- Dynamics that build: forming, storming, norming, performing.
- Trust = foundation of performance.
- Psychological safety frees speech and learning.
- Cohesion = debating then moving forward together.
48h challenge — apply tomorrow
Run 15 min "useful mistakes": everyone shares 1 mistake and 1 lesson, with no mockery. End with 1 collective success celebrated. 15 minutes are enough.
- I can locate my team in Tuckman.
- I can concretely create psychological safety.
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Is storming a bad sign?
No, it is a normal and often necessary stage: the team confronts, adjusts roles, then finds its rules and performs. Smothering it prevents maturing. The manager's role is to channel, not deny.
Why does psychological safety matter so much?
It is the feeling of being able to take risks (ask a question, admit a mistake, disagree) without being humiliated. Research (Google's Aristotle project) identifies it as the top factor of performing teams: it frees speech, innovation and learning.
After the conflict, nobody dares flag mistakes in Salim's team. Priority?