Every other week, we stopped.
Food. Drinks. Tech happy hour.
The calendar description was exactly one sentence: “Every other week we have a tech happy hour where we eat food and drink.”
No agenda. No presentation. No forced lesson attached to the pizza.
That was useful.
The technical organization had grown across product, development, WebOps, SysOps, and IT. Most conversations happened because something needed to ship, something was broken, or somebody wanted another server.
Those groups could work beside one another for weeks while only meeting inside an incident or a planning argument. That was a bad way to learn somebody's name.
Happy hour gave people a reason to talk before the next problem assigned them to the same call.
This was not a grand culture program. It was recurring time and a budget for food.
Recurring mattered. One big party could be skipped or forgotten. Every other Wednesday became part of how the team worked.
The following morning, my own contribution to office hospitality became even more direct. I offered to buy breakfast for anybody who brought me a sausage, egg, and cheese sandwich within thirty minutes.
Leadership takes many forms.
Teams work better when people know one another outside the exact task in front of them. A shared drink does not fix a bad org structure. It can make the next honest conversation easier.
It also gave new people a low-stakes way into a team that already had history and inside jokes.
So we kept the event simple and kept putting it on the calendar.
Eat food. Drink. See everyone again in two weeks.