PostHog Handbook Library / Company

4,142 words. Estimated reading time: 19 min.

# Offsites

Auto TL;DR

## At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

1. All company offsites
2. Small team offsites
3. Hedge House
4. Cambridge
5. London
6. London hotel recommendations
7. Border Control
8. Travel insurance

While we’re async by default, there’s a very real upside to being in the same room - we’ve consistently found that a lot of our best ideas come from actually building things together in real life.

We understand organizing travel can be a challenge when you have personal/family commitments to manage, so we try to take a balanced approach to meetups:

- Once a year: all-company offsite
- Once a year: Small Team offsite (app and platform teams do this as a single combined offsite)
- Occasionally: in-person onboarding
- Whenever you like: in-person meetups

### All-company offsites

> Curious about our all-company offsites? Check out these links:

> - 2021 We shot this video at our Portugal offsite

> - 2023 What we built at our sun-kissed Aruba hackathon

> - 2024 What we built at our windswept Mykonos hackathon

Once a year, the entire company will get together somewhere in the world for a week. Usually we'll all fly on Sunday, have an opening dinner, spend the week doing a mix of hard work, strategy, culture and fun activities and we then all fly back home on Friday. Our past offsites have been in Italy, Portugal and Iceland. We try to ensure that everyone has their own bedroom.

These are organized by the Ops & People team, and we budget up to $3,000 per person in total for these.

Typical agenda:

- A couple of structured social events
- Team dinners
- 24hr Hackathon
- All-hands strategic sessions and workshops
- All-hands culture exercises
- A small amount of downtime so people can explore

### Small team offsites

We want to try to encourage small teams to get together once each year. Ideally they are spaced appropriately through the year in relation to the all-company offsite.

We want team offsites to be social events and encourage you to optimize offsites for meeting as many colleagues as is reasonably possible, even if it means spending more money or travelling further. Hogpatch in San Francisco or the Hedge House in London should be the default choice, because:

- They're places where there are already a lot of PostHog people that you can hang out with. The more we have random cross-pollination, the more ambitious ideas we'll come up with
- If most teams do their offsites there, you're much more likely to run into even more people
- We've put a lot of money and effort into making Hogpatch and Hedge House beautiful spaces that you want to work from
- SF has the benefit of being the epicenter of everything happening in tech, and we have lots of YC founders working out of Hogpatch who you can meet and learn from

We prefer AirBnBs over hotels, to give your team even more time to hang out, but this is not mandatory.

If you do decide to do a small team offsite somewhere outside of these two hubs, let Kendal know why. That way we can figure out how to make going to the hubs more appealing, or perhaps open new hubs.

Planning a small team offsite? Kendal’s got you covered. Here’s how it works:

- The team lead should message Kendal with their proposed dates.
- Kendal will then:
- Create a Slack channel for the offsite (use `#offsite-[team]-[month]-[year]-[where]`) and add everyone who’s going.
- Set up the offsite budget in Brex.
- Update the team’s Canvas with:
- Accommodation details and a handy map
- A flight tracker
- A rough itinerary (Kendal will include the mandatory bits, like 360° feedback/Readme sessions, team leads can fill in the rest)
- Look up dining options for a couple of group dinners (we like to keep a few nights free for “choose your own adventure” dining).
- Suggest and book a whole group activity for everyone to enjoy together.

If there’s anything ad hoc you’d like Kendal to take point on, just let her know, she’s happy to help! Each team member is still responsible for booking their own flights.

Some guidelines:

