Müşterilerimizin adını yayımlamıyoruz. Bu anlatım sektör, ekip ölçeği ve program kurgusu üzerinden aktarılmıştır; kurumu tanımlayacak ayrıntı içermez.
A gathering programme for a distributed team that meets physically once a year. The main constraint was stopping the two days from turning into meetings.
What was the problem in front of the company?
The team worked remotely from four different cities and came together physically only once a year. At previous gatherings the two days had filled up almost entirely with presentations and departmental meetings, and participants had found no time to get to know each other.
Management's description was blunt: "We already meet on screen every day. That is not what we come here for." But sharing the annual plans was also a genuine requirement of this gathering; the content could not simply be removed.
How was the programme built?
Rather than cutting the content, we concentrated it. The meeting portion of the two days was compressed into a single three-hour session and moved to the first morning — the hour when fatigue is lowest.
- A ban on screen presentations started in the afternoon. This was announced as a rule; "free time" left undefined turns into opening laptops in practice.
- Seating changed at every meal. The mix of cities and departments was planned in advance. This small intervention is the most efficient mechanism for people meeting each other in distributed teams.
- A shared piece of work was added. Not a competition format, but a single output completed together. Competition does not speed up bonding in a team that meets once a year.
Why was everyone accommodated at the same hotel?
Some participants lived in Istanbul and could have stayed at home. Even so, the whole team stayed at the same hotel. In distributed teams the evening hours produce more connection than the planned parts of the programme; everyone being in the same place is the precondition for those hours to happen at all.
What was the result?
About 60% of the two days consisted of non-meeting sections. In the company's post-gathering survey the clearest year-on-year increase was on the item "getting to know other parts of the team".
What stood out in management's own review was that condensing the annual plans into three hours had not weakened the content; on the contrary, the number of questions went up in the concentrated session.
What is the general lesson from this case?
At a remote team's gathering the scarce resource is not time but physical togetherness. Everything that can be done on screen should be left to the screen; the hours spent face to face should be reserved for what cannot.