Team cohesion

Foundations of cohesion

Three dimensions of operational cohesion: horizontal (among peers), vertical (with the leader), and task (toward the mission). The three are independent. A team can have excellent horizontal and poor vertical cohesion, or excellent task and poor horizontal cohesion. The cohesion that matters in combat is task cohesion.

• Horizontal: peers know, trust and protect each other
• Vertical: functional respect for the leader, acceptance of decisions
• Task: everyone knows the mission and shares its sense
• Dimensions reinforce but do not replace one another

Functional trust

Functional trust is specific and verifiable: you trust the comrade for task X based on observed evidence. You do not trust them 'as a person' in the abstract. It is built with repeated proofs in training and then in operation. It is destroyed by a few serious violations: unpredictable behaviour under fire, abandonment, lying about operational facts.

Individual predictability

Every member of a cohesive team is predictable within a defined perimeter. The team leader knows their MG will fire 5-round bursts, hold the right sector, call red ammo at 25%. The medic knows the first intervention will be MARCH and the comrade will speak to identify themselves. Predictability is not rigidity: it is shared language.

1. Standardise internal procedures (hand signals, brevity, react-to-contact)
2. Rehearse procedures until they execute without thought
3. Note individual variations (who is slow at recovery, who is fast on map)
4. Update the model of the comrade when it changes

Conflict management

Internal conflicts are inevitable in any team operating under stress for weeks. Do not eliminate, manage. The operational principle is separation between technical and personal: technical critique is immediate, in public if needed, without personalising; personal conflict is handled apart, off operations, with a mediator if needed.

• No emotional arguments under fire, on patrol, before operations
• Technical critique: fact + impact + correction, no judgement on the person
• Personal conflict: face-to-face in protected location, third party if serious
• Escalation: if peers do not resolve, squad leader decides; if not, PL
• Do not tolerate silent feuds — they explode in operation

Integrating newcomers

Inserting a new member is the most fragile moment of a cohesive team. The newcomer does not yet share the others' model and the others do not share theirs. The shakedown phase lasts 2–4 weeks. Compress this phase with three actions: assign an experienced buddy, reduce initial decision responsibility, rehearse standard procedures in training before operational exposure.

1. Initial briefing: team culture, unwritten rules, key people
2. Assigned buddy: newcomer operates with a specific veteran for the first 14 days
3. Progressive tasks: first limited technical tasks, then full participation
4. Social inclusion: meals and decompression together from day 1
5. Weekly debrief with buddy: what works, what does not, obstacles

Common mistakes

• Confusing operational cohesion with off-duty sociability
• Keeping personal conflicts hidden — they explode at the wrong moment
• Treating the newcomer as outsider too long (beyond 4 weeks)
• Punishing technical critique as if it were insubordination
• Allowing national or language cliques in multinational teams
• Promoting friends into positions they cannot cover technically

Lessons learned Ukraine

International teams in Ukraine often work with 5–8 nationalities, different languages, different doctrines, heterogeneous experience. Cohesion that works in these conditions is built on three pillars: shared brevity codes (NATO standard), one operational language at a time (English or Ukrainian), and a visual tag system on kit to identify roles under stress. Cohesion between cultures exists, but is entirely artificial: it must be designed, not assumed.