- Quarterly planning is a great focal point for team offsites – it's worth scheduling your meetup for the week of planning.
- Outside of your small team, you should only invite people who actually need to attend to make the offsite a success - if it would be 'nice to have' them attend, they shouldn't be going.
- It can be useful to combine offsites but beware if you add too many people everything gets harder to arrange. There's no hard and fast rule here but the more people that are attending the more concrete you need to be on who is organising and why people are attending. It will be more work and you should be purposeful about it.
- If the number of attendees is >10 actively consider if Kendal should be attending so there is a person attending whose only focus is making sure it goes well and everyone else can focus on the work of the offsite.
- Specify offsite start and end times down to the hour, for clarity and efficient use of everyone's time.
- These offsites don't happen very often and involve a lot of travel, so make sure you make the most out of it by having an agenda and an idea of what you want to achieve _before_ the start of the trip. Also, it's a good idea to have an expectation-setting session (can be async in a Figjam) to ensure everyone is on the same page about what the outcome/output of the offsite should be.
- Make it very clear who is participating in each session. Sessions / activities require full participation from attendees, especially for the likes of a hackathon given it runs over multiple days. Ideally one person should be responsible for the agenda and run a kick-off at the start of the hackathon.
- You should do a 360 degree feedback session. It can feel uncomfortable doing these, but almost everyone who's done one at PostHog has come out feeling better and with a whole host of things they can improve. These are best in person.
- This can work better over a shared cooked meal or takeaway in the accommodation rather than a noisy restaurant, particularly for people who might be anxious about the format or the feedback.

Ideas for the agenda:

- 360 degree feedback session (mandatory!)
- A spoken README session early in the week to share "Who am I/How I work best"
- Planning session – what does the team want to achieve in the next month/quarter/year?
- Look at the team page - what needs to be updated?
- Dogfooding session – set PostHog up in a toy project from scratch, looking for pain points
- Hackathon - try to leave 2 days for this, and most importantly avoid sessions interrupting hacking
- Even some regular work on ongoing challenging projects - this is the best time for exchanging knowledge!

> Don't run a hackathon during an onboarding offsite. Other offsites normally do have a hackathon. Participation should be _very_ strongly encouraged but not mandatory - if not everyone is taking part make sure that working spaces are available to accommodate the different styles of work. It is super important that people taking part are fully available and focused on participating. Given the offsite is an opportunity to work together there should be no teams of one. This extends beyond the formation of teams and into the hackathon itself in cases where there is team switching.

Here's a real-world example: Product Analytics team's Munich offsite agenda (internal Slack link). Feel free to take inspiration – though your team's needs and wants might be quite different!

The budget for these trips is up to $2,000 per person in total. We ask team members to use their best judgement for these and try to be thrifty where possible - these should be enjoyable, but not feel like a holiday. Generally it's easier to hit budget if you have people travel in on a Monday and out on a Friday - they don't need to be as long as a whole team offsite.

