It's tradition for most remote teams to pick one or two dates per year and meet in-person. Apart from some effective team building, that also means a ton of planning. How do you start such an operation? We've been looking at team retreats and are following some leading teams to see how they are doing it.
A team retreat is an extended trip with your whole company – usually a few days or up to a week long – that is intended to build team culture, let people socialize and get to know eachother. While a common thing to do in many companies and teams, it's almost crucial to the culture of a remote team, due to the usual lack of casual conversation and private exchange.
Remote team retreats tend to be longer – often a week or more – and tend to include more work-related presentations and discussions, rather than just social exchange. As it is often the only time a remote team comes together in-person, it's a popular time for long discussion and planning for the mid- to longterm future of the company.
Depending on company, team retreats happen in different locations that are well accessible to the largest part of the company (e.g. US is often a bad choice for international teams).
Retreat activities differ based on focus and company, these are some of our favourites:
Of course, there is almost no limit to what you can do during this retreat. One thing to keep in mind: This is a special week, so don't strap people into tight deadlines. Give everyone the opportunity to enjoy themselves – it's just one week.
Quite franky, I haven't organized a full team retreat myself, so this post was heavily inspired by the work of some leading remote-first organizations. Let's look at how they do it.
Zapier's piece is especially interesting because they have planned remote retreats with two employees to close to 200 employees. In this piece, they go over all the little details of what goes into planning and executing a successful retreat. This article is a must-read, but I had some favourite pieces nonetheless:
The folks at Remote.co have asked dozens of remote companies about their retreats and the responses – while not very detailed – are interesting to read nonetheless. A lot of it is duplicated, but some favourites:
Buffer's report on their retreats is – as expected – a great and very transparent view into planning a retreat for your remote team. If you've read the previous posts, you'll re-read a lot of stuff here, but there are some notable points to look at either way:
In a hybrid remote setup where remote and local employees live side-by-side, there is always a risk of different company cultures forming. So how can you bridge the gap sustainably?
Whenever we talk to founders, the idea to go remote usually hasn't occured until the company already had a few employees, so how do you effectively transition from a local office to remote?
Remote-First is commonly seen as the mindset needed to gain the most advantage out of remote work. What steps can you take today to get closer to being remote-first?