The best teams I've led weren't close because of team building exercises. They were close because we'd earned the right to relax together.
When my team finished a sprint with time to spare, I'd sometimes just set up a call. No agenda, no work talk, just conversation. Some people joined, some didn't. Some used the time to chip away at tech debt they'd been itching to fix. Both were fine.
Thursdays after a strong sprint, a few of us would go out after work. Not organised, not mandatory, just a natural thing that happened because the work was done well. Planning was wrapped up before we headed out, so Friday was genuinely relaxed. Sprint reviews, retros, a calmer rhythm after two weeks of focused delivery.
None of this was a team building strategy. It was a side effect of trust. When people know the work is solid and nobody's going to fill their downtime with more tasks, they open up. You hear about weekends, kids, hobbies, the random things that make someone a person instead of a Jira ticket assignee.
I think we underestimate how much of team strength comes from these small moments. Not the structured icebreakers or the forced fun. The unplanned conversations where you discover your developer is obsessed with sourdough or your QA lead has strong opinions about Formula 1.
In tech, people often get labelled as "not great with relationships." I don't buy that. Put those same people in a room talking about something they care about and they'll go for hours. The problem isn't that developers can't connect. It's that most workplaces never create the space for it to happen naturally.
Building a team people want to be part of isn't someone else's job. Not the scrum master's, not HR's. It starts with the lead deciding that relationships matter as much as the backlog.