You should assign someone on the small team to be responsible for planning the offsite (doesn't have to be the lead), and they will be supported by the Ops & People team to ensure a successful experience.

> On occasion during busy hiring peak time, we do recommend any team member involved in the interview process to dedicate at least one hour block per day during the offsites to accommodate candidate interviews so that this does not delay the hiring process on your team while you're away. Please coordinate directly with #team-talent if you have additional questions.

### Hedge House

PostHog runs two Hedge Houses in the UK - a small one in Cambridge and a larger one in London. They are actual houses (yes, with a few bedrooms attached!) designed for small teams to run their offsites, host in-person onboardings, or come together for larger internal events like hackathons. Anyone at PostHog is welcome to use them as much as they like — alongside Hogpatch in San Francisco, these are where you should default to doing team offsites and in-person onboarding.

#### Cambridge

Message Kendal Ijeh to check availability or make a booking at the Cambridge Hedge House.

#### London

Our light-filled, studious office is a reliable homebase between Farringdon and Barbican. It’s entirely ours, open 24/7 and the perfect place to stay if you're visiting from abroad. Use the Hedge House London slack tool to see the full address, book a room and/or desk, plus see who else will be there during the week you visit. This means you can easily self-serve, but ask Kendal Ijeh with any questions.

### London hotel recommendations

For offsites and onboardings in London, below is a list of hotels recommended in our #London Slack channel by folks who have stayed at these hotels.:

- Marrable's Farringdon hotel
- The Zetter Clerkenwell
- Hotel Indigo Clerkenwell
- Yotel London City
- Z Hotel City
- citizenM Tower of London hotel
- Clayton Hotel - City of London
- Hampton by Hilton - London Old Street
- hub by Premier Inn London Clerkenwell hotel
- Bob W Tower Hill Studios
- Ruby Stella hotel

If hotel prices are above £200 per night, it is worth quickly looking for alternatives as ~£170 per night should be achievable midweek in London. If prices are high, you should optimise travel for total cost (flights & accom) so if you can get cheaper flights or hotel by moving dates +/- 1 day, then look into these options.

### Border Control

Quite often you will be required to travel to places where some kind of visa is required even if just a visitor visa like an ESTA. When entering places like the US, for work purposes, border control agents may ask the purpose of your trip. In these instances it's best to avoid using PostHog terms like "onboarding" as this can be confusing. It's much better to more generally describe the purpose of your trip. In nearly all circumstances this will be to hang out with your colleagues and to take part in team building exercises. It's usually good to emphasize that you'll be on a short trip and that the company is paying for everything. You should be prepared with the exact addresses of where you are staying and the details of your flight out of the country.

A successful strategy is usually to start off with a high-level purpose of your trip which is usually something like "hanging out with colleauges" or "I am here for a business meeting with colleauges", it is also usually advisable to only respond with a minimal amount, saying only what is necessary. If the agent asks for more details it's usually good to go into a bit more detail about the company structure "I work for a US tech company and I am based in [Insert your country] where I work remotely. I am here to do some in-person meetings with my colleagues for the next few days and I fly back on [insert date]". Sometimes the border patrol agent will ask more about the business, it's fine to give these details and be as honest about that as you would anybody else. If further details are required of the content of the trip, you can again give some context of how we like to lean into the benefits of in-person working and since most of your colleagues are based in the US, you are travelling their for a few days to meet in-person and will be returning home afterwards.

For all company offsites, it's best to describe this as a company gathering where you will be hanging out with colleagues for the week. Generally, it is best to avoid using the phrase "training" as this can also be confusing.

### Travel insurance

Many of our company offsites involve team members traveling abroad, and although we hope that these trips are uneventful and safe for all, in the event of an accident or medical emergency, we carry travel insurance through as well as general & auto liability policies through our partner Embroker.

In the event of an emergency, please cover any related expenses (ideally on your company card) and keep receipts, and then reach out to Kendal as soon as possible. We will assist with making a claim based on our policy binders.

#### Flight delays

If your travel plans are affected due to a flight delay or an airline-induced missed connection and you are forced to stay somewhere unplanned overnight, push the airline to cover the cost of your accommodations (including meals). It's not uncommon for them to initially tell you they no longer offer free hotel rooms for delays that were caused by the airline, but with a little bit of polite coaxing, they will likely give in.

#### Partners / family joining offsites

Sometimes at PostHog you will be asked to travel to places you've never been before and it could be a good opportunity to travel with your partner / family. At PostHog, we do infrequent in-person work that we want to maximise this time in person and your focus to be on PostHog, without distraction. This is why we don't allow partners or family to join you for the dates that the offsite / onboarding takes place. If timing allows it, you are able to tack holiday onto either side and for your partner/family to join you for those dates. However, for the dates of the offsite, you should be staying alone and focusing on your time with your teammates.

### How to plan an offsite in 8 weeks - a checklist

Below is a rough timeline for planning your next offsite, as well as links to templates and resources that you can repurpose and customize as needed. Here's a spreadsheet template you can use with your team to democratically vote for the meetup location, and in other tabs, include travel information (in case someone's flight gets delayed/cancelled), schedule, project ideas, team activities, etc. To use any of the templates, create a copy to your own drive and edit as you see fit.

8 weeks out

