45 minutes on foot through Paris, as a group, before any activity. This is not a commute — it is the first conversation of the evening. People talk differently when walking side by side than when sitting face to face in a meeting room. Walking removes the desk, the badge, the org chart. It puts everyone at the same pace, literally. The Head of SRE and the junior walk in step. The hierarchy does not disappear — it goes into standby for the evening.

Bowling creates a light competition, without professional stakes, in which anyone can shine or fail without consequence. The most reserved engineer in meetings might be the best player. The manager might throw a gutter ball to the laughter of the whole team. These momentary role reversals are valuable: they reveal personality facets that the professional context masks, and they create shared memories — "remember when you got a strike on the last throw" — that weave the fabric of the group over time.

A Yemeni restaurant on the Champs-Élysées is not a neutral choice. It is not the brasserie next door, not the usual company restaurant. It is a choice that says: I am taking you somewhere you may not know, a cuisine you may never have tasted, a place that tells a story. This choice positions the manager as someone curious, open, off the beaten track — and this image reflects onto the team, which recognises itself in its manager.

An evening that extends beyond a certain threshold produces risks the manager must anticipate: the fatigue that turns good humour into irritability, the alcohol that lifts inhibitions in the wrong direction, the subgroups that form and exclude, the words that exceed the thought and are remembered the following morning. "Ending on a good note" is not a cliché — it is a technique. People remember how an evening ends, not just how it begins.

The following morning, everyone arrives at the office with the same shared memory — a good evening, no incident, no regrets. This shared memory is a trust capital the team can spend in the weeks that follow: to approach a difficult topic with less rigidity, to trust a colleague on a point they might previously have challenged, to get through a 3am production incident with the certainty that they will come out the other side together.

Putting 10 people in a seminar room for two days with the declared objective of "strengthening team cohesion" creates a social pressure that inhibits precisely what it seeks to produce. People know they are supposed to bond. This awareness produces a performance of bonding rather than genuine bonding. They play along with the exercises. They participate in the workshops. They go home two days later with offsite memories, not team memories.

An annual two-day offsite represents 16 hours of "cohesion time" across 365 working days. That is 0.4% of working time dedicated to relationships between team members. The remaining 99.6% unfolds in meetings, incidents, tickets, and deadlines. Cohesion built over 16 intensive hours once a year is no more durable than cohesion maintained over 4 hours per quarter in a carefully chosen informal setting.

Social psychology research on group cohesion converges on a few necessary conditions: sharing a common emotional experience, mutual discovery outside usual roles, and the feeling of having been chosen rather than summoned. The evening — walking, bowling, Yemeni dinner, drink at Châtelet — ticks all three. The offsite with its pre-formatted agenda and imposed participant list generally ticks none of them.

During a major incident, two trust dynamics are critical. Technical trust — "I know my colleague knows what they are doing" — and relational trust — "I know my colleague will be honest about what they do not know". The second is harder to build than the first, and it is built precisely in moments outside work. An engineer who has seen their manager throw a gutter ball and laugh about it knows that manager can acknowledge their limits. This link between the informal and the professional is real and documented.

Tensions in an infrastructure team accumulate in the daily routine — poorly handed-off tickets, contested architecture decisions, unevenly distributed on-call, meetings that overrun. These frictions are normal. They become toxic when they have no outlet. The evening is the outlet. Not because it erases the problems — but because it puts the people first and the problems second. You do not resolve conflicts over a Yemeni dinner. You remember that the people you work with are people, not nodes in an org chart.