- [ ] Choose dates
- Try to avoid public holidays and be mindful of proximity to other offsites to minimize travel fatigue
- School holidays are more difficult for people with children
- Be mindful of the season of your chosen location, as this will dictate what activities you can plan
- It is worth getting people to hold dates as early as possible, even before you've selected a location
- [ ] Choose location
- Consider choosing a location that is relatively easy for most people to attend without having to travel outrageous distances or deal with difficult visa processes.
- Transportation to the offsite is usually one of the larger budget line items, so do some research on the cost of flights from team locations before finalizing a location.
- Consider the cost of transportation to/from the airport, and around town, for when your team arrives at the offsite location.
- Be mindful that people who take long flights won't appreciate a 2hr journey from the airport to accommodation!
- [ ] Announce to team
- You can have fun with this and build excitement by progressively dropping hints and having folks try to guess the location
- [ ] Create an offsite Slack channel and invite team
- This is super useful for making announcements and keeping the team updated throughout planning

7 weeks out

- [ ] Secure accommodations
- The ideal location will depend on the size of your team
- We recommend booking a large Airbnb for teams under 10 people as this provides for a more casual atmosphere and can help control costs if you opt to have the team cook meals together. You can also book an Airbnb and supplement with a nearby hotel if the Airbnb doesn't have enough rooms.
- For larger teams, consider a centrally located hotel that has a bookable space with configurable furniture for different activities, an onsite restaurant or bar to simplify meals and provide a location for free social time, as well as amenities like a gym for those who like to stay active while they travel
- [ ] Start flight booking process
- To simplify this process, we give all team members access to a company card, and we ask people to book their own flights
- We strongly recommend this approach as centralizing flight booking can be a huge headache for offsite lead, and this allows team members to accurately enter their personal information including airline frequent flier and trusted traveller numbers
- Encourage folks to buy flights early and with the option to refund if they are unable to attend to save on costs. Use your judgement here - 20% or so is reasonable for the flexibility, but double the price is not really worth it.
- In the event that a new team member will be attending an offsite, but has not started yet, please contact the Ops team to help coordinate. In these cases, the process is:

1. Preemptively create the new team member a Google account
2. Issue them a Brex card to their work email with a sufficiently high temporary balance to cover travel costs
3. Add them as a guest to any planning Slack channels and/or share any necessary itinerary information such as arrival dates/times and airports
4. Have the new team member book travel as usual

- [ ] Draft rough schedule
- Building the schedule as a separate Google Calendar that can eventually be shared with the team will allow you to flexibly move sessions around as you finalize the itinerary
- [ ] Send info gathering form
- Use this form to collect important information like flight details, clothing sizes for merch, dietary restriction, and preferences for things like sharing rooms
- [ ] Brainstorm merch/meeting room decorations (generally just for company-wide offsites)
- Having some branded merch to commemorate the offsite upon arrival is a great way to welcome people and get them excited for their time together (generally this is for whole team offsites only for budgetary reasons)
- If you are staying in a hotel, decorating a meeting room makes it feel much more personal and less corporate
- In the past, we've done shirts, hats, scarves, notebooks, stickers, pens, and water bottles -- feel free to get creative with it

6 weeks out

- [ ] Draft budget
- Using the tentative schedule, you can begin to estimate a rough budget to guide planning. Here are some benchmarks to use, however these will vary a lot based on location, size of team, and how cost-constrained you are:
- Accommodations = $200/night/person
- Intercontinental airfare = $1000/person; intracontinental airfare = $500/person
- Ground transportation = $50/day/person
- Food & drinks = $50/day/person
- Contingency = 10% of total budget
- [ ] Secure transportation
- Book any group transportation like coaches or a rental car ahead of time
- [ ] Finalize team outings and book as needed
- [ ] Flights booking deadline
- [ ] Info gathering form deadline

5 weeks out

- [ ] Assign rooms
- Using preferences from the info gathering form regarding sharing rooms, assign accordingly
- [ ] Secure visas where necessary
- [ ] Review and finalize merch proofs
- [ ] Finalize itinerary
- [ ] Finalize budget
- [ ] Assign session leads & secretaries
- Decide in advance who is going to record the notes from each session - it is _really_ easy for post-offsite followup to fall through the cracks
- With the schedule finalized, assign folks as session leads to design session plans

4 weeks out

- [ ] Reserve restaurants for communal meals
- [ ] Book any remaining activities
- [ ] Order merchandise
- Important to give yourself lots of lead time here, in case of production or shipping delays
- Depending on how restrictive customs are for your destination, consider shipping merch to teammates and checking them as additional bags on flights to the offsite

3 weeks out

- [ ] Draft session plans/presentations due
- [ ] Draft offsite guide package
- [ ] Design and print superlatives/awards
- One activity we've found quite popular is giving out superlative awards to the team during the closing ceremonies

2 Weeks Out

- [ ] Review and finalize session plans/presentations
- We recommend having the offsite lead connect with session leads to review their plans and offer feedback before finalizing them - you want to make the most out of your sync time together
- [ ] Block your calendar and send a reminder in Slack for other team members do the same, to avoid interviews and other meetings being booked during key sessions or at times incompatible with the new timezone. The offsite calendar event needs to be marked as "busy" to prevent others from booking over it, which means changing the default for all-day events.
- [ ] Designate someone to bring or organise some of the essential supplies you expect to need for the week. At a minimum have post-it notes (don't skimp on cheap ones that fall off the wall), sharpies, a HDMI cable and / or a Chrome Cast.

1 Week Out

- [ ] Final plan review
- The offsite lead should do a final, thorough review of the full plan and finalize any outstanding details - visually walk through the entire schedule and see if anything is missing
- [ ] Unveil the final offsite guide to the team

1 day before

- [ ] Add your new timezone as a secondary timezone in Google Calendar and check the 'Ask to update my primary timezone to current location' option. Don't update your primary timezone to the new one, as this causes issues for interview scheduling.
- [ ] We recommend that the offsite organizer consider arriving a day early to prep for the team's arrival
- [ ] Shop for any miscellaneous supplies and groceries (onsite)
- [ ] Print and organize a few paper copies of the itinerary (onsite)
- [ ] Create "Careless Whispers" envelopes (onsite)
- This passive activity involves creating an envelope for every member of the team, posting them in a central location, and encouraging folks to write small notes to each other. These can be anything from retreat memories to compliments, and make a really nice memento to remember the offsite
- Consider also making and posting envelopes for folks who cannot attend

1 week after

- [ ] Collect post-mortem feedback from the team
- We generally do this as an open GitHub issue, but you can also create a Google form to facilitate this

### All company offsite hackathon

The hackathon is always a highlight of the offsite. We tend to run them like this:

Session 1: ideation dinner The day before the start of the hackathon we do a casual 'ideation' dinner where we encourage people to chat about ideas

Session 2: hackathon kick-off The hackathon kick off is 1.5 hours at the end of the day. Ideally we do this in a conference room with beers and wine.

- Everyone writes down their ideas on multiple post-it notes in about 10 minutes.
- People come up to the front one-by-one, and they get 30 seconds to pitch all their ideas.
- Everyone gets three votes to put on whichever ideas they like most. Just do this as a tally. You can't vote on your own idea
- We dismiss all ideas with zero votes, and sort all the other ideas from top to bottom based on the number of votes.
- Everyone writes their name on the other side of the sticky bit of a small piece of post-it note, then add their name to the idea they want to work on. Every group should have at least two people in it, and ideally 3.
- Once groups are formed, everyone can go off and ideate or hack.

Session 3: presentations

This should be the last work related session of the offsite. Again ideally in a conference center with beer and wine provided.

Each group gets 5 minutes to demo and present their idea.

2 weeks after

- [ ] Compile post-mortem feedback and share with team
- [ ] Host post-mortem meeting to discuss any outstanding issues (optional)

Canonical URL: https://posthog.com/handbook/company/offsites

GitHub source: contents/handbook/company/offsites.md

Content hash: `a7c3fe6cec136b0c`

Static reader notes

- `MDX_COMPONENT_STATIC_ADAPTER`: Adapted interactive MDX components for static reading: TeamMember.